A brief update. Partial replies to Gerritt. Self-corrections.
Soren A [EMAIL PROTECTED] wrote
in [EMAIL PROTECTED]:">news:[EMAIL PROTECTED]:
The scenario is that I am trying to re-create the process of building
bleadperl [...] but one thing that
you can get from using dlltool, that you don't
Hallo,
[...]
passes it to ld:
$command =$CC -shared -o $dllname;
# $command .= --verbose if $verbose;
$command .= -Wl,--output-def=$libname$DEF_EXT if $DEF_EXT;
$command .= -Wl,--output-exp=$libname$EXP_EXT if $EXP_EXT;
$command .= -Wl,--out-implib=$libname.dll$LIB_EXT if
Is it a science, or an art?
[The following description pertains to the *July 2002* version of dlltool].
I am wanting to know about something relating to building of DLLs on
Cygwin using the GNU Binutils tools. Up until this point I've been happy
enough just letting recent GCC (ld) versions work
Hallo Soren,
Taking apart the current build setup, we see that dlltool (through dllwrap)
is invoked for building the shared Perl library
That is not correct. At first a static lib is created:
/bin/ar rcu libperl.a perl.o malloc.o gv.o toke.o perly.o op.o pad.o regcomp.o dump.o
util.o mg.o
4 matches
Mail list logo
