|
From: Spencer O. <sp...@sp...> - 2010-11-01 11:05:39
|
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 |