openocd-devel

[Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Øyvind H. <oyv...@zy...>]

OpenOCD master branch now uses Jim Tcl.

This means you'll have to build Jim Tcl before building OpenOCD.

bootstrap prints the instructions:

git submodule init
git submodule update
cd jimtcl
./configure --with-jim-ext=nvp
make
make install


>From the OpenOCD command line you can determine
the version of Jim Tcl you're running by typing =>

> info version
0.63


(It used to be 0.53)

-- 
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Peter S. <pe...@st...>]

Øyvind Harboe wrote:
> OpenOCD master branch now uses Jim Tcl.
> 
> This means you'll have to build Jim Tcl before building OpenOCD.

Is there also an upstream for Jim Tcl to make distribution packages
from?

Or is Jim Tcl only ever statically linked with OpenOCD?


//Peter

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Øyvind H. <oyv...@zy...>]

On Sun, Oct 31, 2010 at 5:53 PM, Peter Stuge <pe...@st...> wrote:
> Øyvind Harboe wrote:
>> OpenOCD master branch now uses Jim Tcl.
>>
>> This means you'll have to build Jim Tcl before building OpenOCD.
>
> Is there also an upstream for Jim Tcl to make distribution packages
> from?
>
> Or is Jim Tcl only ever statically linked with OpenOCD?

Statically linked, no change there.



-- 
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Peter S. <pe...@st...>]

Øyvind Harboe wrote:
> > Is there also an upstream for Jim Tcl to make distribution packages
> > from?
> >
> > Or is Jim Tcl only ever statically linked with OpenOCD?
> 
> Statically linked, no change there.

Ok. Has Jim Tcl ever been packaged independently? Is it "our" project
as well?


//Peter

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Øyvind H. <oyv...@zy...>]

On Sun, Oct 31, 2010 at 6:26 PM, Peter Stuge <pe...@st...> wrote:
> Øyvind Harboe wrote:
>> > Is there also an upstream for Jim Tcl to make distribution packages
>> > from?
>> >
>> > Or is Jim Tcl only ever statically linked with OpenOCD?
>>
>> Statically linked, no change there.
>
> Ok. Has Jim Tcl ever been packaged independently? Is it "our" project
> as well?

It's designed to be statically linked with applications, which means
that packaging is not as important as for your typical module
that is used in e.g. embedded Linux.

It's not our project, but I'm a maintainer of Jim Tcl, but I hope to sit
on the sideline now that Steve Bennet has stepped up. He knows
a LOT more about Tcl than I do and has really cleaned up lots of
stuff in Jim Tcl.


-- 
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Marek V. <mar...@gm...>]

On Sunday 31 October 2010 18:37:33 Øyvind Harboe wrote:
> On Sun, Oct 31, 2010 at 6:26 PM, Peter Stuge <pe...@st...> wrote:
> > Øyvind Harboe wrote:
> >> > Is there also an upstream for Jim Tcl to make distribution packages
> >> > from?
> >> > 
> >> > Or is Jim Tcl only ever statically linked with OpenOCD?
> >> 
> >> Statically linked, no change there.
> > 
> > Ok. Has Jim Tcl ever been packaged independently? Is it "our" project
> > as well?
> 
> It's designed to be statically linked with applications, which means
> that packaging is not as important as for your typical module
> that is used in e.g. embedded Linux.
> 
> It's not our project, but I'm a maintainer of Jim Tcl, but I hope to sit
> on the sideline now that Steve Bennet has stepped up. He knows
> a LOT more about Tcl than I do and has really cleaned up lots of
> stuff in Jim Tcl.

Well this is weird ... won't it be better compile both jimtcl and openocd with 
single ./configure and make, without needing to install that stuff separatelly ?

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Spencer O. <sp...@sp...>]

On 01/11/2010 00:48, Marek Vasut wrote:
> On Sunday 31 October 2010 18:37:33 Øyvind Harboe wrote:
>> On Sun, Oct 31, 2010 at 6:26 PM, Peter Stuge<pe...@st...>  wrote:
>>> Øyvind Harboe wrote:
>>>>> Is there also an upstream for Jim Tcl to make distribution packages
>>>>> from?
>>>>>
>>>>> Or is Jim Tcl only ever statically linked with OpenOCD?
>>>>
>>>> Statically linked, no change there.
>>>
>>> Ok. Has Jim Tcl ever been packaged independently? Is it "our" project
>>> as well?
>>
>> It's designed to be statically linked with applications, which means
>> that packaging is not as important as for your typical module
>> that is used in e.g. embedded Linux.
>>
>> It's not our project, but I'm a maintainer of Jim Tcl, but I hope to sit
>> on the sideline now that Steve Bennet has stepped up. He knows
>> a LOT more about Tcl than I do and has really cleaned up lots of
>> stuff in Jim Tcl.
>
> Well this is weird ... won't it be better compile both jimtcl and openocd with
> single ./configure and make, without needing to install that stuff separatelly ?

