Resources in natively compiled executables

Wed Apr 14 21:00:00 GMT 2004

Am Mittwoch, 14. April 2004 16:33 schrieb Tom Tromey:
> >>>>> "Chris" == Chris Burdess <dog@bluezoo.org> writes:
>> Chris> All is well when building a jarfile. However, when our target
> is a Chris> native executable, there is currently (AFAIK) no way for
> gcj to be Chris> informed of these resources and package them into
> the executable in Chris> such a way as to be accessible via the above
> methods.
>> Look at the `--resource' option. This lets you compile in a file as
> a resource. It is available via the special `core:' URL handler;
> `core:/' is put on the class path by default. I think all the
> methods you mention will work fine with core resources.

As I learned with gcjwebplugin there are problems when compiling 
different jars to native because the resources in the different jars 
get the same symbols names it seems (_Jr1, _Jr2, _Jr3, etc.). We need 
to fix this somehow.
Michael