From: Stefan Seefeld (seefeld_at_[hidden])
Date: 2007-02-21 06:32:00
David Abrahams wrote:
> Stefan Seefeld <seefeld_at_[hidden]> writes:
>>> The deeper problem: detecting the link compatibility will need more
>>> research, and has to be addressed within Boost.Build I guess.
>> AFAIU, you can compile your own C++ code with 'g++ -mno-cygnus' on
Sorry for the lapsus. That's what I meant.
>> cygwin, and are then able to link with a windows-native python runtime.
>> That's the equivalent of using a mingw toolchain directly.
>> I'm not sure this is the best time to experiment with toolchains, though,
>> so marking this variant as not available may be the right thing to do.
> Boost.Python has always worked with Cygwin GCC, but if you don't use
> -mno-cygwin, you have to use the cygwin version of Python (the one
> installed when you select it in the Cygwin installer). Currently the
> Python support in BBv2 on Windows and Cygwin is a total mess, which
> may explain why it isn't working for you. I'm trying to fix that up
I wasn't talking about boost. I have been able to compile another project
(Synopsis, to be specific) with 'g++ -mno-cygwin', and then linking it
with the windows Python libs. That worked fine.
-- ...ich hab' noch einen Koffer in Berlin...
Boost list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk