[C++-sig] Where to start...
whisper at oz.net
Thu May 9 22:15:08 CEST 2002
Thanks for your reply.
I would like some sort of guidance on where to actually start doing the
work... headers, python wrapper classes... ?
Also, I belatedly realized (right after copying CVS over the boost 2.0 d/l
install) that i'm not using any kind of tag when getting stuff out of CVS.
What do I need to do to get 2.0? It looks as though Win-CVS is using "HEAD"
as the -r tag, but i'm not positive of that.
I hope you won't mind my asking a bunch of questions - this thing i'm doing
is for a free/open source library.
Seattle, WA USA
> -----Original Message-----
> From: c++-sig-admin at python.org [mailto:c++-sig-admin at python.org]On
> Behalf Of David Abrahams
> Sent: Thursday, May 09, 2002 11:13
> To: c++-sig at python.org
> Subject: Re: [C++-sig] Where to start...
> ----- Original Message -----
> From: "David LeBlanc" <whisper at oz.net>
> > I have the latest CVS Boost (5.9.2002 @ 09:00 PDT). I have python 2.2.1.
> > have a C++ static library that i'd like to control from python, ideally
> > creating a dll wrapping the C++ static library. I'd like to do all of
> > on Windows with MSVC 6.0 sp3.
> No guarantees with sp3. Sp4 probably works (earlier versions of
> the library
> were tested with it), but SP5 is what we're testing with.
> > Where do I start?
> You have two options:
> Boost.Python v1 - mature, but a dead branch. Depends on the presence of a
> common bug in C++ many implementations. There will be no further
> development after the upcoming boost release. If you build the "test"
> target in libs/python/build using Boost.Build it will build and run some
> tests for your platform. Docs are in libs/python/doc.
> Boost.Python v2 - Still officially prerelease, but already in use for some
> large projects. Better handling of references and pointers, better
> cross-module support, nicer syntax, fully-conforming code. Build
> the "test"
> target in libs/python/test to see it in operation. Docs are in
> > Also, one bit that has me concerned is that some of the methods have
> > call-back arguments. Is it within the realm of possibility to structure
> > things such that those call-backs can be written in Python?
> Definitely. For v1, see libs/python/doc/overriding.html. For v2, see
> libs/python/doc/v2/callbacks.html (you'll need to update your CVS again).
> C++-sig mailing list
> C++-sig at python.org
More information about the Cplusplus-sig