September 2008 - Boost-users

XML namespace support in boost serialization?
by Shiwani Sambarey 24 Sep '08

24 Sep '08

Hello all, I am planning to use the boost serialization library for a project but need to use XML namespaces for serialization. I could not find any way of doing so. Is there any support for XML namespaces in boost serialization? Thank you. Shiwani

1 0

[gil] new io extension
by Christian Henning 23 Sep '08

23 Sep '08

Hi there, I've been busy working on the next version of gil's IO extension. The last iteration was very slow to compile especially when reading or writing tiff images. This and other problems have been fixed. As a result compilation is a lot faster but also a lot more tiff formats can now be read or written. Please grab the latest from: http://gil-contributions.googlecode.com/svn/trunk/gil_2/boost/gil/extension… This download is a little bigger than to usual since there are test images included. Please see my original announcement below for documentation. The goal of this extension is to substitute the original io lib which is part of gil, and though shipped with boost. To do this a review is probably needed. I'll work on a proper documentation as the next step. Can anyone tell me where to find a tutorial for creating quickdoc? There is one problem I cannot fix and would like to ask the experts on this list. Please read the readme.txt in libs\gil\io_new\unit_test which explains the scenario. This problem has something to do with erroneously choosing the wrong functions by the compiler. The enable_if metafunction doesn't work correctly here. As usual any feedback is welcome. Thanks, Christian ------------------------------------------------------- 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 ) ); 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

1 0

[boost] File_lock bad compilation - 1.35.0
by Germain BARRET 23 Sep '08

23 Sep '08

I'm actually using boost 1.35.0 When I just include boost/interprocess/sync/file_lock.hpp in a very simple programm, then I have a list of error very surprising : "member function already defined or declared" So what, is file_lock unusable in 1.35 ? It was my only hope, other boost locks don't satisfy me. I didn't see such an error in the last 6 month ML log, so I guess nobody had it yet. log : 1>c:\boost_tri\include\boost-1_35\boost\interprocess\sync\file_lock.hpp(167) : error C2535: 'bool boost::interprocess::file_lock::timed_acquire_file_lock(boost::interprocess::file_handle_t,bool &,const boost::posix_time::ptime &)' : member function already defined or declared 1> c:\boost_tri\include\boost-1_35\boost\interprocess\sync\file_lock.hpp(110) : see declaration of 'boost::interprocess::file_lock::timed_acquire_file_lock' 1>c:\boost_tri\include\boost-1_35\boost\interprocess\sync\file_lock.hpp(195) : error C2535: 'bool boost::interprocess::file_lock::timed_acquire_file_lock_sharable(boost::interprocess::file_handle_t,bool &,const boost::posix_time::ptime &)' : member function already defined or declared 1> c:\boost_tri\include\boost-1_35\boost\interprocess\sync\file_lock.hpp(138) : see declaration of 'boost::interprocess::file_lock::timed_acquire_file_lock_sharable' 1>c:\boost_tri\include\boost-1_35\boost\interprocess\sync\file_lock.hpp(119) : error C3861: 'try_acquire_file_lock': identifier not found 1>c:\boost_tri\include\boost-1_35\boost\interprocess\sync\file_lock.hpp(147) : error C3861: 'try_acquire_file_lock_sharable': identifier not found 1>c:\boost_tri\include\boost-1_35\boost\interprocess\sync\file_lock.hpp(175) : error C3861: 'try_acquire_file_lock': identifier not found 1>c:\boost_tri\include\boost-1_35\boost\interprocess\sync\file_lock.hpp(188) : error C3861: 'sleep': identifier not found 1>c:\boost_tri\include\boost-1_35\boost\interprocess\sync\file_lock.hpp(203) : error C3861: 'try_acquire_file_lock_sharable': identifier not found 1>c:\boost_tri\include\boost-1_35\boost\interprocess\sync\file_lock.hpp(262) : error C2039: 'timed_acquire_file_lock' : is not a member of 'boost::interprocess::detail' 1>c:\boost_tri\include\boost-1_35\boost\interprocess\sync\file_lock.hpp(298) : error C2039: 'timed_acquire_file_lock_sharable' : is not a member of 'boost::interprocess::detail'

2 1

[GIL] Image of doubles
by Brice Rivé 23 Sep '08

23 Sep '08

I need an image type (and view) that has doubles for pixels. I only found a type with floats. How can I do that? -- View this message in context: http://www.nabble.com/-GIL--Image-of-doubles-tp19607063p19607063.html Sent from the Boost - Users mailing list archive at Nabble.com.

2 2

functors with function_traits
by Christoph 23 Sep '08

23 Sep '08

Do function_traits work with functors? I tried with struct XYZ { bool operator() (int x) const { return x+2; } }; template<typename FUNCTION> class BindingImpl1xxx { public: typedef FUNCTION function; typedef typename boost::function_traits<FUNCTION>::result_type res_type; typedef typename boost::function_traits<FUNCTION>::arg1_type arg1_type; }; but the following won't compile: XYZ xyz; BindingImpl1xxx<XYZ> xxx(xyz); Is there a way to achieve the function_traits functionality with function_traits or some other type_traits? Thank you. Christoph

4 3

Memory stream
by Lloyd 23 Sep '08

23 Sep '08

Hi, How can I create a memory stream. That is, a stream to which we can write any binary data. Thanks, Lloyd ______________________________________ Scanned and protected by Email scanner

