Re: [Openocd-development] Openocd release known issues
On 28/06/2011 10:09, Steve Bennett wrote: One observation is that jimsh0 is built in the src dir, perhaps it would be better to use the builddir. I tend to build out of tree for various arch's and having jimsh0 built in the src dir does create issues for this kind of setup. I will see if this is easily doable. If its problem then perhaps adding jimsh0.exe to .gitignore Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 28/06/2011, at 6:32 PM, Spencer Oliver wrote: > On 27 June 2011 22:33, Steve Bennett wrote: > On 27/06/2011, at 10:07 PM, Spencer Oliver wrote: > >> On 27 June 2011 11:05, Spencer Oliver wrote: >> Thanks that solves all the problems i see with make distcheck. >> At some point i may look into a method of tweaking so we do not install >> unnecessary files, but all is good for the next openocd release. >> >> Cheers >> Spen >> >> Spoke to soon :) >> jimtcl head now fails to build under cygwin - ok under linux. >> >> After a full distclean i then get a segfault >> === configuring in jimtcl (/home/soliver/openocd/openocd-inline/jimtcl) >> configure: running /bin/sh ./configure.gnu --disable-option-checking >> '--prefix=/usr/local' '--enable-maintainer-mode' '--disable-shared' >> '--disable-werror' '--enable-parport' '--enable-jlink' '--enable-rlink' >> '--enable-ft2232_ftd2xx' 'CFLAGS=-O0 -g' --cache-file=/dev/null --srcdir=. >> No installed jimsh or tclsh, building local bootstrap jimsh0 >> ./configure.gnu: line 2: 2392 Segmentation fault (core dumped) $SHELL >> .././jimtcl/configure --with-jim-ext=nvp --disable-lineedit "$@" >> configure: error: ./configure.gnu failed for jimtcl >> >> The issue was introduced in commit f25d6276ee487d583e35c48f3125ef388c9f7d3f > > Try latest git. You will need to remove the old autosetup/jimsh0.exe > > > Steve, > > Another small observation cygwin does includes tclsh - tclsh.exe and > tclsh84.exe tclsh84 isn't "good enough". tclsh85 is OK, and it will be used if it is available. Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 28/06/2011, at 6:24 PM, Spencer Oliver wrote: > On 27 June 2011 22:33, Steve Bennett wrote: > On 27/06/2011, at 10:07 PM, Spencer Oliver wrote: > >> On 27 June 2011 11:05, Spencer Oliver wrote: >> Thanks that solves all the problems i see with make distcheck. >> At some point i may look into a method of tweaking so we do not install >> unnecessary files, but all is good for the next openocd release. >> >> Cheers >> Spen >> >> Spoke to soon :) >> jimtcl head now fails to build under cygwin - ok under linux. >> >> After a full distclean i then get a segfault >> === configuring in jimtcl (/home/soliver/openocd/openocd-inline/jimtcl) >> configure: running /bin/sh ./configure.gnu --disable-option-checking >> '--prefix=/usr/local' '--enable-maintainer-mode' '--disable-shared' >> '--disable-werror' '--enable-parport' '--enable-jlink' '--enable-rlink' >> '--enable-ft2232_ftd2xx' 'CFLAGS=-O0 -g' --cache-file=/dev/null --srcdir=. >> No installed jimsh or tclsh, building local bootstrap jimsh0 >> ./configure.gnu: line 2: 2392 Segmentation fault (core dumped) $SHELL >> .././jimtcl/configure --with-jim-ext=nvp --disable-lineedit "$@" >> configure: error: ./configure.gnu failed for jimtcl >> >> The issue was introduced in commit f25d6276ee487d583e35c48f3125ef388c9f7d3f > > Try latest git. You will need to remove the old autosetup/jimsh0.exe > > > > Many Thanks again, that seems to fix the build (for cygwin and mingw) - i > will try functional testing later today. Thanks. > > One observation is that jimsh0 is built in the src dir, perhaps it would be > better to use the builddir. > I tend to build out of tree for various arch's and having jimsh0 built in the > src dir does create issues for this kind of setup. I will see if this is easily doable. > > Also it would be good if a distclean removed jimsh0 as it is generated by > configure. Yes. Good idea. > > Cheers > Spen -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 27 June 2011 22:33, Steve Bennett wrote: > On 27/06/2011, at 10:07 PM, Spencer Oliver wrote: > > On 27 June 2011 11:05, Spencer Oliver wrote: > >> Thanks that solves all the problems i see with make distcheck. >> At some point i may look into a method of tweaking so we do not install >> unnecessary files, but all is good for the next openocd release. >> >> Cheers >> Spen >> > > Spoke to soon :) > jimtcl head now fails to build under cygwin - ok under linux. > > After a full distclean i then get a segfault > === configuring in jimtcl (/home/soliver/openocd/openocd-inline/jimtcl) > configure: running /bin/sh ./configure.gnu --disable-option-checking > '--prefix=/usr/local' '--enable-maintainer-mode' '--disable-shared' > '--disable-werror' '--enable-parport' '--enable-jlink' '--enable-rlink' > '--enable-ft2232_ftd2xx' 'CFLAGS=-O0 -g' --cache-file=/dev/null --srcdir=. > No installed jimsh or tclsh, building local bootstrap jimsh0 > ./configure.gnu: line 2: 2392 Segmentation fault (core dumped) $SHELL > .././jimtcl/configure --with-jim-ext=nvp --disable-lineedit "$@" > configure: error: ./configure.gnu failed for jimtcl > > The issue was introduced in commit f25d6276ee487d583e35c48f3125ef388c9f7d3f > > > Try latest git. You will need to remove the old autosetup/jimsh0.exe > > Steve, Another small observation cygwin does includes tclsh - tclsh.exe and tclsh84.exe Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 27 June 2011 22:33, Steve Bennett wrote: > On 27/06/2011, at 10:07 PM, Spencer Oliver wrote: > > On 27 June 2011 11:05, Spencer Oliver wrote: > >> Thanks that solves all the problems i see with make distcheck. >> At some point i may look into a method of tweaking so we do not install >> unnecessary files, but all is good for the next openocd release. >> >> Cheers >> Spen >> > > Spoke to soon :) > jimtcl head now fails to build under cygwin - ok under linux. > > After a full distclean i then get a segfault > === configuring in jimtcl (/home/soliver/openocd/openocd-inline/jimtcl) > configure: running /bin/sh ./configure.gnu --disable-option-checking > '--prefix=/usr/local' '--enable-maintainer-mode' '--disable-shared' > '--disable-werror' '--enable-parport' '--enable-jlink' '--enable-rlink' > '--enable-ft2232_ftd2xx' 'CFLAGS=-O0 -g' --cache-file=/dev/null --srcdir=. > No installed jimsh or tclsh, building local bootstrap jimsh0 > ./configure.gnu: line 2: 2392 Segmentation fault (core dumped) $SHELL > .././jimtcl/configure --with-jim-ext=nvp --disable-lineedit "$@" > configure: error: ./configure.gnu failed for jimtcl > > The issue was introduced in commit f25d6276ee487d583e35c48f3125ef388c9f7d3f > > > Try latest git. You will need to remove the old autosetup/jimsh0.exe > > > Many Thanks again, that seems to fix the build (for cygwin and mingw) - i will try functional testing later today. One observation is that jimsh0 is built in the src dir, perhaps it would be better to use the builddir. I tend to build out of tree for various arch's and having jimsh0 built in the src dir does create issues for this kind of setup. Also it would be good if a distclean removed jimsh0 as it is generated by configure. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
> Try latest git. You will need to remove the old autosetup/jimsh0.exe It's a good idea to run 'git clean -f -d -x' prior to running autotools and friends. This will erase all files and directories that aren't under revision control. Regards, Dimitar ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 27/06/2011, at 10:07 PM, Spencer Oliver wrote: > On 27 June 2011 11:05, Spencer Oliver wrote: > Thanks that solves all the problems i see with make distcheck. > At some point i may look into a method of tweaking so we do not install > unnecessary files, but all is good for the next openocd release. > > Cheers > Spen > > Spoke to soon :) > jimtcl head now fails to build under cygwin - ok under linux. > > After a full distclean i then get a segfault > === configuring in jimtcl (/home/soliver/openocd/openocd-inline/jimtcl) > configure: running /bin/sh ./configure.gnu --disable-option-checking > '--prefix=/usr/local' '--enable-maintainer-mode' '--disable-shared' > '--disable-werror' '--enable-parport' '--enable-jlink' '--enable-rlink' > '--enable-ft2232_ftd2xx' 'CFLAGS=-O0 -g' --cache-file=/dev/null --srcdir=. > No installed jimsh or tclsh, building local bootstrap jimsh0 > ./configure.gnu: line 2: 2392 Segmentation fault (core dumped) $SHELL > .././jimtcl/configure --with-jim-ext=nvp --disable-lineedit "$@" > configure: error: ./configure.gnu failed for jimtcl > > The issue was introduced in commit f25d6276ee487d583e35c48f3125ef388c9f7d3f Try latest git. You will need to remove the old autosetup/jimsh0.exe Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 27/06/2011, at 10:07 PM, Spencer Oliver wrote: > On 27 June 2011 11:05, Spencer Oliver wrote: > Thanks that solves all the problems i see with make distcheck. > At some point i may look into a method of tweaking so we do not install > unnecessary files, but all is good for the next openocd release. > > Cheers > Spen > > Spoke to soon :) > jimtcl head now fails to build under cygwin - ok under linux. > > After a full distclean i then get a segfault > === configuring in jimtcl (/home/soliver/openocd/openocd-inline/jimtcl) > configure: running /bin/sh ./configure.gnu --disable-option-checking > '--prefix=/usr/local' '--enable-maintainer-mode' '--disable-shared' > '--disable-werror' '--enable-parport' '--enable-jlink' '--enable-rlink' > '--enable-ft2232_ftd2xx' 'CFLAGS=-O0 -g' --cache-file=/dev/null --srcdir=. > No installed jimsh or tclsh, building local bootstrap jimsh0 > ./configure.gnu: line 2: 2392 Segmentation fault (core dumped) $SHELL > .././jimtcl/configure --with-jim-ext=nvp --disable-lineedit "$@" > configure: error: ./configure.gnu failed for jimtcl > > The issue was introduced in commit f25d6276ee487d583e35c48f3125ef388c9f7d3f Thanks. Will investigate. -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 27 June 2011 11:05, Spencer Oliver wrote: > Thanks that solves all the problems i see with make distcheck. > At some point i may look into a method of tweaking so we do not install > unnecessary files, but all is good for the next openocd release. > > Cheers > Spen > Spoke to soon :) jimtcl head now fails to build under cygwin - ok under linux. After a full distclean i then get a segfault === configuring in jimtcl (/home/soliver/openocd/openocd-inline/jimtcl) configure: running /bin/sh ./configure.gnu --disable-option-checking '--prefix=/usr/local' '--enable-maintainer-mode' '--disable-shared' '--disable-werror' '--enable-parport' '--enable-jlink' '--enable-rlink' '--enable-ft2232_ftd2xx' 'CFLAGS=-O0 -g' --cache-file=/dev/null --srcdir=. No installed jimsh or tclsh, building local bootstrap jimsh0 ./configure.gnu: line 2: 2392 Segmentation fault (core dumped) $SHELL .././jimtcl/configure --with-jim-ext=nvp --disable-lineedit "$@" configure: error: ./configure.gnu failed for jimtcl The issue was introduced in commit f25d6276ee487d583e35c48f3125ef388c9f7d3f Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 21 June 2011 07:44, Spencer Oliver wrote: > > > > Try this: > http://repo.or.cz/w/jimtcl.git/commit/fbc998db178da5c462e164b63da128a7d7412e37 > > > > With your recent changes, now 'make distcheck' works for me. > > > > Many thanks :-) > > I am away on holiday at the moment so will not get time to look at this > again until next week. > > Cheers > Spen > Steve, Thanks that solves all the problems i see with make distcheck. At some point i may look into a method of tweaking so we do not install unnecessary files, but all is good for the next openocd release. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
> > Try this: http://repo.or.cz/w/jimtcl.git/commit/fbc998db178da5c462e164b63da128a7d7412e37 > > With your recent changes, now 'make distcheck' works for me. > Many thanks :-) I am away on holiday at the moment so will not get time to look at this again until next week. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 19/06/2011, at 4:59 PM, Steve Bennett wrote: > On 17/06/2011, at 6:51 PM, Spencer Oliver wrote: > >> On 17 June 2011 01:11, Steve Bennett wrote: >> >> Yes, you're right. Try the attached patch. >> >> make distcheck mostly works for me, but the build fails for reasons which is >> nothing >> to do with jimtcl. Not sure if there are any more problems after this point. >> Does this work for you? >> >> >> Steve, >> >> Many thanks, that solves that problem :) >> I am just about to push some fixes to the openocd side of distcheck, this >> still leaves an issue with distcheck - attached log. >> >> The issue is related to the install part of distcheck, to be honest we do >> not really need to install jim as we use it inline. >> Can you think of a way of telling jim to not install - perhaps a configure >> option (--noinstall) that replaces the default install with a blank handler > > May be easiest to just add an uninstall target. > I'll take a look. Try this: http://repo.or.cz/w/jimtcl.git/commit/fbc998db178da5c462e164b63da128a7d7412e37 With your recent changes, now 'make distcheck' works for me. Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 17/06/2011, at 6:51 PM, Spencer Oliver wrote: > On 17 June 2011 01:11, Steve Bennett wrote: > > Yes, you're right. Try the attached patch. > > make distcheck mostly works for me, but the build fails for reasons which is > nothing > to do with jimtcl. Not sure if there are any more problems after this point. > Does this work for you? > > > Steve, > > Many thanks, that solves that problem :) > I am just about to push some fixes to the openocd side of distcheck, this > still leaves an issue with distcheck - attached log. > > The issue is related to the install part of distcheck, to be honest we do not > really need to install jim as we use it inline. > Can you think of a way of telling jim to not install - perhaps a configure > option (--noinstall) that replaces the default install with a blank handler May be easiest to just add an uninstall target. I'll take a look. Cheers, Steve > > cc'd the list again as it must have got removed. > > Cheers > Spen > -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Spencer Oliver scrisse: > The solution as mentioned is to either get the user to download jim > and install in the jimtcl dir of openocd or we tweak jim to work with > make dist. I have been making a few tweaks and got it working, but it > is a bodge - life would be simpler if automake was used in jimtcl :) Given that jimctl is a third-party package, IMHO its hypothetical "dist" target won't work anyway (wouldn't it just create a tarball-in-tarball?). I think you really need something along the line of the following patch. Let me know if it works for your "make dist" needs (after a fresh autotool-ization), if so I can cook a proper git commit out of it. Cheers, Luca diff --git a/Makefile.am b/Makefile.am index b31bcea..5187f7b 100644 - --- a/Makefile.am +++ b/Makefile.am @@ -18,6 +18,7 @@ endif SUBDIRS += src doc EXTRA_DIST = \ + jimtcl \ Doxyfile.in \ tools/logger.pl - -- .''`. ** Debian GNU/Linux ** | Luca Bruno (kaeso) : :' : The Universal O.S.| lucab (AT) debian.org `. `'` | GPG Key ID: 3BFB9FB3 `- http://www.debian.org | Debian GNU/Linux Developer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk36hOwACgkQRqobajv7n7PQ8ACgsWIL8i0NjGj7yPHFDeIo3fq+ vSMAnjX5Zm4nYdUrFl8O+ohipIB40+QY =rH3O -END PGP SIGNATURE- ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 16 June 2011 13:02, Steve Bennett wrote: > Hmmm. Works for me. Can you send me first few lines of git log in the > jimtcl dir and also the output of make distcheck? And also jimtcl/Makefile > > Cheers, > Steve > I think there is some confusion again. openocd and jimtcl build ok - even after updating to jimtcl git master. The problem is when make distcheck is run at top level. jim has dummy calls for dist/distcheck and because of that the openocd tarball will have an empty jimtcl dir. So running make distcheck from the openocd dir will fail - it has been like this since we started using jim as a submodule. The solution as mentioned is to either get the user to download jim and install in the jimtcl dir of openocd or we tweak jim to work with make dist. I have been making a few tweaks and got it working, but it is a bodge - life would be simpler if automake was used in jimtcl :) Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
Hmmm. Works for me. Can you send me first few lines of git log in the jimtcl dir and also the output of make distcheck? And also jimtcl/Makefile Cheers, Steve On 16/06/2011, at 6:33 PM, Spencer Oliver wrote: > On 16 June 2011 05:38, Steve Bennett wrote: > On 16/06/2011, at 7:49 AM, Spencer Oliver wrote: > >> >> On Jun 15, 2011 10:30 PM, "Øyvind Harboe" wrote: >> > >> > I think we should stick to distributing source packages only. >> > >> >> That's my plan >> - even that is not easy as Jim does not use autoconf etc. >> >> > > That sounds like an easy problem to fix. > Try the latest version of Jim. > I've added: > http://repo.or.cz/w/jimtcl.git/commit/142edb4e35a90c316564ec1aacf6dde9ec5861cb > > This should mean that 'make distcheck' works, but let me know if it doesn't. > > > Steve, > > I have just updated to latest jimtcl master in my local repo. > make distcheck still fails - this is because openocd expects jimtrcl to be in > its src dist archive. > This will not happen because jim does not create a distribution when make > dist is called. > > I personally want to release the openocd src and jimtcl src as one archive > that the use can just build. > This is always a problem when using submodules that doe not fully comply with > the automake stuff. > > The solution seems to be to get jim to create a src release when make dist in > called at top level. > Another option is to manually copy the jimtcl src into the openocd > distribution - but that is not very gnu and may put of packagers fir the > various linux distributions. > > Cheers > Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 16 June 2011 05:38, Steve Bennett wrote: > On 16/06/2011, at 7:49 AM, Spencer Oliver wrote: > > > On Jun 15, 2011 10:30 PM, "Øyvind Harboe" wrote: > > > > I think we should stick to distributing source packages only. > > > > That's my plan > - even that is not easy as Jim does not use autoconf etc. > > > That sounds like an easy problem to fix. > Try the latest version of Jim. > I've added: > http://repo.or.cz/w/jimtcl.git/commit/142edb4e35a90c316564ec1aacf6dde9ec5861cb > > This should mean that 'make distcheck' works, but let me know if it > doesn't. > > Steve, I have just updated to latest jimtcl master in my local repo. make distcheck still fails - this is because openocd expects jimtrcl to be in its src dist archive. This will not happen because jim does not create a distribution when make dist is called. I personally want to release the openocd src and jimtcl src as one archive that the use can just build. This is always a problem when using submodules that doe not fully comply with the automake stuff. The solution seems to be to get jim to create a src release when make dist in called at top level. Another option is to manually copy the jimtcl src into the openocd distribution - but that is not very gnu and may put of packagers fir the various linux distributions. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On 16/06/2011, at 7:49 AM, Spencer Oliver wrote: > > On Jun 15, 2011 10:30 PM, "Øyvind Harboe" wrote: > > > > I think we should stick to distributing source packages only. > > > > That's my plan > - even that is not easy as Jim does not use autoconf etc. > > That sounds like an easy problem to fix. Try the latest version of Jim. I've added: http://repo.or.cz/w/jimtcl.git/commit/142edb4e35a90c316564ec1aacf6dde9ec5861cb This should mean that 'make distcheck' works, but let me know if it doesn't. Cheers, Steve -- µWeb: Embedded Web Framework - http://uweb.workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On Jun 15, 2011 10:30 PM, "Øyvind Harboe" wrote: > > I think we should stick to distributing source packages only. > That's my plan - even that is not easy as Jim does not use autoconf etc. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On Wed, Jun 15, 2011 at 9:30 PM, Øyvind Harboe wrote: > I think we should stick to distributing source packages only. > > For the source package, we can include the version of Jim Tcl we > tested with. > > If someone wants something else, they can start with cloning > the openocd repository and checking out the release tag? Agree. Submodules should stay submodules, as there will be even more of them in future (libswd for innstance). The OpenOCD src distro can have tag/branch set to download specific submodules (I have created separate branch v0.2 for libswd to be included into openocd)... The other thing is a binary release as building submodules produces some dynamic components (that can possibly overwrite existing ones..?) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
I think we should stick to distributing source packages only. For the source package, we can include the version of Jim Tcl we tested with. If someone wants something else, they can start with cloning the openocd repository and checking out the release tag? -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On Jun 15, 2011 10:10 PM, "Tomek CEDRO" wrote: > > Hello Spencer :-) > > I would use git submodule and simply include JimTCL with OpenOCD build > binary. This would save lots of problems and produce common > distribution. Anyone who want to use external library can build > his/her own binary. Ofcourse there is a situation to solve what to to > when JimTCL is already installed on the system... > > However in future it would be nice to select library at runtime somehow.. > I may have not explained clearly enough. This has nothing todo with binaries but the src release of openocd. Previously it was not an issue as openocd src release contained Jim. Now that we are using Jim as a sub module means that when we create a src release using 'make dist' then by default the Jim src is not included. We have the option of leaving as is and the user will have to download and build Jim or we include the tested version of Jim with the openocd src release. The issue with the user having to build Jim is that they may end up using an untested verson. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
Hello Spencer :-) I would use git submodule and simply include JimTCL with OpenOCD build binary. This would save lots of problems and produce common distribution. Anyone who want to use external library can build his/her own binary. Ofcourse there is a situation to solve what to to when JimTCL is already installed on the system... However in future it would be nice to select library at runtime somehow.. Best regards! Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On Jun 15, 2011 8:08 PM, "Øyvind Harboe" wrote: > > On Wed, Jun 15, 2011 at 9:01 PM, Spencer Oliver wrote: > > The main thing that needs fixing is the issue with how to release the Jim > > tcl lib. > > Currently a make distcheck will fail due the Jim lib. > > > > Previously Jim was integrated and this made releases simpler - now we have > > to decide whether to leave it seperate or release the Jim src with openocd > > release package. > > > > I think we need to release as one package with the Jim lib included - I will > > look into a way of doing this. > > > > Any other thoughts ? > > FYI, Edgar Grimberg wrote a debian package for Jim Tcl. > Would not help windoze users who are probably the majority. I will look into the various options, just thought I would see what the general consensus was. Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Openocd release known issues
On Wed, Jun 15, 2011 at 9:01 PM, Spencer Oliver wrote: > The main thing that needs fixing is the issue with how to release the Jim > tcl lib. > Currently a make distcheck will fail due the Jim lib. > > Previously Jim was integrated and this made releases simpler - now we have > to decide whether to leave it seperate or release the Jim src with openocd > release package. > > I think we need to release as one package with the Jim lib included - I will > look into a way of doing this. > > Any other thoughts ? FYI, Edgar Grimberg wrote a debian package for Jim Tcl. -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] Openocd release known issues
The main thing that needs fixing is the issue with how to release the Jim tcl lib. Currently a make distcheck will fail due the Jim lib. Previously Jim was integrated and this made releases simpler - now we have to decide whether to leave it seperate or release the Jim src with openocd release package. I think we need to release as one package with the Jim lib included - I will look into a way of doing this. Any other thoughts ? Cheers Spen ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
