[C++-sig] Building "hello world" with Boost.Python

[David Abrahams]

on Tue Sep 30 2008, k k <ralvek-AT-yahoo.it> wrote:

> Yes, running bjam -n -a i can see that it really creates hello_ext.pyd:
>
> gcc.link.dll bin\gcc-mingw-3.4.5\debug\hello_ext.lib
>
>     "g++" -L"C:\Python25\libs" -Wl,-R -Wl,"C:\Python25" -Wl,-R -Wl,"C:\Python25\
> libs" "-Wl,--out-implib,bin\gcc-mingw-3.4.5\debug\hello_ext.lib" -o "bin\gcc-min
> gw-3.4.5\debug\hello_ext.pyd"  -shared -Wl,--start-group "bin\gcc-mingw-3.4.5\de
> bug\hello.o" "..\..\..\..\bin.v2\libs\python\build\gcc-mingw-3.4.5\debug\boost_p
> ython-mgw34-d-1_35.lib"  -Wl,-Bstatic  -Wl,-Bdynamic -lpython25 -Wl,--end-group
> -g
>
> but after some other operations it deletes this file(as i understand it):
>
> RmTemps bin\hello.test\gcc-mingw-3.4.5\debug\hello
>
>     del /f /q "bin\gcc-mingw-3.4.5\debug\hello_ext.pyd"
>
> this is strange, isn't it? how can i tell it to do not delete it?

Pass --preserve-test-targets to bjam, and/or remove the test target from
the Jamfile.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com