LibGCJ static linking trouble

Andrew Haley aph@redhat.com
Thu Nov 16 15:22:00 GMT 2006


Thomas Womack writes:
 > Using gcc instead of gcj for the final link has produced an executable 
 > with no run-time dependency on libgcj, and reminded me to go and get my 
 > eyeglass prescription checked, but I've now run into another problem:
It's the usual static linking problem: you're going to have to find
out some way to force MessagesBundle.properties to be included in your
executable or you'll have to provide a jar file so that it will be
found at runtime. When compiling a jarfile, gcj's default behaviour
is to include the resource files it finds, or you can use the
--resource option.
Andrew.


More information about the Java mailing list

AltStyle によって変換されたページ (->オリジナル) /