On 13/11/2010, at 1:13 AM, Spencer Oliver wrote:

> On 12/11/2010 14:31, Spencer Oliver wrote:
>> Hi,
>> 
>> Started a new thread as the others are getting bogged down.
>> 
>> This defaults to building the jimtcl inline - only one configure step
>> required, eg.
>> ./configure --enable-maintainer-mode --with-jim-ext=nvp ...
>> 
>> The only limitation is that we have to pass the jim options through
>> openocd. autoconf currently does not allow project specific subconfigure
>> options - this is being looked at.
>> I have also added a temp hack so we do not get warnings due to the jim
>> headers - this will need looking at.

This looks like it is heading in the right direction.

> 
> As mentioned above we are currently adding a hack so jimtcl builds inline - 
> this is fine for the standard configure/make case.

Can you explain why you needed -DHAVE_NO_AUTOCONF?
I tried with the latest version of jimtcl and it didn't need this.

> 
> Running a few other tests shows that to use jimtcl inline the jimtcl build 
> system will need other updates to function as per openocd.
> For example make dist/distcheck will fail as jimtcl does not support the std 
> autotools options.

Tell me what you need these targets to do.

Cheers,
Steve

--
µWeb: Embedded Web Framework - http://uweb.workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au      P: 0434 921 300
E: ste...@workware.net.au   F: 07 3102 9221




_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to