[Fwd: [Starkit] starkit & mingw]

[Jean-Claude Wippler]

Jim Hinds wrote:

>  Most of the link problems go away if the 'mk' module is compiled with  
> the 'STATIC_BUILD' macro defined for the mk4tcl step.  Otherwise, the  
> windows default is to grab the tcl API stuff from some .dll.  When  
> building starkits (with tcl and tk statically linked in) the names get  
> mangled from Tcl_EvalObjEx to _imp__Tcl_EvalObjEx, for example.
>
> The current CVS sources for mk do NOT have STATIC_BUILD in any of the  
> config or make mechanism.  I found the 'most convenient' place to  
> splice this macro into the build was in the 'mk wing of the genkit  
> build:
>
>   mk {
>     config mk/unix --with-tcl=$S/tcl/generic --disable-shared
>        run sh -c "CXX=\"g++ -DSTATIC_BUILD\" $X(make) -e libmk4tcl.la"
>   }
>
> I tried other ways to do this (via the env array) but mingw doesn't  
> export properly under windows.

Hm... weird that this never has been a problem before.  I build tclkit  
for windows myself using MSVC6.  Could this be added permanently to all  
builds of genkit?

> PS I'm still working on the 'Init_dde' unresolved referance.

That means the DDE extension was not linked in - it probably has to do  
with the same reason: that I never used genkit with Windows (dde and  
registry are windows-specific - both are part of Tcl itself).

> is there a way to build tclkit on a win2000 using mingw?
> Or some other envoronment *except* MSVC6?

Google for dqkit - or go here:
	http://sourceforge.net/project/showfiles.php? 
group_id=65692&package_id=105324

AFAIK it was built with mingw, and all sources and build scripts are  
included.

> I need a patched tk Version of tclkit-win32.upx.exe.

-jcw