I tend to agree with this, and have a working implementation of it:
http://repo.or.cz/w/openocd/ntfreak.git/shortlog/refs/heads/jimtcl

The build system in jim will need updating as its a bit of a hack but 
can be made to work.

As a side not the current "make install" will not install to the correct 
dirs, so using AC_CONFIG_SUBDIRS solves all this.

Cheers
Spen

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Spencer O. <sp...@sp...>]

> As a side not the current "make install" will not install to the correct
> dirs, so using AC_CONFIG_SUBDIRS solves all this.
>

I mean under windoze install :)

Cheers
Spen

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Peter S. <pe...@st...>]

Marek Vasut wrote:
> won't it be better compile both jimtcl and openocd with single
> ./configure and make, without needing to install that stuff
> separatelly ?

It doesn't need to be installed, that's part of the point.

Although I'm thinking about if it might make sense to package it
anyway. I guess it's like a library.


//Peter

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Marek V. <mar...@gm...>]

On Monday 01 November 2010 01:50:19 Peter Stuge wrote:
> Marek Vasut wrote:
> > won't it be better compile both jimtcl and openocd with single
> > ./configure and make, without needing to install that stuff
> > separatelly ?
> 
> It doesn't need to be installed, that's part of the point.

In my case, openocd chokes if I don't install it ... that's my point.
> 
> Although I'm thinking about if it might make sense to package it
> anyway. I guess it's like a library.
> 
> 
> //Peter
> _______________________________________________
> Openocd-development mailing list
> Ope...@li...
> https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Laurent G. <lau...@am...>]

>
> >/ won't it be better compile both jimtcl and openocd with single
> />/ ./configure and make, without needing to install that stuff
> />/ separatelly ?
> /
> It doesn't need to be installed, that's part of the point.
>
> Although I'm thinking about if it might make sense to package it
> anyway. I guess it's like a library.
>   

I tried to compile openocd under cygwin, it failed .

What to do on cygwin, to get Jim TCL and to be able to compile openocd.

Before providing this kind of patch, we should write doc and "how-to" 
compile !!!

OpenOCD community will receive a lot of new messages regarding 
compilation errors / troubles, if we do not give any how-to compile with 
external  JIM TCL.

Regards,
Laurent

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Peter S. <pe...@st...>]

Laurent Gauch wrote:
> OpenOCD community will receive a lot of new messages regarding
> compilation errors / troubles, if we do not give any how-to compile
> with external  JIM TCL.

Please contribute documentation.


//Peter

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Laurent G. <lau...@am...>]

under Cygwin with external JIM TCL 0.63 in ./openocd/jimtcl, the make 
error is :

../../../src/helper/command.h:34:17: jim.h: No such file or directory

