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]

Re: native cross dll compile

From: Christian Stuellenberg <gcj at stuellenberg dot de>
To: Anthony Green <green at redhat dot com>
Cc: java at gcc dot gnu dot org
Date: Thu, 11 Sep 2003 14:46:04 +0200 (CEST)
Subject: Re: native cross dll compile
References: <16224.12947.401766.654228@tower.cgs.condor.local><1063282201.30541.49.camel@escape>

>>>>> "Anthony" == Anthony Green <green@redhat.com> writes:

    Anthony> I believe this is because it's linking libgcj.a
    Anthony> statically into your dll.  Try creating a libgcj.dll
    Anthony> first and then creating your dll.  See
    Anthony> http://gcc.gnu.org/ml/java/2002-12/msg00287.html

You've posted:
    msg00287> $ i686-pc-mingw32-gcj -shared -o libgcj.dll
    msg00287> -Wl,--out-implib,libgcj.a -Wl,--export-all-symbols
    msg00287> [all-object-files-here]

What exact are "all the object files"?
Are that only the objects that are stored in the file
<gcc-build>/<target>/libjava/libgcj.objectlist
or also some other?

    Anthony> BTW, how is the i386-mingw32msvc target different from
    Anthony> i386-mingw32 ?

I have extracted all a few options from
http://www.libsdl.org/extras/win32/cross/build-cross.sh

So I also used this msvc suffix because it was there, but I only use
win32api-2.3 and mingw-runtime-3.0 (so I assume nothing special).

Regards,
Christian

Follow-Ups:
- Re: native cross dll compile
  - From: Anthony Green

References:
- native cross dll compile
  - From: gcj
- Re: native cross dll compile
  - From: Anthony Green

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]