Re: [jamboost] gcc/NT/dll problem

From: David Abrahams (dave_at_[hidden])
Date: 2003-01-09 10:46:43

Vladimir Prus <ghost_at_[hidden]> writes:

> I'm trying to get one of the tests working on NT, and get this problem.
> A dll is compiled from one source file. That file contains a reference
> to external symbol, i.e
>
> void foo();
> int main() { foo(); return 0; }
>
> The dll does not link, saying that "foo" is not found. For Linux, that
> function is provided by the executable the dll is linked into. Any
> idea if this can be made to work? Or I should fix the test?

I am not sure whether it's possible under Cygwin, but it is not
possible under NT. That's why regular Windows Python has a DLL, while
Unix builds do not (so that extension modules can link to the DLL to
get Python's symbols). You might learn about the Cygwin case by
looking at the Python sources. Hmm, from looking at
tools/build/python.jam, I think that Cygwin builds are the same as NT
builds in this respect:

<$(gcc-compilers)><*><find-library>python$(PYTHON_VERSION).dll 

-- 
David Abrahams
dave_at_[hidden] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution