[Openocd-development] [PATCH] Build inline jimtcl

2010-11-12 Thread Spencer Oliver
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. autocon

Re: [Openocd-development] [PATCH] Build inline jimtcl

2010-11-12 Thread Spencer Oliver
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

Re: [Openocd-development] [PATCH] Build inline jimtcl

2010-11-13 Thread Øyvind Harboe
Works fine here for the case of using installed and submodule jim tcl. Tested with cross compiles for installed jim. When Jim Tcl is not installed and using --disable-internal-jimtcl, the build fails as it should. I like that there is no detection going on, it does what it is told to do. This avo

Re: [Openocd-development] [PATCH] Build inline jimtcl

2010-11-14 Thread Steve Bennett
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-m

Re: [Openocd-development] [PATCH] Build inline jimtcl

2010-11-15 Thread Spencer Oliver
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 nee

Re: [Openocd-development] [PATCH] Build inline jimtcl

2010-11-15 Thread Steve Bennett
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 -DHAV

Re: [Openocd-development] [PATCH] Build inline jimtcl

2010-11-16 Thread Spencer Oliver
As I suspected. This is fixed in: http://repo.or.cz/w/jimtcl.git/commit/5a9c9cdc1a0add1d0e6e63e64d5d7d7febc6d749 cheers - i will respin the patch against latest jimtcl then. we can work around this many ways depending on how much/little work you fancy doing :) I won't use automake, b

Re: [Openocd-development] [PATCH] Build inline jimtcl

2010-11-16 Thread Øyvind Harboe
> We also need to think about the openocd distribution, previously it was > standalone, now we have a dependancy. The question is do we distribute the > submodule version of jimtcl in the openocd tarball. > > My thinking is yes we do, so the user gets the tested version of openocd. + there is the

[Openocd-development] [PATCH] Build inline jimtcl - 2

2010-11-16 Thread Spencer Oliver
Updated patch that removed the HAVE_NO_AUTOCONF hack. This has an updated jimtcl version. I will look into the make dist issues, but this gets the inline build working for the average case. Cheers Spen >From 4336b9e07195b416af651f385eadbbc5c33345ab Mon Sep 17 00:00:00 2001 From: Spencer Oliver

Re: [Openocd-development] [PATCH] Build inline jimtcl

2010-11-17 Thread Laurent Gauch
>/ As I suspected. This is fixed in: />/ />/ http://repo.or.cz/w/jimtcl.git/commit/5a9c9cdc1a0add1d0e6e63e64d5d7d7febc6d749 />/ / cheers - i will respin the patch against latest jimtcl then. >>/ we can work around this many ways depending on how much/little work you fancy doing :) />/ />/ I

Re: [Openocd-development] [PATCH] Build inline jimtcl - 2

2010-11-16 Thread Peter Stuge
Spencer Oliver wrote: > Updated patch that removed the HAVE_NO_AUTOCONF hack. > This has an updated jimtcl version. Well done! > +if test "$use_internal_jimtcl" = yes; then > + if test -d "$srcdir/jimtcl"; then This doesn't work because the jimtcl exists also in the openocd repo. Change it to

Re: [Openocd-development] [PATCH] Build inline jimtcl - 2

2010-11-17 Thread Spencer Oliver
On 16/11/2010 22:15, Peter Stuge wrote: Spencer Oliver wrote: Updated patch that removed the HAVE_NO_AUTOCONF hack. This has an updated jimtcl version. Well done! +if test "$use_internal_jimtcl" = yes; then + if test -d "$srcdir/jimtcl"; then This doesn't work because the jimtcl exists a

Re: [Openocd-development] [PATCH] Build inline jimtcl - 2

2010-11-18 Thread Spencer Oliver
On 16/11/2010 22:02, Spencer Oliver wrote: Updated patch that removed the HAVE_NO_AUTOCONF hack. This has an updated jimtcl version. I will look into the make dist issues, but this gets the inline build working for the average case. I have updated the patch to support passing options to the j

Re: [Openocd-development] [PATCH] Build inline jimtcl - 2

2010-11-19 Thread Spencer Oliver
On 18/11/2010 14:10, Spencer Oliver wrote: On 16/11/2010 22:02, Spencer Oliver wrote: Updated patch that removed the HAVE_NO_AUTOCONF hack. This has an updated jimtcl version. I will look into the make dist issues, but this gets the inline build working for the average case. I have updated t

Re: [Openocd-development] [PATCH] Build inline jimtcl -> WORKS ON LINUX and CYGWIN

2010-11-16 Thread Laurent Gauch
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. autocon