Re: Building DLLs out of C++ code

Adriaan de Groot wrote:

> I have a tiny recipe and a tiny fragment of C++ code (both attached)
> from which I would like to build a shared library (DLL). Running A-A-P
> (CVS HEAD) on this generates a Python recursion-depth exception and
> the build fails.  Re-running A-A-P causes a shared library to be
> built, but it looks like the wrong libker is used (the C linker, not
> g++).

That the wrong linker is used when the compilation isn't done is a known
problem.  While compiling an attribute is added to the object file to
indicate the linker needed.  When the compilation is skipped the
attribute isn't there and the wrong linker may be used.  I still haven't
found a simple solution for this.

The "recursion depth" error looks strange.  The stack traceback doesn't
have many entries.  I don't see an obvious problem.  Perhaps you can
debug this?

--=20
hundred-and-one symptoms of being an internet addict:
200. You really believe in the concept of a "paperless" office.

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \=
\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ =
\\\
\\\        download, build and distribute -- http://www.A-A-P.org        =
///
 \\\            help me help AIDS victims -- http://www.ICCF.nl         /=
//


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=3D=
121642