[C++-sig] Stand-alone Boost.Python

[Stefan Seefeld]

On 20.06.2016 04:35, Giuseppe Corbelli wrote:
> On Sat, 18 Jun 2016 00:25:08 -0400 Stefan Seefeld <stefan at seefeld.name>
> wrote:
>> Hello,
>> I have started working on a new SCons-based build infrastructure for
>> Boost.Python that allows the Boost.Python code to be compiled
>> stand-alone against a pre-installed Boost. I have checked in a first
>> version to the develop branch, and have enabled Travis-CI to use that.
>>
>> While this works reasonably well, and provides a much simpler workflow
>> for developers wanting to contribute to Boost.Python, it isn't (yet)
>> entirely feature-complete. Notably, running this on Windows (using MSVC)
>> produces errors. I'd appreciate any help with this, especially from
>> Windows users who are more familiar with MSVC than I am (that shouldn't
>> be hard, given I have next to no experience with using MSVC :-) ).
> I can be of some (testing) help.
> Cloned the repo, configured for x86 target.
>
> arch = 'x86'
> toolchain = 'msvc'
>
> First thing that I notice is that the /arch compiler option is missing (1).
> The commandline is (cut include dirs):
> cl /Fobin.SCons\msvc-14.0\release\dynamic\threading-multi\test
> \andreas_beyer.obj /c bin.SCons\msvc-14.0\release\dynamic\threading-multi
> \test\andreas_beyer.cpp /TP /nologo
> -TP /Z7 /W3 /GR /MDd /Zc:forScope /Zc:wchar_t /wd4675 /EHs /DBOOST_ALL_NO_LIB=1 /DNDEBUG 
>
> In this way the compiler relies on the default architecture.

which should be fine. Note that the 'arch' flag is used to initialize
the environment, so the appropriate vcvars* script is read.
Let's follow up with details on
https://github.com/boostorg/python/issues/72 so we don't pollute this
list with technical details.

Many thanks !

        Stefan

-- 

      ...ich hab' noch einen Koffer in Berlin...