On 14 July 2011 11:17, Steve Bennett <ste...@workware.net.au> wrote: > On 14/07/2011, at 7:19 PM, Spencer Oliver wrote: > >> On 13 July 2011 22:53, Steve Bennett <ste...@workware.net.au> wrote: >>> >>> Hi Eric, >>> >>> Thanks for the report. >>> This is caused by a couple of things. >>> >>> Firstly, the version of jimtcl used by openocd isn't fully functional >>> when built under mingw. It's fine for openocd, but things like backslashes >>> in paths and exec aren't handled properly. So the built jimsh isn't suitable >>> for configure/autosetup. (Not that the latest version of jimtcl adds better >>> support for mingw, but that version is not yet used by openocd) >>> >>> But, that wouldn't be a problem except for... >>> >>> Secondly, when openocd installs it also installs jimtcl. It really >>> shouldn't. >>> It uses jimtcl internally and doesn't need anything installed. >>> >> >> I have looked into this and there is no easy way when using automake, > > Really? Then maybe we have the wrong approach of treating jimtcl as > a subproject. Maybe it should be simply be a subdirectory where > configure and make are run and the directory simply added to the search > path for headers and libraries. >
I tell a lie, just discovered the noinst_SUBDIRS and that seems todo what we want Cheers Spen _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
