[C++-sig] Constructor w/ string

[David Abrahams]

From: "Scott A. Smith" <ssmith at magnet.fsu.edu>

> So, I guess I have other problems/questions/statments.
>
> 1.) I need to find out the difference between building a dll and building
>     a pyd file? Why is one preferrable over the other?

The .pyd shows a nice little Python icon; otherwise they are exactly
identical.

> As I mentioned, the
>     dll build of my project with Boost 1.25.0 worked just fine.
> 2.) What version of Boost.Python am I using? If I build it from the main
> directory

What is "the main directory"?

>     I think I understand that I make 1.2x with x>=8, even though the CVS
> distribution
>     contains both? But I think Ralf told me that
>     if one builds things in the Python sub-directory it uses 2.0. Can
this

Yes.

> cause
>     trouble or should I just not worry about it?


Don't worry about it.

> Since I am nearly back to
> square 1
>     at this point I have no problems just using 2.0, but I am not sure
how.

If you really want to start over with v2:
http://mail.python.org/pipermail/c++-sig/2002-May/001100.html

> 3.) While I have python22.lib I don't have python22_d.lib, is that for
> debugging?

Read the section on "Build Variants" at
http://www.boost.org/libs/python/doc/building.html

>     If so, where can I get this or how can I build it? Apparently I will
> need it.

You don't need it, but it will help you to detect certain problems if you
use it.

> 4.) When I build my Boost.Python example with Jam it appears that it
> automatically
>     a.) Builds Boost.Python (e.g. when I set the BUILD variable
differently)
>     b.) Sets up the PYTHONPATH and PATH
>     c.) Attempts to run my example?


Yes.

> 5.) I have never actually seen the tests/examples run automatically
during
> the
>     build of test. Is there supposed to be something other than compiler
> output
>     when one issues a "bjam test"?

See the section on Testing at
http://www.boost.org/libs/python/doc/building.html

> Now that I've CVS upgraded the mpl stuff
>     it seems to compile fine (is this version 2.0?) but if it is supposed
to
>     invoke Python and do something else I don't see it.

Does this clarify?

build in             target     version    requirements     result
--------             ------     -------    ------------     ------
libs/python/build    all/<none> v1         Boost            libboost_python
libs/python/build    test       v1         Boost            v1 tests

libs/python          all/<none> v2         +mpl-development bpl library
libs/python/test     test       v2         +mpl-development v2 tests