Re: [C++-sig] building 32 Bit and 64 Bit extensions on the same machine

It's a feature, not an option. Features do not have a leading dashdash. You may of course have to point out a suitable Python path anyway, but it helps if you actually instruct the build to be 64-bit in the first place. -- Lars Viklund | z...@acc.umu.se _

Re: [C++-sig] A very strange behaviour of Boost (Mingw, gcc 4.5)

printed. If the runtimes have different ideas of what constitutes a FILE* (which output is done through), you blow up good. This also includes using static runtimes to some extent. -- Lars Viklund | z...@acc.umu.se ___ Cplusplus-sig mailing list Cplusplu

Re: [C++-sig] Fill a python::str with contents of a vector ?

ere's str(char const*, char const*) and str(char const*, size_t) overloads. Won't they suffice? -- Lars Viklund | z...@acc.umu.se ___ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig

Re: [C++-sig] Differences between 32-bit and 64-bit python25.lib

ll from a Windows perspective of course, as that's your context. As for getting things to do the right thing, I'm unsure. [1] http://blogs.msdn.com/oldnewthing/archive/2004/01/08/48616.aspx [2] http://blogs.msdn.com/freik/archive/2005/03/1