]>
Commit | Line | Data |
---|---|---|
4f8cf629 JB |
1 | --- boost_1_34_0/tools/build/v2/tools/python.jam.orig 2007-04-06 20:17:43.000000000 +0200 |
2 | +++ boost_1_34_0/tools/build/v2/tools/python.jam 2007-06-17 00:19:00.865685036 +0200 | |
3 | @@ -911,30 +911,7 @@ | |
4 | ; | |
5 | } | |
10fc06f2 | 6 | |
4f8cf629 JB |
7 | - # On *nix, we don't want to link either Boost.Python or Python |
8 | - # extensions to libpython, because the Python interpreter itself | |
9 | - # provides all those symbols. If we linked to libpython, we'd get | |
10 | - # duplicate symbols. So declare two targets -- one for building | |
11 | - # extensions and another for embedding | |
12 | - # | |
13 | - # Unlike most *nix systems, Mac OS X's linker does not permit undefined | |
14 | - # symbols when linking a shared library. So, we still need to link | |
15 | - # against the Python framework, even when building extensions. | |
16 | - # Note that framework builds of Python always use shared libraries, | |
17 | - # so we do not need to worry about duplicate Python symbols. | |
18 | - if $(target-os) in windows cygwin darwin | |
19 | - { | |
20 | - alias python_for_extensions : python : $(target-requirements) ; | |
21 | - } | |
22 | - else | |
23 | - { | |
24 | - alias python_for_extensions | |
25 | - : | |
26 | - : $(target-requirements) | |
27 | - : | |
28 | - : $(usage-requirements) | |
29 | - ; | |
30 | - } | |
31 | + alias python_for_extensions : python : $(target-requirements) ; | |
32 | } | |
10fc06f2 | 33 | |
4f8cf629 | 34 | rule configured ( ) |