SWT in a DLL [long]

[Andrew Haley]

Andrea aime writes:
 > Andrea aime wrote:
 > > Oh, by the way,
 > > using -findirect-dispatch triggers a different error
 > > (jc1.exe eats up to 300MB or RAM and then exits with
 > > the follwing message):
 > > 
 > > D:\gcc40-20051104\explorer\gcj>gcj -fjni -mwindows -findirect-dispatch 
 > > -classpath org.eclipse.core.runtime_3.1.1.jar org.eclipse.osgi_3.1.1.jar 
 > > org.eclipse.core.commands_3.1.0.jar 
 > > org.eclipse.core.expressions_3.1.0.jar org.eclipse.jface_3.1.1.jar 
 > > swt.jar explorer.jar --main=explorer_12.Explorer -o explorer 
 > > org/eclipse/jface/wizard/WizardSelectionPage.java:0: internal compiler 
 > > error: in parse_zip_file_entries, at java/jcf-parse.c:1390
 > > Please submit a full bug report,
 > > with preprocessed source if appropriate.
 > > See <URL:http://gcc.gnu.org/bugs.html> for instructions.
 > 
 > I've found out that changing the jar ordering makes it compile the
 > application without crashing, it's just a matter of putting swt.jar 
 > before org.eclipse.jface_3.1.1.jar -> it seems that the jars must be
 > provided so that each jar dependencies are completely satisfied by
 > the previous jars in the classpath (this is not required by the standard
 > java runtime).

To the best of my knowledge it's not required by gcj either.

If I were you I'd compile each jar file on its own and then link the
resulting objects together.

Andrew.