diff options
author | Tor Lillqvist <tlillqvist@novell.com> | 2011-05-23 17:15:48 +0300 |
---|---|---|
committer | Tor Lillqvist <tlillqvist@novell.com> | 2011-05-23 17:33:49 +0300 |
commit | bd9d0067a6ad22c978186a413e4ce3093e3da7d2 (patch) | |
tree | 1c6af38bd7c9370cf5bbd5b3488e2149accb6329 /stlport | |
parent | 4915eb35712e310e9a60d8d966ed789c945338a5 (diff) |
Rework DLL creation code for MinGW (cross-)compilation
Don't run dlltool --output-exp to create a separate object file with
just export data (.edata section). In the case where at least one
function in the objects being linked has been explicitly marked for
export, GNU ld will not look for export information in the object
files anyway. At least the GetVersion() function seems to be marked
for export explicitly. Just pass the .def file when linking.
GNU ld since 2.17 supports @cmdfile syntax, just like MSVC tools, so
no need to create a separate shell command file and source that. (Why
that even would work better than just running the ld command with a
long command line directly, I don't know.)
Actually I don't know why even bother with the @cmdfile, after all we
mainly intend WNTGCC to be used when cross-compiling, and there are no
short command-line length restrictions on modern OSes from which one
might want to cross-compile. But oh well.
Pass the necessary -L switches, i.e. SOLARLIB, when linking with GNU
ld. (For MSVC, the ILIB environment variable is used.)
Produce the import library when linking, no need to have a separate
rule to produce an import library for WNTGCC.
Re-unroll tg_shl.mk into _tg_shl.mk with the recently unbroken
mkunroll tool.
Diffstat (limited to 'stlport')
0 files changed, 0 insertions, 0 deletions