- Boost-users - lists.boost.org

FW: Using Boost.Build with Boost.Python: Three Questions; "Copy" Rule
by Bilokon, Paul 30 Apr '08

30 Apr '08

Hi, Forwarding this question to boost-users as it applies to Boost.Python and Boost.Build in equal measure. Regards, Paul > ______________________________________________ > From: Bilokon, Paul > Sent: Wednesday, April 30, 2008 3:07 PM > To: 'boost-build(a)lists.boost.org' > Subject: Using Boost.Build with Boost.Python: Three Questions; > "Copy" Rule > > Hi, > > I would be very much obliged if you could share your insights on the > following three questions: > > (1) Is it at all possible to change the location of the "bin" folder > for my project or is it hardcoded? (bjam generates a number of files > under (project root)/bin/msvc-8.0/debug and (project > root)/bin/msvc-8.0/release. If so, what is the "correct" (good > practice) way of achieving this? > > (2) I am using Boost.Build with Boost.Python. The generated files are > linked to boost_python-vc80-mt-gd-1_34_1.dll (debug) and > boost_python-vc80-mt-gd-1_34_1.dll (release). But then I'm using > > install bin : hello : <location>$(dist-dir)/debug <variant>debug ; > install bin : hello : <location>$(dist-dir)/release <variant>release ; > > in Jamroot to dist the files. The DLLs do not get copied to the dist > location (nor do they appear under "bin"). How can I instruct bjam to > copy the DLLs? > > (3) On a related note, is there a "copy" rule in Boost.Build (very > much along the lines of the similar Ant rule), which would copy my > supporting Python files to $(dist-dir)? > > Sorry if my questions have obvious answers; I did read through the > documentation and check the related resources on the Web. > > Many thanks for your help. > > Regards, > Paul > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.

1 0

Re: [Boost-users] [variant, mpl] passing variable list of types
by Neal Meyer 30 Apr '08

30 Apr '08

This is what I use for the same thing typedef typename boost::make_variant_over< Types >::type variant_t; Where Types is a mpl::vector<> of the types I want to put in the vector. -Neal Date: Wed, 30 Apr 2008 17:28:30 +0300 From: Igor R. <igor_rubinov(a)hotmail.com> Subject: [Boost-users] [variant, mpl] passing variable list of types as a template parameter To: <boost-users(a)lists.boost.org> Message-ID: <BAY109-W253127985653CE5AF34F9AF8D80(a)phx.gbl> Content-Type: text/plain; charset="windows-1255" Hello, I've got a class template that one of its members is boost::variant: template<?> class MyClass { boost::variant</*bounded types*/> var_; }; At the stage of MyClass instantiation, I'd like to specify variant' bounded types list - which is variable. What's the most simple way to do this? Can I use mpl::list somehow - both as MyClass template parameter and in the variant specialization? Thank you.

2 1

[statechart] using the same event handler in multiple states.
by Paul Heil 30 Apr '08

30 Apr '08

I'm trying to implement a state machine using the boost statechart library. It has 3 main states (call them "State 1", "State 2", and "State 3") and 3 classes of events ("Class 1", "Class 2", and "Class 3"). State 1 should have event handlers for all Class 1 events. State 2 should have handlers for Class 1 and 2 events. State 3 should have handlers for Class 1, 2, and 3 events. The handling of each class of events is essentially the same regardless of what state the machine is in. Is there a way I can derive State 3 from States 1 and 2 so that I'm not repeating the Class 1 and 2 event handling code in State 3? What is the best way to architect something like this? Thanks, PaulH

3 3

boost MPI on FreeBSD 4.11
by Dheeraj Gautam 30 Apr '08

30 Apr '08

Hi, I am trying to compile Boost.MPI on FreeBSD 4.11 machine. But its failing with following error: Found MPICH wrapper compiler: mpic++ MPI compilation flags: -I/home/eqsupport/mpich2_install/include -L/home/eqsupport/mpich2_install/lib -lmpichcxx -lmpich MPI link flags: -I/home/eqsupport/mpich2_install/include -L/home/eqsupport/mpich2_install/lib -lmpichcxx -lmpich MPI build features: <include>/home/eqsupport/mpich2_install/include <library-path>/home/eqsupport/mpich2_install/lib <find-shared-library>mpichcxx <find-shared-library>mpich <include>/home/eqsupport/mpich2_install/include <library-path>/home/eqsupport/mpich2_install/lib < find-shared-library>mpichcxx <find-shared-library>mpich MPI launcher: mpirun -np ==================================================== warning: No toolsets are configured. warning: Configuring default toolset "gcc". warning: If the default is wrong, your build may not work correctly. warning: Use the "--toolset=xxxxx" option to override our guess. warning: For more configuration options, please consult warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html notice: will use 'g++' for gcc, condition <toolset>gcc-2.95.4 notice: using gcc libraries :: <toolset>gcc-2.95.4 :: /usr/bin /usr/lib /usr/lib32 /usr/lib64 notice: using gcc archiver :: <toolset>gcc-2.95.4 :: /usr/bin/ar warning: toolset gcc initialization: can't find tool windres warning: initialized from notice: using rc compiler :: <toolset>gcc-2.95.4 :: /usr/bin/as ...patience... ...found 1889 targets... ...updating 29 targets... gcc.compile.c++ bin.v2/libs/mpi/build/gcc-2.95.4/release/threading-multi/broadcast.o In file included from boost/serialization/nvp.hpp:34, from boost/serialization/serialization.hpp:24, from boost/archive/detail/oserializer.hpp:64, from boost/mpi/detail/mpi_datatype_oarchive.hpp:12, from boost/mpi/detail/mpi_datatype_cache.hpp:13, from boost/mpi/datatype.hpp:26, from boost/mpi/communicator.hpp:20, from boost/mpi/collectives.hpp:21, from boost/mpi/collectives_fwd.hpp:19, from boost/mpi/collectives/broadcast.hpp:11, from libs/mpi/src/broadcast.cpp:9: boost/serialization/base_object.hpp: In function `static const void * boost::serialization::detail::base_register<Base,Derived >::invoke()': boost/serialization/base_object.hpp:56: syntax error before `::' boost/serialization/base_object.hpp:59: use of class template `template <class T> boost::is_polymorphic<T>' as expression In file included from boost/mpi/detail/mpi_datatype_oarchive.hpp:12, from boost/mpi/detail/mpi_datatype_cache.hpp:13, from boost/mpi/datatype.hpp:26, from boost/mpi/communicator.hpp:20, from boost/mpi/collectives.hpp:21, from boost/mpi/collectives_fwd.hpp:19, from boost/mpi/collectives/broadcast.hpp:11, from libs/mpi/src/broadcast.cpp:9: boost/archive/detail/oserializer.hpp: In function `static const class boost::archive::detail::basic_pointer_oserializer * boos t::archive::detail::save_pointer_type<Archive,TPtr>::abstract<T>::register_type(Archive &)': boost/archive/detail/oserializer.hpp:329: syntax error before `::' boost/archive/detail/oserializer.hpp:330: template argument 1 is invalid boost/archive/detail/oserializer.hpp:330: confused by earlier errors, bailing out "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -fPIC -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_MPI_DYN_ LINK=1 -DBOOST_MPI_SOURCE=1 -DNDEBUG -I"." -I"/home/eqsupport/mpich2_install/include" -c -o "bin.v2/libs/mpi/build/gcc-2.95.4 /release/threading-multi/broadcast.o" "libs/mpi/src/broadcast.cpp" ...failed gcc.compile.c++ bin.v2/libs/mpi/build/gcc-2.95.4/release/threading-multi/broadcast.o... gcc.compile.c++ bin.v2/libs/mpi/build/gcc-2.95.4/release/threading-multi/communicator.o In file included from boost/serialization/nvp.hpp:34, from boost/serialization/serialization.hpp:24, from boost/archive/detail/oserializer.hpp:64, from boost/mpi/detail/mpi_datatype_oarchive.hpp:12, from boost/mpi/detail/mpi_datatype_cache.hpp:13, ========================================================================= Almost all compilations for MPI are failing with similar error. It seems some C++ support is not there. I am new to C++ and Boost. Any help will be of great help. Dheeraj Gautam

3 2

Serialization of boost::thread::detail::singleton
by Campbell Morrison 30 Apr '08

30 Apr '08

I need to serialize a singleton, but have no idea how to go about it. I have made several attempts to date with very little success. I am new to using Boost and would greatly appreciate any help. regards, Campbell.

1 0

Question about Any usage
by Jeffery Cavallaro 30 Apr '08

30 Apr '08

I have a question about the use of Any, especially when used in a larger facility such as program_options. There doesn't seem to be a (easy) way to post-process the results of a facility that has generically stuffed a bunch of values into a list of Any's. For example, if I wanted to a program to spit out all of its options to standard out, there doesn't seem to be any hooks to extract an Any value in a generic way (e.g., as a string). Granted, I could derive a class and add methods to do so, but that doesn't work when Any is already embedded in the program_options implementation. I certainly could be missing something here. I haven't used Any or program_options yet, and trying to understand all of the possibilities from the spec-like doc is hard. How do the rest of you do such things? -- Jeffery Cavallaro, 1055 Joaquin-191A Infrastructure Engineering Google Inc. 1600 Amphitheatre Parkway Mountain View, CA 94043 650-214-2552

7 6

[concept_check] Why does char not qualify as "Integer"?
by Peter 30 Apr '08

30 Apr '08

The statement BOOST_CONCEPT_ASSERT((boost::Integer<T>)); triggers an error if T is the type char. It does not trigger an error if T is either of type signed char or unsigned char. I can understand why it's not so easy to detect for SignedInteger or UnsignedInteger given type char, but to my understanding using type char should work with the above statement. Peter

1 0

MPL preprocessed question
by Neal Meyer 30 Apr '08

30 Apr '08

Alright I've been through the mailing list a few times, and thanks to Ovanes for the help on getting some of the mpl stuff working. Here's what I've got working so far. I built a vector100.hpp and placed it in the boost\mpl\vector and added the following to my header. #define BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS #define BOOST_MPL_LIMIT_VECTOR_SIZE 100 #include "boost/mpl/vector.hpp" #undef BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS #undef BOOST_MPL_LIMIT_VECTOR_SIZE Great everything works great, except for the fact that it takes an extra long time to compile. So following some threads on the list, I'd like to pregenerate a header file with the definitions for the vector that takes 100 elements. Placed the vector100.cpp in the \libs\mpl\preprocessed\vector and ran the preproces.py and got the vector100.hpp file generated in boost\mpl\vector\aux_\preprocessed\plain. Everthing seems like I'm heading in the right direction to get it proprocessed. So know what do I do to get it included in the same way as the previous code? I've tried including the new header directly and playing around with various macros to get it to be included, but no dice so far. Is there a way to have the preprocessing scripts regenerate the vector.hpp in boost\mpl\aux_\preprocessed\plain? So that I can use boost::mpl::vector instead of a version with the number of parameters in it, because that's varies dramatically throughout how this code is being used and would be a major pain. -Neal

1 0

[gil] [announcement] New IO lib
by Christian Henning 30 Apr '08

30 Apr '08

Hi there, over the past few months I have been working on a new version of gil's io extension. In this release I've added support for: * more image formats, most importantly bit_aligned images ( like 1bit images ), * reading of subimages like one row at a time for huge images, * reading image information, only. * having a unified interface for all sorts of devices, subimages, and converter objects. So far, png, jpeg, and tiff images are supported. In the not so distant future there will be bmp and pnm images added. You can grab the current version via subversion from: https://gil-contributions.googlecode.com/svn/trunk/gil_2/boost/gil/extensio… If desired I can supply a zip file to the vault. The images libraries can be grabbed from: ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz ( www.ijg.org isn't responding ) http://www.libpng.org/pub/png/libpng.html http://www.libtiff.org/ It's highly advised to built your own version of the image lib you need. I installed the GNU's binaries for Windows, but unfortunately, I only had problems with them. The library is still header-only. When using boost::filesystem's paths, of course, you add a dependency to the filesystem lib. The Read Interface ------------------------ Reading an image can be done in multiple ways depending on what your need is. Like the old io lib there are 4 different ways of reading images. As there are: * read_image: Read image, the right amount of memory will be allocated beforehand. The supplied image type needs to be compatible with actual image file. * read_view: Read image, the image's memory must be already allocated. The supplied image type needs to be compatible with actual image file. * read_and_convert_image: Same as read_image, but the user can specify an color converter. * read_and_convert_view: Same as read_view, but the user can specify an color converter. There is a new function for reading image information. Since every image format has it's own set of tags, the library defines seperate image_read_info<format_tag> structures. Please see, for instance, the jpeg_tags.hpp header. As for the function parameters the following sections in the same order. 1. String for file name ( std::string, std::wstring, char*, boost::filesystem::path ) OR devices ( FILE*, TIFF*, std::ifstream ) 2. Image or view type 3. Optional: Subimage definition ( top_left corner + dimensions ) 4. Optional: Color converter. This parameter is only valid for converting functions. The default parameter is gil's default_color_converter 5. Format Tag. Reading the image information only takes parameter 1 and 5. Here are some examples for reading images: #include <boost/gil/extension/io_new/jpeg_read.hpp> // Read image information std::string filename( "..\\test_images\\jpg\\found online\\test.jpg" ); image_read_info< jpeg_tag > info = read_image_info( filename, tag_t() ); // Read image FILE* file = fopen( filename.c_str(), "rb" ); rgb8_image_t img; read_image( file, img, tag_t() ); // Read image ifstream in( filename.c_str(), ios::in | ios::binary ); rgb8_image_t img( 136, 98 ); read_view( in, view( img ), tag_t() ); // Read and convert image, use gil's default converter. rgb8_image_t img; read_and_convert_image( filename, img, tag_t() ); // Read a 10x10 subimage, starting from the top_left corner. rgb8_image_t img; read_image( filename, img, point_t( 0,0 ), point_t( 10, 10 ), tag_t() ); I have created some header files to support the old read interface. For example: #include <boost/gil/extension/io_new/jpeg_io_old.hpp> std::string filename( "..\\test_images\\jpg\\found online\\test.jpg" ); rgb8_image_t img( 136, 98 ); jpeg_read_view( filename, view( img ) ); The Write Interface --------------------------- The write interface is a much simpler than the read interface. Here, we only have write_view as the entry point. As for parameters the following sections are supported: 1. String for file name ( std::string, std::wstring, char*, boost::filesystem::path ) or devices ( FILE*, TIFF*, std::ofstream ) 2. View type 3. Optional: image_write_info< FormatTag > 4. Format type The image_write_info<...> structure defines a format specific properties which can be used when writing an image. A good example is jpeg's image quality value. Examples: #include <boost/gil/extension/io_new/tiff_write.hpp> // Write image string filename( "..\\test\\tiff\\test1.tif" ); gray8_image_t img( 320, 240 ); write_view( filename, view( img ), tiff_tag() ); // Write image string filename( "..\\test\\tiff\\test2.tif" ); TIFF* file = TIFFOpen( filename.c_str(), "w" ); rgb8_image_t img( 320, 240 ); write_view( file, view( img ), tag_t() ); I have created some header files to support the old write interface. For example: #include <boost/gil/extension/io_new/tiff_io_old.hpp> string filename( "..\\test\\tiff\\test3.tif" ); gray8_image_t img( 320, 240 ); tiff_write_view( filename, view( img ) ); Supported image formats ------------------------------------- In the process of developing the new version I tried to include as many formats as possible. One consequence is a much higher compilation time. Hopefully, a design review by the community can hint me better ways to reduce it. Also, there are still holes in the support. Most noteably is TIFF, since it can support almost everything. This makes it very hard not to have code explosion during compilation. Here is a list of list of supported formats: TIFF: * Number of samples: 1, 3, 4 ( eg. RGB would be 3 ) * Bits per sample: 1, 2, 4, 8, 16, 32, 64 * planar and interleaved images * indexed images. Indices can be of 1, 2, 4, 8, or 16 bit depth, whereas the palette must a rgb16_image_t. PNG: * gray, gray_alpha, rgb, rgba * bit_depth can be 1, 2, 4, 8, 16 JPEG: * gray, rgb, cmyk, ycck ( will be read as cymk ) Please note, that I'm still in process of testing all these different formats. The primary goal of this new version is to eventually replace the old io library which is part of boost's distribution. Do I need to apply for a review? I'm not sure how to go from here. I know there is still some work to do before a possible review. Documentation is lacking and support for dynamic image needs to be added. But what I want for now is to get some feedback on design and implementation. I would like to thank Lubomir Bourdev and Andreas Pokorny for their most valueable input. Thanks, Christian

2 2

Boost CGI
by Brad 29 Apr '08

29 Apr '08

What is the current status of Darren Garvey CGI library? I am starting a CGI project and am wondering whether this is mature enough for the job? At the moment I am only looking at CGI but I may need FastCGI, etc. at a later date. My current opinion from looking at the source downloaded from http://cgi.sourceforge.net is that it will be suitable. Anyone know of any alternatives? Darren, are you still working on this? I noticed the site says you had some study to get out of the way, we've all been there ;-) Cheers, Brad

3 3