Re: [C++-sig] Problem with bjam quickstart

[Rene Rivera]

Gabriel Joel Perez wrote:

Hi! I'm getting problems with running the basic demo that is described in
the bjam quickstart guide
http://www.boost.org/doc/libs/1_38_0/libs/python/doc/building.html

I have the following bjam version: boost-jam-3.1.17-1-linuxx86/ and I'm
running Ubuntu 8.04 Hardy Heron  and I have libboost-python1.34.1

Whenever I run the following: bjam --verbose-test --debug-configuration test

I get the following error

notice: found boost-build.jam at
/usr/share/doc/libboost-doc/examples/libs/python/example/boost-build.jam
notice: loading Boost.Build from /usr/share/boost-build
notice: loading site-config.jam from /etc/site-config.jam
notice: loading user-config.jam from /usr/share/boost-build/user-config.jam
Error: Illegal attempt to re-bootstrap the build system by invoking

   'boost-build ../../../../tools/build/v2 ;'

Please consult the documentation at 'http://www.boost.org'.


IIRC, that example assumes it's being run as part of the full Boost 
sources. But it does it as a standalone project to show what it could 
look like in your own project. Hence it causes problems when it's really 
separate :-( It means you should open up the "example/boost-build.jam" 
 
file, the "example/Jamroot" file, and likely other Jam* files in there 
to follow the instructions that mention changing paths when those 
examples are moved outside of the Boost source tree.


HTH.

--
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://mail.python.org/mailman/listinfo/cplusplus-sig

Re: [C++-sig] Some thoughts on py3k support

[Rene Rivera]

Matthew Scouten (TT) wrote:

I can work with whatever you come up with, but it might convenient if a
char* or char[] was treated as a bytes object and a std::string was
treated as a string. Thoughts? 


A char* can never be fully treated as a bytes object. You must mean a 
char* plus a size_t (or two char* iterator pointers). At which point any 
convenience you think you are getting from treating char* as bytes is 
gone as you have to introduce an intermediate type anyway to put in the 
"buffer" semantics. Hence you are better off with real buffer objects, 
or equivalents thereof. Say a std::pair iterator range, or 
std::vector, etc.



--
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://mail.python.org/mailman/listinfo/cplusplus-sig