[C++-sig] First time pointers, first crash...

[Stefan Franke]

> -----Original Message-----
> From: c++-sig-admin at python.org [mailto:c++-sig-admin at python.org]On
> Behalf Of David Abrahams
> Sent: Monday, February 18, 2002 10:27 PM
> To: c++-sig at python.org
> Subject: Re: [C++-sig] First time pointers, first crash...

[...]

> Yes. I presume you know that BOOST_DEBUG_PYTHON requires _DEBUG and a
> specially-compiled version of Python with reference-count 
> tracking enabled.
> I built and ran your example with Boost.Build, which takes care of all
> configuration issues for me.
> 
> > If so it's very strange and I have no clue what's going on here.
> 
> If you're also using Boost.Build, then neither do I.

No I'm not. I'm building Boost.Python as part of an MSVC workspace that 
contains 65 other subprojects -- our app is rather big. My reasons for 
not using Boost.Build are

- I don't know how to use jam. I'm able to build & run the demos like
  shown in the docs, but I don't even know how the set up and run this
  little test example like you did. Maybe you can give me a few hints.

- Our app is cross-platform (Win, Mac OS, OS-X). Jam is too, of course,
  but I don't have an idea how to manage all compile & link options for
  the various platforms within jam.

- I'm doing something experimental here. My co-workers are quite sceptical
  about "this Python thing" anyway, and expecting them (espacially or Mac 
  guys) to use yet another build tool for a simgle subproject is pretty 
  much.

One general question here: Are users of Boost in general supposed to learn
jam? Since I consider my case pretty "real-world", I hope there is - and
ever will be - a way and some documentation how to build the libs 
generically. 

Stefan