2 1

Problems installing Boost OSX 10.4.11
by Mine 23 Sep '08

23 Sep '08

Hi, I am trying to install Boost 1.35.0_2 as it is a requirement of installing mkvToolnix. I have installed Boost using MacPorts. When I try to install mkvToolnix I get the following error: *** Not checking for wxWidgets: disabled by user request checking for magic_open in -lmagic... no checking for boostlib >= 1.20.0... yes checking whether the Boost::Regex library is available... yes checking for main in -lboost_regex-mt... no checking for main in -lboost_regex-boost_regex-mt... no configure: error: Could not link against boost_regex-boost_regex-mt ! Error: Status 1 encountered during processing. Am I right in thinking that not all the required libraries are being install and if so, how do I configure the install to include them. Thanks, Terrence

2 1

error C2733 second C linkage of overloaded function InterlockedIncrement not allowed
by menuthaur 23 Sep '08

23 Sep '08

Hello, I'm a newbie in using boost. First : For programming I'm using Visual Studio 2008 with SP1 (german edition) and the target platform is Windows CE 6.0 with PXA270 (XScale, ARMVI) processor. And i'm using the STL delivered with Visual Studio. If i include shared_ptr.hpp i get at compiling the errors : "error C2733 second C linkage of overloaded function 'InterlockedIncrement' not allowed." "error C2733 second C linkage of overloaded function 'InterlockedDecrement' not allowed." "error C2733 second C linkage of overloaded function 'InterlockedCompareExchange not allowed." "error C2733 second C linkage of overloaded function 'InterlockedExchange' not allowed." "error C2733 second C linkage of overloaded function 'InterlockedExchangeAdd' not allowed." All errors are targeting to the file interlocked.hpp line 55-63. So my question is, what can i do to solve this problem ? Regards, Marcus Gehr

2 5

App will not run when linked to boost thread library
by kittymaguire 23 Sep '08

23 Sep '08

Hi I have added boost::threads to our mac application, which means that I have to build the boost thread library. I have manage to build the universal boost static and dynamic library. When I add the static library to the project, the project builds with no problems and the dynamic library produced it added to the application package. However as soon a I try to run the application, the application fails with the error that it cannot load the dynamic library. Is there a tool on the mac to determine why a dynamic library does not load. Does anyone know why boost is causing this problem. The dynamic library to built on 10.5 with 10.4 framework. The version of boost is 1.36.0 Thanks in advance Katherine -- View this message in context: http://www.nabble.com/App-will-not-run-when-linked-to-boost-thread-library-… Sent from the Boost - Users mailing list archive at Nabble.com.

4 5

Building for x64 and ia64
by Terdale, Shantibhushan 23 Sep '08

23 Sep '08

I am trying to build for x64 and ia64 and getting few errors. OS: XP Sp2 32 bit Compiler : MSVC 8.0 with SP1 Build Commands : REM Clean All REM .\tools\jam\stage\bin.ntx86\bjam.exe --clean release REM Build x86 .\tools\jam\stage\bin.ntx86\bjam.exe release debug-symbols=on link=static --with-serialization --stagedir=".\bin\release\i386" stage REM Build x64 call "%VS80COMNTOOLS%..\..\vc\bin\x86_amd64\vcvarsx86_amd64.bat" .\tools\jam\stage\bin.ntx86\bjam.exe release debug-symbols=on link=static --with-serialization --toolset=msvc address-model=64 --stagedir=".\bin\release\X64" stage REM Build IA64 call "%VS80COMNTOOLS%..\..\vc\bin\x86_ia64\vcvarsx86_ia64.bat" .\tools\jam\stage\bin.ntx86\bjam.exe release debug-symbols=on link=static --with-serialization --toolset=msvc architecture=ia64 --stagedir=".\bin\release\IA64" stage x86 builds fine. I am getting these errors and I don't see the libs eventually at the end. C:\Documents and Settings\shantibhushan.terdal\Desktop\boost_1_36_0\bin.v2\libs\config\te st\all\no_std_locale_pass.test\msvc-8.0\release\address-model-64\debug-s ymbols-on\link-static\threading-multi\no_std_locale_pass.exe is not a valid Win32 application. C:\Documents and Settings\shantibhushan.terdal\Desktop\boost_1_36_0\bin.v2\libs\config\te st\all\no_std_wstreambuf_pass.test\msvc-8.0\release\address-model-64\deb ug-symbols-on\link-static\threading-multi\no_std_wstreambuf_pass.exe is not a valid Win32 application. C:\Documents and Settings\shantibhushan.terdal\Desktop\boost_1_36_0\bin.v2\libs\config\te st\all\no_std_locale_pass.test\msvc-8.0\release\architecture-ia64\debug- symbols-on\link-static\threading-multi\no_std_locale_pass.exe is not a valid Win32 application. C:\Documents and Settings\shantibhushan.terdal\Desktop\boost_1_36_0\bin.v2\libs\config\te st\all\no_std_wstreambuf_pass.test\msvc-8.0\release\architecture-ia64\de bug-symbols-on\link-static\threading-multi\no_std_wstreambuf_pass.exe is not a valid Win32 application. Is there any way to get around this ? Is it because I am running these tests on x68 machine? I don't have x64 and ia64 machines to test; what is the alternative? Thanks Shanti

3 2