Test repository to check push and ssh key
bd9d0067a6
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. |
||
---|---|---|
bin | ||
distro-configs | ||
dmake | ||
git-hooks | ||
guw | ||
instsetoo_native | ||
m4/mac | ||
scp2 | ||
soldep | ||
solenv | ||
soltools | ||
splitbuild | ||
stlport | ||
tail_build | ||
.gitattributes | ||
.gitignore | ||
acinclude.m4 | ||
autogen.sh | ||
bootstrap.1 | ||
buildscript.sh | ||
config.guess | ||
config.sub | ||
configure.in | ||
COPYING | ||
COPYING.LGPL | ||
COPYING.MPL | ||
download | ||
g | ||
GNUmakefile.mk | ||
install-sh | ||
Makefile.in | ||
makefile.rc | ||
Module_tail_build.mk | ||
ooo.lst.in | ||
oowintool | ||
post_download.in | ||
Repository.mk | ||
RepositoryFixes.mk | ||
RepositoryModule_ooo.mk | ||
set_soenv.in | ||
TEMPLATE.SOURCECODE.HEADER |