> checking whether standard drivers can be built... yes
> checking for ftd2xx.lib exists (win32)... checking whether ftd2xx 
> library works.
> .. Success!
> checking for ftd2xx highspeed device support... yes
> checking for environ in unistd.h and stdlib.h... yes
> checking for a C compiler for build tools... gcc -mno-cygwin -std=gnu99
> checking for suffix of executable build tools... .exe
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating src/Makefile
> config.status: creating src/helper/Makefile
> config.status: creating src/jtag/Makefile
> config.status: creating src/jtag/drivers/Makefile
> config.status: creating src/xsvf/Makefile
> config.status: creating src/svf/Makefile
> config.status: creating src/target/Makefile
> config.status: creating src/server/Makefile
> config.status: creating src/flash/Makefile
> config.status: creating src/flash/nor/Makefile
> config.status: creating src/flash/nand/Makefile
> config.status: creating src/pld/Makefile
> config.status: creating doc/Makefile
> config.status: creating config.h
> config.status: executing depfiles commands
> config.status: executing libtool commands
> make  all-recursive
> make[1]: Entering directory 
> `/cygdrive/c/amontec/openocd-builder/git/openocd'
> Making all in src
> make[2]: Entering directory 
> `/cygdrive/c/amontec/openocd-builder/git/openocd/src
> '
> cat helper/startup.tcl jtag/startup.tcl target/startup.tcl 
> flash/startup.tcl ser
> ver/startup.tcl > startup.tcl
> make  all-recursive
> make[3]: Entering directory 
> `/cygdrive/c/amontec/openocd-builder/git/openocd/src
> '
> Making all in jtag
> make[4]: Entering directory 
> `/cygdrive/c/amontec/openocd-builder/git/openocd/src
> /jtag'
> cp drivers/minidriver_imp.h minidriver_imp.h
> make  all-recursive
> make[5]: Entering directory 
> `/cygdrive/c/amontec/openocd-builder/git/openocd/src
> /jtag'
> Making all in drivers
> make[6]: Entering directory 
> `/cygdrive/c/amontec/openocd-builder/git/openocd/src
> /jtag/drivers'
> /bin/sh ../../../libtool --tag=CC   --mode=compile gcc -mno-cygwin 
> -std=gnu99 -D
> HAVE_CONFIG_H -I. -I../../..  -I../../../src -I../../../src   -g -O2 
> -I/cygdrive
> /c/amontec/jtagkey/driver/d2xx/nt -Wall -Wstrict-prototypes 
> -Wformat-security -W
> shadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align 
> -Wredundan
> t-decls -MT driver.lo -MD -MP -MF .deps/driver.Tpo -c -o driver.lo 
> driver.c
> libtool: compile:  gcc -mno-cygwin -std=gnu99 -DHAVE_CONFIG_H -I. 
> -I../../.. -I.
> ./../../src -I../../../src -g -O2 
> -I/cygdrive/c/amontec/jtagkey/driver/d2xx/nt -
> Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra 
> -Wno-unused-paramete
> r -Wbad-function-cast -Wcast-align -Wredundant-decls -MT driver.lo -MD 
> -MP -MF .
> deps/driver.Tpo -c driver.c -o driver.o
> In file included from ../../../src/helper/log.h:29,
>                  from ../../../src/jtag/jtag.h:27,
>                  from driver.c:34:
> ../../../src/helper/command.h:34:17: jim.h: No such file or directory
> ../../../src/helper/command.h:35:21: jim-nvp.h: No such file or directory

Regards,
Laurent
  http://www.amontec.com

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Steve B. <st...@wo...>]

On 03/11/2010, at 12:23 AM, Laurent Gauch wrote:

> under Cygwin with external JIM TCL 0.63 in ./openocd/jimtcl, the make error is :
> 
> ../../../src/helper/command.h:34:17: jim.h: No such file or directory

Did you forget 'make install' in ./openocd/jimtcl?

This is the symptom I see when that step is missed.

(Although as someone pointed out, it would be nice to have
 a single stage configure/build without needing to install jimtcl)

> 
>> checking whether standard drivers can be built... yes
>> checking for ftd2xx.lib exists (win32)... checking whether ftd2xx library works.
>> .. Success!
>> checking for ftd2xx highspeed device support... yes
>> checking for environ in unistd.h and stdlib.h... yes
>> checking for a C compiler for build tools... gcc -mno-cygwin -std=gnu99
>> checking for suffix of executable build tools... .exe
>> configure: creating ./config.status
>> config.status: creating Makefile
>> config.status: creating src/Makefile
>> config.status: creating src/helper/Makefile
>> config.status: creating src/jtag/Makefile
>> config.status: creating src/jtag/drivers/Makefile
>> config.status: creating src/xsvf/Makefile
>> config.status: creating src/svf/Makefile
>> config.status: creating src/target/Makefile
>> config.status: creating src/server/Makefile
>> config.status: creating src/flash/Makefile
>> config.status: creating src/flash/nor/Makefile
>> config.status: creating src/flash/nand/Makefile
>> config.status: creating src/pld/Makefile
>> config.status: creating doc/Makefile
>> config.status: creating config.h
>> config.status: executing depfiles commands
>> config.status: executing libtool commands
>> make  all-recursive
>> make[1]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd'
>> Making all in src
>> make[2]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>> '
>> cat helper/startup.tcl jtag/startup.tcl target/startup.tcl flash/startup.tcl ser
>> ver/startup.tcl > startup.tcl
>> make  all-recursive
>> make[3]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>> '
>> Making all in jtag
>> make[4]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>> /jtag'
>> cp drivers/minidriver_imp.h minidriver_imp.h
>> make  all-recursive
>> make[5]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>> /jtag'
>> Making all in drivers
>> make[6]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>> /jtag/drivers'
>> /bin/sh ../../../libtool --tag=CC   --mode=compile gcc -mno-cygwin -std=gnu99 -D
>> HAVE_CONFIG_H -I. -I../../..  -I../../../src -I../../../src   -g -O2 -I/cygdrive
>> /c/amontec/jtagkey/driver/d2xx/nt -Wall -Wstrict-prototypes -Wformat-security -W
>> shadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundan
>> t-decls -MT driver.lo -MD -MP -MF .deps/driver.Tpo -c -o driver.lo driver.c
>> libtool: compile:  gcc -mno-cygwin -std=gnu99 -DHAVE_CONFIG_H -I. -I../../.. -I.
>> ./../../src -I../../../src -g -O2 -I/cygdrive/c/amontec/jtagkey/driver/d2xx/nt -
>> Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-paramete
>> r -Wbad-function-cast -Wcast-align -Wredundant-decls -MT driver.lo -MD -MP -MF .
>> deps/driver.Tpo -c driver.c -o driver.o
>> In file included from ../../../src/helper/log.h:29,
>>                 from ../../../src/jtag/jtag.h:27,
>>                 from driver.c:34:
>> ../../../src/helper/command.h:34:17: jim.h: No such file or directory
>> ../../../src/helper/command.h:35:21: jim-nvp.h: No such file or directory
> 
> Regards,
> Laurent
> http://www.amontec.com
> 
> _______________________________________________
> Openocd-development mailing list
> Ope...@li...
> https://lists.berlios.de/mailman/listinfo/openocd-development
> 

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

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Steve B. <st...@wo...>]

