Uisng SlickEdit with Yagarto ARM toolchain

[mwb1100]

I was wondering if anyone might have some pointers to using the Yargarto ARM toolchain (GCC, GDB, Eclipse and some plugin to get Eclipse to work with OpenOCD JTAG - http://www.yagarto.de/)?  I have this all working fine with Eclipse, but I'm not loving it. I'm wondering if anyone out there has any experience with getting this stuff to work well via SlickEdit.

I'm only doing this for a class so it's not essential and I don't want to spend a lot of time with it, but if someone out there has a config already working with this stuff, I'd love to know a few details.

[hs2]

Well, build is not a big deal I think. I've used a cross-toolchain with a (physical) JTAG connection to the target and SE's gdb support where the toolchain came with a gdb proxy. The gdb proxy provided a TCP interface so I was able to use the std. remote gdb debugging feature of SE.
Hmm - seems that OpenOCD works the same way... (see http://openocd.berlios.de/doc/GDB-and-OpenOCD.html)
HS2

[mwb1100]

Thanks - I hope it is as simple as that, but I'm enough of a Windows guy that words like "gdb proxy" mean little to me.  I'll fiddle around with it this weekend and hopefully I'll be able to ditch Eclipse as the IDE. (I don't meant to imply that Eclipse is awful - it's just that sometimes you're used to what you' reused to, and Eclipse isn't it for me).

[hs2]

A 'gdb proxy' is a customized gdb which provides the mentioned std. remote interface (TCP) to the user and handles the JTAG/target interfacing internally in a transparent way.
So it seems to the user that just a remote machine is debugged.
HS2

[jporkkahtc]

FYI ... I was struggling to get this to work and finally figured it out.
I have 8dot3 name generation disabled (fsutil 8dot3name set 1) on my machine and it turns out that "vs-gdb-proxy.exe" doesn't work.

vs-gdb-proxy doesn't parse its command line properly when launched via:
"C:\Program Files\SlickEditV18.0.1 x64\win\vsproxy.exe"
But change that up to
C:\PROGRA~1\SLICKE~1.1X6\win\vsproxy.exe
and then it works.