Re: OpenJade 1.3 Released

[Carlos Villegas <cav@xxxxxxxxxxxxxx>]

Toby Speight wrote:

> What about Cygwin systems?  Is it worth trying to compile and build
> Jade on a Cygwin platform, or are there platform specifics in the way?
> (I don't really have the time or expertise to debug the build process.
> (Portable) C code maybe, but not Windows builds!)

I've been able to compile jade with the latest gcc2.95 for mingw32
(which means cygwin is also supported).
However, gcc is still buggy in the __declspec(dllexport/dllimport)
support. I got around by exporting all symbols from the DLL. And
it worked, however creating the import library takes about
1 and half hours on my machine (Pentium 200/64Mb) :-(. It looks
like dlltool generates an object file for each exported symbol
and later links all object files! The time it's ok for up to
2 to 3 thousands symbols, but it grows dramatically for the
8,000+ symbols of SP. If __declspec(dllexport) worked properly,
that's about 3,000 symbols which gives a reasonable linking
time. But I get unresolved symbols when linking any of the
applications. I haven't checked the gcc mailing lists and
news groups, there may be some work-arounds or fixes.
I've been tracking egcs/gcc for win32 and
2.95 is the first one able to compile SP as a DLL. Previous
versions generated duplicate Constructor/Destructors and had
other problems. I basically used the settings for gcc in
config.h plus copied some definitions from MSVC section.
I'll keep an eye on the win32 port of gcc and when it gets
reasonable, I'll publish the results. 
If someone is interested I can provide my setup and building
system.

Carlos Villegas
Uniscope, Inc.


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist