Re: Preview: kitgen builds Tclkit Lite
Jean-Claude Wippler <[email protected]>
| Newsgroups | gmane.comp.lang.tcl.starkit |
|---|---|
| Message-ID | <[email protected]> |
Brian Theado wrote: > On 11/19/06, Jean-Claude Wippler <[email protected]> wrote: >> It's all very lightweight (read: maintainable). I don't have access >> to a mingw build setup right now, but I hope that kitgen can be >> tweaked to work there as well. > > I made some tweaks that got me pretty far. I'm currently stuck on the > kit-cli linking stage. All Tcl library calls in the kit C files > (kitInit.c, pwb.c, etc.) are showing up as undefined references. For > some reason, the .o files have references to things like > '_imp__Tcl_GetByteArrayFromObj' whereas 'nm libtcl84s.a' shows symbols > like '_Tcl_GetByteArrayFromObj '. Sounds like lib/dll trouble. Could it be that the last compile/build step (of kitInit.c etc) needs a -DSTATIC_BUILD? If that's not it, I'd consider looking at EXTERN and things like __declspec. You might also be able to glean some settings from the tcl make which builds a static tclsh as one of the first kitgen steps. (FWIW, I had some trouble with a threaded X11 build on Mac, no doubt that last link step is still a bit too simplistic) > Here are my steps: [...] Wow. Once it all works, it'd be great to get all this information linked-from or included-in the kitgen docs. <snip> > make 8.4-cvs > ==> 'wget -O -' doesn't seem to work properly and the 'tar x' fails Hm. Perhaps because Win32 pipes assume that text-mode data passes through? > make small > ==> Linking step in kit-cli target fails with a bunch of undefined > reference errors. Great. Almost there! -jcw