On 16/11/2010, at 6:05 AM, Spencer Oliver wrote:

>> 
>> 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.
>> 
> 
> This is only required when using jim inline.
> If using an external lib then all is ok, it is due to multiple defines:
> It seesm due to the inclustion of jimautoconf.h from jim.h:94
> 
> In file included from ../../../openocd/jimtcl/jim.h:94,
> [snip]
> I have not tried jim git head - onlt the version that is linked to openocd 
> 0.63

As I suspected. This is fixed in:

  http://repo.or.cz/w/jimtcl.git/commit/5a9c9cdc1a0add1d0e6e63e64d5d7d7febc6d749

Please try at least this version and you can get rid of -DHAVE_NO_AUTOCONF 
which could
lead to problems with 32 vs 64 bit integers on some platforms.

> 
>>> 
>>> 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.
>> 
> 
> i have noticed that jim only really uses autoconf, but does not use automake. 
> OpenOCD uses both and so expects the standard make targets, eg:
> http://www.gnu.org/software/automake/manual/html_node/Third_002dParty-Makefiles.html#Third_002dParty-Makefiles
> 
> we can work around this many ways depending on how much/little work you fancy 
> doing :)

I won't use automake, but I can probably add all of these targets to be 
compatible.
Most of them are likely to be nops.

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