This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Bryce McKinlay writes:Well, yes, obviously that's the alternative - but it may not be an option in a mixed compiled/bytecode application, or where you want to compile/run an application against a complex set of dependencies (Jonas!) easily without being forced to link everything explicitly.
> > >First, gcj can in fact compile jar files into usable libraries (as we
> >all know or have read), but there are limitations which are not clearly
> >advertised or documented (at least not in any obvious way).
> >
> >1) The first limitation is that in order to get working libs from jars
> >you have to work with this assumption. The jar can only contain one
> >package.
No.
> Yes, unfortunately this is a well-known limitation of the existing > shared-library naming scheme.
All you have to do is link explicitly against the shared library.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |