RE: input line is too long

["Erik Poupaert" <erik dot poupaert at chello dot be>]

Hi

>>> 1. Create an exports definition file:
    dlltool --output-def bar.def foo.o
>>> 2. Generate an export file from this:
    dlltool --dllname snafu.exe --output-exp foobar.exp --def bar.def
>>> 3. Link in to create the final executable:
    gcc -o snafu.exe foobar.exp foo.o wombat.o

In principle it works!

In this case, however, dlltool fails to grab and expose symbols from the
VC.NET generated object files. It only lists symbols from callback.obj,
because I compiled that one with gcc. Some truly ugly duct tape implies that
structs.c, swt.c, and swtole.c must be compiled with VC.NET while callback.c
must be compiled with gcc.

But then again, linking with the VC.NET generated swt-win32-2122.exp, does
do the trick:

gcj -s -mwindows -fCLASSPATH=cls HelloWorld1.java libswtwin32.a  *.obj
*.exp -o
hello.exe --main=HelloWorld1 -lole32 -lcomctl32 -luser32 -lgdi32 -lcomdlg32 
-lkernel32 -lshell32 -ladvapi32 -limm32 -lwinspool -loleaut32

Probably, all the swt native sources will compile with gcc, when they add
support for all these 'CHEVRONREBAR' things.

Thanks
Erik