On 03/11/2010, at 8:34 AM, Steve Bennett wrote:

> On 03/11/2010, at 12:23 AM, Laurent Gauch wrote:
> 
>> under Cygwin with external JIM TCL 0.63 in ./openocd/jimtcl, the make error is :
>> 
>> ../../../src/helper/command.h:34:17: jim.h: No such file or directory
> 
> Did you forget 'make install' in ./openocd/jimtcl?
> 
> This is the symptom I see when that step is missed.
> 
> (Although as someone pointed out, it would be nice to have
> a single stage configure/build without needing to install jimtcl)

Although the link step still fails for me on cygwin.

make[4]: Entering directory `/src/openocd/src'
/bin/sh ../libtool --tag=CC   --mode=link gcc -std=gnu99  -g -O2 -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -Werror   -o openocd.exe main.o libopenocd.la -ljim 
libtool: link: gcc -std=gnu99 -g -O2 -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -Werror -o openocd.exe main.o  ./.libs/libopenocd.a -ljim
/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld: cannot find -ljim
collect2: ld returned 1 exit status
make[4]: *** [openocd.exe] Error 1
make[4]: Leaving directory `/src/openocd/src'

I'm no automake expert. It seems to me that it should be possible to add include
and lib paths directly to the jimtcl directory under openocd, thus avoiding the need
to 'make install' and addressing this link problem.

> 
>> 
>>> checking whether standard drivers can be built... yes
>>> checking for ftd2xx.lib exists (win32)... checking whether ftd2xx library works.
>>> .. Success!
>>> checking for ftd2xx highspeed device support... yes
>>> checking for environ in unistd.h and stdlib.h... yes
>>> checking for a C compiler for build tools... gcc -mno-cygwin -std=gnu99
>>> checking for suffix of executable build tools... .exe
>>> configure: creating ./config.status
>>> config.status: creating Makefile
>>> config.status: creating src/Makefile
>>> config.status: creating src/helper/Makefile
>>> config.status: creating src/jtag/Makefile
>>> config.status: creating src/jtag/drivers/Makefile
>>> config.status: creating src/xsvf/Makefile
>>> config.status: creating src/svf/Makefile
>>> config.status: creating src/target/Makefile
>>> config.status: creating src/server/Makefile
>>> config.status: creating src/flash/Makefile
>>> config.status: creating src/flash/nor/Makefile
>>> config.status: creating src/flash/nand/Makefile
>>> config.status: creating src/pld/Makefile
>>> config.status: creating doc/Makefile
>>> config.status: creating config.h
>>> config.status: executing depfiles commands
>>> config.status: executing libtool commands
>>> make  all-recursive
>>> make[1]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd'
>>> Making all in src
>>> make[2]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>>> '
>>> cat helper/startup.tcl jtag/startup.tcl target/startup.tcl flash/startup.tcl ser
>>> ver/startup.tcl > startup.tcl
>>> make  all-recursive
>>> make[3]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>>> '
>>> Making all in jtag
>>> make[4]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>>> /jtag'
>>> cp drivers/minidriver_imp.h minidriver_imp.h
>>> make  all-recursive
>>> make[5]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>>> /jtag'
>>> Making all in drivers
>>> make[6]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>>> /jtag/drivers'
>>> /bin/sh ../../../libtool --tag=CC   --mode=compile gcc -mno-cygwin -std=gnu99 -D
>>> HAVE_CONFIG_H -I. -I../../..  -I../../../src -I../../../src   -g -O2 -I/cygdrive
>>> /c/amontec/jtagkey/driver/d2xx/nt -Wall -Wstrict-prototypes -Wformat-security -W
>>> shadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundan
>>> t-decls -MT driver.lo -MD -MP -MF .deps/driver.Tpo -c -o driver.lo driver.c
>>> libtool: compile:  gcc -mno-cygwin -std=gnu99 -DHAVE_CONFIG_H -I. -I../../.. -I.
>>> ./../../src -I../../../src -g -O2 -I/cygdrive/c/amontec/jtagkey/driver/d2xx/nt -
>>> Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-paramete
>>> r -Wbad-function-cast -Wcast-align -Wredundant-decls -MT driver.lo -MD -MP -MF .
>>> deps/driver.Tpo -c driver.c -o driver.o
>>> In file included from ../../../src/helper/log.h:29,
>>>                from ../../../src/jtag/jtag.h:27,
>>>                from driver.c:34:
>>> ../../../src/helper/command.h:34:17: jim.h: No such file or directory
>>> ../../../src/helper/command.h:35:21: jim-nvp.h: No such file or directory
>> 
>> Regards,
>> Laurent
>> http://www.amontec.com
>> 
>> _______________________________________________
>> Openocd-development mailing list
>> Ope...@li...
>> https://lists.berlios.de/mailman/listinfo/openocd-development
>> 
> 
> --
> µWeb: Embedded Web Framework - http://uweb.workware.net.au/
> WorkWare Systems Pty Ltd
> W: www.workware.net.au      P: 0434 921 300
> E: st...@wo...   F: 07 3102 9221
> 
> 
> 
> 
> _______________________________________________
> Openocd-development mailing list
> Ope...@li...
> https://lists.berlios.de/mailman/listinfo/openocd-development

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

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Laurent G. <lau...@am...>]

Hi Steve,

Yes, you're right.

I think we do not need to have any 'make install' for JIM TCL, since we 
want JIM TCL embedded in the openocd project.

The jim include paths and jim lib paths directly should be added in the 
'configure' of openocd.

Regards,
Laurent
  http://www.amontec.com
  USB JTAG JTAGkey Tiny .
> On 03/11/2010, at 8:34 AM, Steve Bennett wrote:
>
>   
>> On 03/11/2010, at 12:23 AM, Laurent Gauch wrote:
>>
>>     
>>> under Cygwin with external JIM TCL 0.63 in ./openocd/jimtcl, the make error is :
>>>
>>> ../../../src/helper/command.h:34:17: jim.h: No such file or directory
>>>       
>> Did you forget 'make install' in ./openocd/jimtcl?
>>
>> This is the symptom I see when that step is missed.
>>
>> (Although as someone pointed out, it would be nice to have
>> a single stage configure/build without needing to install jimtcl)
>>     
>
> Although the link step still fails for me on cygwin.
>
> make[4]: Entering directory `/src/openocd/src'
> /bin/sh ../libtool --tag=CC   --mode=link gcc -std=gnu99  -g -O2 -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -Werror   -o openocd.exe main.o libopenocd.la -ljim 
> libtool: link: gcc -std=gnu99 -g -O2 -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -Werror -o openocd.exe main.o  ./.libs/libopenocd.a -ljim
> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld: cannot find -ljim
> collect2: ld returned 1 exit status
> make[4]: *** [openocd.exe] Error 1
> make[4]: Leaving directory `/src/openocd/src'
>
> I'm no automake expert. It seems to me that it should be possible to add include
> and lib paths directly to the jimtcl directory under openocd, thus avoiding the need
> to 'make install' and addressing this link problem.
>
>   
>>>> checking whether standard drivers can be built... yes
>>>> checking for ftd2xx.lib exists (win32)... checking whether ftd2xx library works.
>>>> .. Success!
>>>> checking for ftd2xx highspeed device support... yes
>>>> checking for environ in unistd.h and stdlib.h... yes
>>>> checking for a C compiler for build tools... gcc -mno-cygwin -std=gnu99
>>>> checking for suffix of executable build tools... .exe
>>>> configure: creating ./config.status
>>>> config.status: creating Makefile
>>>> config.status: creating src/Makefile
>>>> config.status: creating src/helper/Makefile
>>>> config.status: creating src/jtag/Makefile
>>>> config.status: creating src/jtag/drivers/Makefile
>>>> config.status: creating src/xsvf/Makefile
>>>> config.status: creating src/svf/Makefile
>>>> config.status: creating src/target/Makefile
>>>> config.status: creating src/server/Makefile
>>>> config.status: creating src/flash/Makefile
>>>> config.status: creating src/flash/nor/Makefile
>>>> config.status: creating src/flash/nand/Makefile
>>>> config.status: creating src/pld/Makefile
>>>> config.status: creating doc/Makefile
>>>> config.status: creating config.h
>>>> config.status: executing depfiles commands
>>>> config.status: executing libtool commands
>>>> make  all-recursive
>>>> make[1]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd'
>>>> Making all in src
>>>> make[2]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>>>> '
>>>> cat helper/startup.tcl jtag/startup.tcl target/startup.tcl flash/startup.tcl ser
>>>> ver/startup.tcl > startup.tcl
>>>> make  all-recursive
>>>> make[3]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>>>> '
>>>> Making all in jtag
>>>> make[4]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>>>> /jtag'
>>>> cp drivers/minidriver_imp.h minidriver_imp.h
>>>> make  all-recursive
>>>> make[5]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>>>> /jtag'
>>>> Making all in drivers
>>>> make[6]: Entering directory `/cygdrive/c/amontec/openocd-builder/git/openocd/src
>>>> /jtag/drivers'
>>>> /bin/sh ../../../libtool --tag=CC   --mode=compile gcc -mno-cygwin -std=gnu99 -D
>>>> HAVE_CONFIG_H -I. -I../../..  -I../../../src -I../../../src   -g -O2 -I/cygdrive
>>>> /c/amontec/jtagkey/driver/d2xx/nt -Wall -Wstrict-prototypes -Wformat-security -W
>>>> shadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundan
>>>> t-decls -MT driver.lo -MD -MP -MF .deps/driver.Tpo -c -o driver.lo driver.c
>>>> libtool: compile:  gcc -mno-cygwin -std=gnu99 -DHAVE_CONFIG_H -I. -I../../.. -I.
>>>> ./../../src -I../../../src -g -O2 -I/cygdrive/c/amontec/jtagkey/driver/d2xx/nt -
>>>> Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-paramete
>>>> r -Wbad-function-cast -Wcast-align -Wredundant-decls -MT driver.lo -MD -MP -MF .
>>>> deps/driver.Tpo -c driver.c -o driver.o
>>>> In file included from ../../../src/helper/log.h:29,
>>>>                from ../../../src/jtag/jtag.h:27,
>>>>                from driver.c:34:
>>>> ../../../src/helper/command.h:34:17: jim.h: No such file or directory
>>>> ../../../src/helper/command.h:35:21: jim-nvp.h: No such file or directory
>>>>         
>>> Regards,
>>> Laurent
>>> http://www.amontec.com
>>>
>>> _______________________________________________
>>> Openocd-development mailing list
>>> Ope...@li...
>>> https://lists.berlios.de/mailman/listinfo/openocd-development
>>>
>>>       
>> --
>> µWeb: Embedded Web Framework - http://uweb.workware.net.au/
>> WorkWare Systems Pty Ltd
>> W: www.workware.net.au      P: 0434 921 300
>> E: st...@wo...   F: 07 3102 9221
>>
>>
>>
>>
>> _______________________________________________
>> Openocd-development mailing list
>> Ope...@li...
>> https://lists.berlios.de/mailman/listinfo/openocd-development
>>     
>
> --
> µWeb: Embedded Web Framework - http://uweb.workware.net.au/
> WorkWare Systems Pty Ltd
> W: www.workware.net.au      P: 0434 921 300
> E: st...@wo...   F: 07 3102 9221
>
>
>
>
>   

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Peter S. <pe...@st...>]

Laurent Gauch wrote:
> I think we do not need to have any 'make install' for JIM TCL,
> since we want JIM TCL embedded in the openocd project.

As you may already know, if a project uses autotools then the build
is not completed without make install.

I would suggest to set --prefix for jim to a subdir of the openocd
dir.


> The jim include paths and jim lib paths directly should be added in
> the 'configure' of openocd.

As you may already know, configure is a generated file, and nothing
should be added to it. The source for configure is configure.in. It
could assume that jim was built and installed into some default
prefix, but really, since jim is standalone, it would make sense to
me to have it installed separately in the system even if it is linked
statically into openocd.


//Peter

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Anders M. <And...@ik...>]

On Nov 3, 2010, at 11:13, Peter Stuge wrote:

> It could assume that jim was built and installed into some default
> prefix, but really, since jim is standalone, it would make sense to
> me to have it installed separately in the system even if it is linked
> statically into openocd.

Look at how GCC handles its external dependencies (MPFR etc.)

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Laurent G. <lau...@am...>]

>
> >/ I think we do not need to have any 'make install' for JIM TCL,
> />/ since we want JIM TCL embedded in the openocd project.
> /
> As you may already know, if a project uses autotools then the build
> is not completed without make install.
>
> I would suggest to set --prefix for jim to a subdir of the openocd
> dir.
>   
This is not the trouble here. Jim TCL compiles OK in openocd/jimtcl, but 
then we are not able to link jim for compiling openocd.
>
> >/ The jim include paths and jim lib paths directly should be added in
> />/ the 'configure' of openocd.
> /
> As you may already know, configure is a generated file, and nothing
> should be added to it. The source for configure is configure.in. 
sorry for my configure, I want thinking configure.in as input file.
> It
> could assume that jim was built and installed into some default
> prefix, but really, since jim is standalone, it would make sense to
> me to have it installed separately in the system even if it is linked
> statically into openocd.
>   
Yes, but having jim as standalone make a new dependency for openocd 
project :-( ! With new version control of jim TCL ...
>
> //Peter
>   

Laurent
  http://www.amontec.com

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Øyvind H. <oyv...@zy...>]

> Yes, but having jim as standalone make a new dependency for openocd project
> :-( ! With new version control of jim TCL ...

The current thinking is to have the choice of whether
to use installed Jim Tcl or have OpenOCD just build the Jim
Tcl that ships with(submodule) OpenOCD.

Release builds are another issue a bit further down the road.

-- 
Øyvind Harboe

Can Zylin Consulting help on your project?

US toll free 1-866-980-3434 / International +47 51 63 25 00

http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Laurent G. <lau...@am...>]

Øyvind Harboe wrote:
>> Yes, but having jim as standalone make a new dependency for openocd project
>> :-( ! With new version control of jim TCL ...
>>     
>
> The current thinking is to have the choice of whether
> to use installed Jim Tcl or have OpenOCD just build the Jim
> Tcl that ships with(submodule) OpenOCD.
>
> Release builds are another issue a bit further down the road.
>
>   
Having external Jim TCL is not so bad, but if we still want more and 
more users / developpers for the openocd projects, we have to make sure 
the compile step stays as easy as possible on Windows as on Linux and 
Mac ! This is not the case for the actual external Jim TCL .

As I know, the major part of the OpenOCD users build their release 
themself (they do not use any pre-build openocd binary file) And this is 
really nice in the way to have more users close to the code ... You know 
what I mean. More users / more developers / more activity / more success ...

Regards,
 Laurent
 http://www.amontec.com

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Peter S. <pe...@st...>]

Laurent Gauch wrote:
> Having external Jim TCL is not so bad,

I think it's an important improvement.


> we have to make sure the compile step stays as easy as possible on
> Windows as on Linux and Mac !

I don't agree. Windows is pretty much a useless development
environment as-is, and it's not really the task of openocd or
any other project to work around that.

MSYS and Cygwin are significantly better environments, and they work
much like a *ix systems. Big improvement, and many of the same
methods can be used across all operating systems thanks to them.


> This is not the case for the actual external Jim TCL .

When there's no package management (like on Windows) dependencies
will always mean that some extra effort and care is required to build
a package. I don't think this is a reason to keep a copy of all
dependencies within projects.

If you can help make it easier to build the two packages then please
go for it and send a patch.

Thanks!


//Peter

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Laurent G. <lau...@am...>]

>
> Laurent Gauch wrote:
> >/ Having external Jim TCL is not so bad,
> /
> I think it's an important improvement.
>
>
> >/ we have to make sure the compile step stays as easy as possible on
> />/ Windows as on Linux and Mac !
> /
> I don't agree. Windows is pretty much a useless development
> environment as-is, 
That's your point of view ... but, for me, this is a user point of view 
and not a developer point of view .
my 2c.
> and it's not really the task of openocd or
> any other project to work around that.
>   
As you say, it should not be the task of openocd developers and any 
other developer of any other software to play with OS, but having easy 
build solution for  Multi-OS (Windows / Linux  / Mac ...) is a big plus 
for the success of an open source project as the openocd.
> MSYS and Cygwin are significantly better environments, and they work
> much like a *ix systems. Big improvement, and many of the same
> methods can be used across all operating systems thanks to them.
>   
Yes, but do not confuse the "how-to" build and "how-to" use !!! We build 
openocd for Windows under Cygwin and then we use openocd binary on 
Windows without the need of Cygwin ...
>
> >/ This is not the case for the actual external Jim TCL .
> /
> When there's no package management (like on Windows) dependencies
> will always mean that some extra effort and care is required to build
> a package. I don't think this is a reason to keep a copy of all
> dependencies within projects.
>   
So why jimtcl directory in OpenOCD ?
> If you can help make it easier to build the two packages then please
> go for it and send a patch.
>
> Thanks!
>   
Thanks.

Laurent
  http://www.amontec.com 

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Peter S. <pe...@st...>]

Laurent Gauch wrote:
>> >/ we have to make sure the compile step stays as easy as possible on
>> />/ Windows as on Linux and Mac !
>> /
>> I don't agree. Windows is pretty much a useless development
>> environment as-is, 
> 
> That's your point of view ... but, for me, this is a user point of
> view and not a developer point of view .
> my 2c.

It's not about what users like to run (everyone should absolutely use
the environment they prefer) - it's about what different systems
allow in terms of a development environment, which is required to
build source code.

The Windows system that we can expect users have access to is an
incredibly limited development environment when compared to that
of Linux or MacOS X users. This matters when those users want to
do development (e.g. compile) of projects.

I think that it is important to optimize for users and to optimize
for developers, and that these two are very different things. I think
it's fine to place more requirements on developers and important to
have as few requirements as possible for users.


>> and it's not really the task of openocd or any other project to
>> work around that.
>
> As you say, it should not be the task of openocd developers and any other 
> developer of any other software to play with OS, but having easy build 
> solution for  Multi-OS (Windows / Linux  / Mac ...) is a big plus for the 
> success of an open source project as the openocd.

There exists no easy build solution for the Windows systems that
users might have access to, because such systems are so limited.

This means that working on Windows will always have more
requirements.


>> MSYS and Cygwin are significantly better environments, and they work
>> much like a *ix systems. Big improvement, and many of the same
>> methods can be used across all operating systems thanks to them.
>
> Yes, but do not confuse the "how-to" build and "how-to" use !!! We
> build openocd for Windows under Cygwin and then we use openocd
> binary on Windows without the need of Cygwin ...

Who is "we" ?

If the OpenOCD project produces some binaries then I feel strongly
that they should be built by MinGW and not using Cygwin.

It is fundamental to realise that Cygwin is not Windows. Cygwin is a
different system, running on top of Windows.


>> >/ This is not the case for the actual external Jim TCL .
>> /
>> When there's no package management (like on Windows) dependencies
>> will always mean that some extra effort and care is required to build
>> a package. I don't think this is a reason to keep a copy of all
>> dependencies within projects.
>
> So why jimtcl directory in OpenOCD ?

I agree - I think the next step is to remove the jimtcl directory and
submodule, and only have a system jimtcl. This is the goal for me,
but there's no rush.

However, going to the submodule first might make the transition
easier, since it divides the change into two steps.


//Peter

Re: [Openocd-development] OpenOCD master now uses Jim Tcl 0.63

[Spencer O. <sp...@sp...>]

On 02/11/2010 12:55, Laurent Gauch wrote:
>>
>> >/ won't it be better compile both jimtcl and openocd with single
>> />/ ./configure and make, without needing to install that stuff
>> />/ separatelly ?
>> /
>> It doesn't need to be installed, that's part of the point.
>>
>> Although I'm thinking about if it might make sense to package it
>> anyway. I guess it's like a library.
>
> I tried to compile openocd under cygwin, it failed .
>
> What to do on cygwin, to get Jim TCL and to be able to compile openocd.
>
> Before providing this kind of patch, we should write doc and "how-to"
> compile !!!
>
> OpenOCD community will receive a lot of new messages regarding
> compilation errors / troubles, if we do not give any how-to compile with
> external JIM TCL.
>

The issue is caused because jim will install into /usr/local/lib.
cygwin and mingw will only look in /usr/lib - quick solution is to 
manually move the various files.
You may also have todo this for the include files aswell.

Tweaking the install path is the better solution,eg.
./configure --with-jim-ext="nvp" --prefix=/usr

I am working on a updated build that will build jimtcl inline, so this 
will solve all problems.

Cheers
Spen