(dsssl) building OSP 1.5 /OpenJade 1.3.2

[Ron Ross <ronross@xxxxxxxxx>]

Hi,

Thanks to all who made this release possible.

I've built the lastest OSP/OpenJade without problems (except for a minor
nit-pick[1]) on Gnu/linux (Slackware 8.1, gcc 2.95.3), but would
appreciate some tips on building this release with Gnu tools on the
Windows 9x platform (is it in fact possible?). With the MinGW edition of
gcc 3.2 and Cygwin shell and file utilities, I've tried to do a straight
`./configure' / `make' / `make install' in the top level directory of
OpenSP-1.5 source package.

After creating ./lib/libosp.a (could I have renamed this libosp.dll or
Osplib.dll?), compilation failed while linking the later into the build
of onsgmls.exe:

--- output --
g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../generic     -g -O2 -c -o nsgmls_inst.o `test -f nsgmls_inst.cxx || echo './'`nsgmls_inst.cxx
C:/cygwin/bin/sh.exe ../libtool --mode=link g++  -g -O2   -o onsgmls.exe  nsgmls.o SgmlsEventHandler.o RastEventHandler.o StringSet.o nsgmls_inst.o ../lib/libosp.la 
mkdir .libs
g++ -g -O2 -o onsgmls.exe nsgmls.o SgmlsEventHandler.o RastEventHandler.o StringSet.o nsgmls_inst.o  ../lib/.libs/libosp.a
../lib/.libs/libosp.a(CodingSystemKit.o): In function `ZN6OpenSP19CodingSystemKitImplC2EPKNS_21TranslateCodingSystem4DescE':
c:/Gambol/dev/OpenSP-1.5/lib/CodingSystemKit.cxx:355: undefined reference to `OpenSP::Win32CodingSystem::Win32CodingSystem(OpenSP::Win32CodingSystem::SpecialCodePage, unsigned)'
c:/Gambol/dev/OpenSP-1.5/lib/CodingSystemKit.cxx:355: undefined reference to `OpenSP::Win32CodingSystem::Win32CodingSystem(OpenSP::Win32CodingSystem::SpecialCodePage, unsigned)'
../lib/.libs/libosp.a(CodingSystemKit.o): In function `ZN6OpenSP19CodingSystemKitImplC1EPKNS_21TranslateCodingSystem4DescE':
c:/Gambol/dev/OpenSP-1.5/lib/CodingSystemKit.cxx:355: undefined reference to `OpenSP::Win32CodingSystem::Win32CodingSystem(OpenSP::Win32CodingSystem::SpecialCodePage, unsigned)'
c:/Gambol/dev/OpenSP-1.5/lib/CodingSystemKit.cxx:355: undefined reference to `OpenSP::Win32CodingSystem::Win32CodingSystem(OpenSP::Win32CodingSystem::SpecialCodePage, unsigned)'
make[3]: *** [onsgmls.exe] Error 1
make[3]: Leaving directory `c:/Gambol/dev/OpenSP-1.5/nsgmls'
c:\MINGW\BIN\make.exe[2]: *** [all] Error 2
c:\MINGW\BIN\make.exe[2]: Leaving directory `c:/Gambol/dev/OpenSP-1.5/nsgmls'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `c:/Gambol/dev/OpenSP-1.5'
c:\MINGW\BIN\make.exe: *** [all] Error 2
-- end of output ---

My comprehension of compilation processes in general and of
cross-platform issues in particular is a little rudimentary, and my
approach is perhaps a little naive. But I'm willing to slug through
trial and error, given a few pointers and some indication that it is in
fact possible to build OSP/OJ on my system (Win98se, Mingw-gcc-3.2,
Cygwin bash, etc.).

Of course, if someone has already compiled a win32 version and makes the
package available, I won't spend too much time making my own.

[1] On Gnu/linux, I noticed in both this release and in previous ones
that no matter what I disable or enable in terms of shared and static
linking, both the executables and the libraries created are *huge* -
libosp.a comes out at well over 20Mb and onsgmls at at over 1Mb. Setting
CFLAGS and CXXFLAGS to "-s -O3 -march=i686" ("-s" for stripping) does
bring resulting file sizes down to much more modest levels. Is that just
the way it is, or should I take something else into account?

All the best,
Ron


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