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