- Boost-users - lists.boost.org

[Interprocess] WIN32 define case unaccessible ?
by Antoine Pédron 10 Feb '13

10 Feb '13

Hello, I'm using Boost.Interprocess in order to get a single portable source code between Windows and Linux using Mutexes and Shared Memory. Documentation says that, for Windows, the API default behaviour is emulation with mapped files, which is the case (:D). Though, having a look at interprocess' headers, i encountrered this case : from D:\Libraries\boost\boost_1_51\boost\interprocess\sync\named_mutex.hpp : ____________________________________________________________________________ #if defined(BOOST_INTERPROCESS_NAMED_MUTEX_USES_POSIX_SEMAPHORES) #include <boost/interprocess/sync/posix/named_mutex.hpp> #define BOOST_INTERPROCESS_USE_POSIX_SEMAPHORES #elif !defined(BOOST_INTERPROCESS_FORCE_GENERIC_EMULATION) && defined (BOOST_INTERPROCESS_WINDOWS) #include <boost/interprocess/sync/windows/named_mutex.hpp> #define BOOST_INTERPROCESS_USE_WINDOWS #else #include <boost/interprocess/sync/shm/named_mutex.hpp> #endif ____________________________________________________________________________ A case where BOOST_INTERPROCESS_FORCE_GENERIC_EMULATION is not defined and BOOST_INTERPROCESS_WINDOWS is, meaning that i can use Windows standard API. My problem is that i want to use this case and i wonder how to reach it. The former file includes boost/interprocess/detail/workaround.hpp where both symbols are defined : ____________________________________________________________________________ #if defined(_WIN32) || defined(__WIN32__) || defined(WIN32) #define BOOST_INTERPROCESS_WINDOWS #define BOOST_INTERPROCESS_FORCE_GENERIC_EMULATION #define BOOST_INTERPROCESS_HAS_KERNEL_BOOTTIME ____________________________________________________________________________ and i can't see an #undef anywhere to get into the case i want. Thanks in advance, Antoine

2 1

Testing whether result_of<F(U)> is a valid expression
by oswin krause 08 Feb '13

08 Feb '13

Hi, Is it possible to evaluate, whether a certain argument type given to a functor will lead to a valid expression with the result_of template? i am trying to achieve the following, maybe there is a better way to do it: template<class T, class F> Container< typename boost::result_of<F(T)>::type > transform( Container<T> c, F f, std::disable_if<valid_expression<F(Block<T>) > >::type* dummy = 0 ){ //slow default implementation Container<T> res(c.size()); std::transform(c.begin(),c.end(),res.begin(),f): return res; } //blocked implmentation of transform template<class T, class F> Container< typename boost::result_of<F(T)>::type > transform( Container<T>, F functor, std::enable_if<valid_expression<F(Block<T>) > >::type* dummy = 0 ){ //functor supports fast implementation Container<T> res(c.size()); std::transform(c.blocks().begin(),c.blocks().end(),res.blocks().begin(),functor): return res; } the question is, how valid_expression<F(Block<T>) > could be implemented and right now the only mechanism which get's close to what i want would be checking result_of<F(Block<T>)> is valid. Greetings, Oswin

4 4

Re: [Boost-users] How do you compile Boost C++ code in Ubuntu?
by Giovanni 08 Feb '13

08 Feb '13

Greetings All, Thank you so much, Mr. Maddock. I was able to compile my program successfully and resolve my linking errors with your help. Also, thank you very much, Mr. Loskot! I appreciate all the precious time that you have spent to help me out. Have an awesome weekend! Regards On Fri, Feb 8, 2013 at 8:20 AM, John Maddock <boost.regex(a)virgin.net> wrote: > It is a quirk of GCC that the libraries used by a source file must appear > *after* the source file. Nothing to do with Boost really... > > John. On Fri, Feb 8, 2013 at 9:45 AM, Mateusz Loskot <mateusz(a)loskot.net> wrote: > On 8 February 2013 16:03, Giovanni <giovanni.ong(a)comsoc.org> wrote: >> I followed your instructions to link the libraries, with the >> "-lboost_filesystem -lboost_system" sequence of linking the >> aforementioned Boost C++ libraries. >> >> However, I cannot resolve the linking error. I have included a >> snippet from my Terminal session below. > > No idea what's wrong really and have no time to investigate it. > But, I've done quick test on Ubuntu 10.04 using Boost 1.40 > installed from its packages and small sample from this book > http://en.highscore.de/cpp/boost/errorhandling.html > and it worked for me: > > Here is my console log: > > mloskot@vb-ubuntu104-x64:~/tmp$ /usr/bin/lsb_release -d > Description: Ubuntu 10.04.4 LTS > > mloskot@vb-ubuntu104-x64:~/tmp$ cat bsystem.cpp > #include <boost/system/error_code.hpp> > #include <iostream> > #include <string> > > class application_category : > public boost::system::error_category > { > public: > const char *name() const { return "application"; } > std::string message(int ev) const { return "error message"; } > }; > > application_category cat; > > int main() > { > boost::system::error_code ec(14, cat); > std::cout << ec.value() << std::endl; > std::cout << ec.category().name() << std::endl; > } > > mloskot@vb-ubuntu104-x64:~/tmp$ g++ -L/usr/lib -lboost_system bsystem.cpp > mloskot@vb-ubuntu104-x64:~/tmp$ ./a.out > 14 > application > > mloskot@vb-ubuntu104-x64:~/tmp$ ldd ./a.out |grep boost > libboost_system.so.1.40.0 => /usr/lib/libboost_system.so.1.40.0 > (0x00007f2df87b6000) > > > Perhaps something has changed in later versions. > I have no time to dig it deeper, sorry. > > Best regards,

1 0

Re: [Boost-users] How do you compile Boost C++ code in Ubuntu?
by Giovanni 08 Feb '13

08 Feb '13

Greetings, I realized that when I installed certain packages from the Ubuntu Software Center, I had broken some dependencies. That may have caused the problem. Now, I have reinstalled Boost C++. See the following for a snippet from the Terminal session that indicates the availability of the previously missing files. Go Bears >ls -al | grep libboost_system -rw-r--r-- 1 root root 48666 Jan 2 2012 libboost_system.a lrwxrwxrwx 1 root root 17 Jan 2 2012 libboost_system-mt.a -> libboost_system.a lrwxrwxrwx 1 root root 25 Jan 2 2012 libboost_system-mt.so -> libboost_system.so.1.46.1 lrwxrwxrwx 1 root root 25 Jan 2 2012 libboost_system.so -> libboost_system.so.1.46.1 -rw-r--r-- 1 root root 14568 Jan 2 2012 libboost_system.so.1.46.1 Go Bears > Go Bears >make all g++ -L/usr/lib -lboost_system get_sys_info.cpp /tmp/cckONUUl.o: In function `__static_initialization_and_destruction_0(int, int)': get_sys_info.cpp:(.text+0x13f): undefined reference to `boost::system::generic_category()' get_sys_info.cpp:(.text+0x14b): undefined reference to `boost::system::generic_category()' get_sys_info.cpp:(.text+0x157): undefined reference to `boost::system::system_category()' /tmp/cckONUUl.o: In function `boost::filesystem3::path::codecvt()': get_sys_info.cpp:(.text._ZN5boost11filesystem34path7codecvtEv[boost::filesystem3::path::codecvt()]+0x5): undefined reference to `boost::filesystem3::path::wchar_t_codecvt_facet()' collect2: ld returned 1 exit status make: *** [all] Error 1 Go Bears > So, I am back to square one with the "undefined reference" compilation error. Can you please kindly suggest how can I resolve this problem? Thank you. Regards On Thu, Feb 7, 2013 at 8:33 AM, Mateusz Loskot <mateusz(a)loskot.net> wrote: > On 7 February 2013 15:21, Giovanni <giovanni.ong(a)comsoc.org> wrote: >> >> I had set the shell variable $LD_LIBRARY_PATH to: >> /usr/lib/libboost_system.so. It was originally empty. I used the >> "echo" command to reflect the path that I had set it to. > > I tried to make a point not about how you did set the variable, > but about the fact it has incorrect value. > Let me copy it once again: > > "LD_LIBRARY_PATH, which is a colon-separated list of directories" [1] > > [1] http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html > > And you may learn from that what the LD_LIBRARY_PATH is meant to be. > >> I had installed it with Ubuntu Software Center. >> Here is a snippet of: /usr/lib >> [...] >> -rw-r--r-- 1 root root 14568 Jan 2 2012 libboost_system.so.1.46.1 >> -rw-r--r-- 1 root root 14568 Jan 5 2012 libboost_system.so.1.48.0 > > You seem to be missing libboost_system.so library or symlink named > libboost_system.so with one of the two as a target. > It may look the installation is broken. > >> When I followed your instructions to install it (again), I couldn't. >> Here is the transcript from the Terminal. >> Go Bears >sudo apt-get install libboost-system-dev >> [sudo] password for arvind: >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> Some packages could not be installed. This may mean that you have >> requested an impossible situation or if you are using the unstable >> distribution that some required packages have not yet been created >> or been moved out of Incoming. >> The following information may help to resolve the situation: >> >> The following packages have unmet dependencies: >> libboost-system-dev : Depends: libboost-system1.46-dev but it is not >> going to be installed >> E: Unable to correct problems, you have held broken packages. > > Clearly, something is broken with installation of boost packages in your system. > You should seek for help from Ubuntu folks, it's unrelated to Boost. >

3 4

[python] how to call python's built-in type() function
by Eric Niebler 08 Feb '13

08 Feb '13

In C++, I have a boost::python::object that is wrapping ... something. I'd like to find out what. If I were in python land, I'd call the built-in 'type' function on it. What do I do in C++? Thanks in advance, -- Eric Niebler Boost.org

2 1

Problem with boost 1.53 compilation in Windows
by DUNDEK Ivan 08 Feb '13

08 Feb '13

Hi. We are using boost in our project, and now with 1.53 and some added options we are unable to compile the boost in Windows. In Linux, the build is OK. It seems, that when compiling under Windows, the path for compiled boost obj files depends on the options specified, so if there are many options specified, the path become too long. With reduced number of options, the build is OK. Build environment: Windows7 64bit, Boost 1.53, VisualStudio 2010 Express Here is the build command: bjam -d2 --toolset=msvc-10.0 variant=debug,release threading=multi link=static runtime-link=shared install boost.locale.std=on boost.locale.icu=off boost.locale.winapi=off boost.locale.posix=off -a --with-log --with-thread --with-system --with-date_time --with-filesystem --with-program_options --with-iostreams --with-regex --with-serialization --with-locale --with-atomic define=BOOST_LOG_NO_SETTINGS_PARSERS_SUPPORT --prefix="c:\projects\cpce-cpp-stack\1.3.0\win" -sZLIB_SOURCE="c:\projects\cpce-cpp-stack\1.3.0\win\third-party\zlib-1.2.7" And the output: Performing configuration checks - iconv (libc) : no - iconv (separate) : no - has_icu builds : no Component configuration: - atomic : building - chrono : not building - context : not building - date_time : building - exception : not building - filesystem : building - graph : not building - graph_parallel : not building - iostreams : building - locale : building - log : building - math : not building - mpi : not building - program_options : building - python : not building - random : not building - regex : building - serialization : building - signals : not building - system : building - test : not building - thread : building - timer : not building - wave : not building ...patience... ...patience... ...patience... ...patience... ...found 30159 targets... ...updating 10944 targets... …. file bin.v2\libs\program_options\build\msvc-10.0\debug\boost.locale.icu-off\boost.locale.posix-off\boost.locale.std-on\boost.locale.winapi-off\link-static\threading-multi\split.obj.rsp "libs\program_options\src\split.cpp" -Fo"bin.v2\libs\program_options\build\msvc-10.0\debug\boost.locale.icu-off\boost.locale.posix-off\boost.locale.std-on\boost.locale.winapi-off\link-static\threading-multi\split.obj" -TP /Z7 /Od /Ob0 /W3 /GR /MDd /Zc:forScope /Zc:wchar_t /wd4675 /EHs -c -DBOOST_ALL_NO_LIB=1 -DBOOST_LOG_NO_SETTINGS_PARSERS_SUPPORT "-I." compile-c-c++ bin.v2\libs\program_options\build\msvc-10.0\debug\boost.locale.icu-off\boost.locale.posix-off\boost.locale.std-on\boost.locale.winapi-off\link-static\threading-multi\split.obj call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86 >nul cl /Zm800 -nologo @"bin.v2\libs\program_options\build\msvc-10.0\debug\boost.locale.icu-off\boost.locale.posix-off\boost.locale.std-on\boost.locale.winapi-off\link-static\threading-multi\split.obj.rsp" split.cpp failed to write output file 'bin.v2\libs\program_options\build\msvc-10.0\debug\boost.locale.icu-off\boost.locale.posix-off\boost.locale.std-on\boost.locale.winapi-off\link-static\threading-multi\libboost_program_options-vc100-mt-gd-1_53.lib.rsp'! c:\projects\cpce-cpp-stack\1.3.0\src\boost_1_53_0>cd "c:\projects\cpce-cpp-stack\1.3.0\win" Thank you for advice Best regards Ivan Dundek.

2 2

Problem linking with boost 1, 51 64-bits from boostpro, VC10
by Alain Leblanc 07 Feb '13

07 Feb '13

Hi, I'm having some issues linking my code with the 64-bit version of boost 1.51 on windows with VC 10. I managed to write this small example that illustrates my problem. It is a project to create a DLL. I downloaded from boostpro.com. Here's the code: #include <boost/regex.hpp> #include <boost/filesystem.hpp> void useBoost() { } and the result. ------ Build started: Project: test-64, Configuration: Release x64 ------ UsesRegex.cpp UsesRegex.obj : error LNK2001: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::system_category(void)" (?system_category@system@boost@ @YAAEBVerror_category@12@XZ) UsesRegex.obj : error LNK2001: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::generic_category(void)" (?generic_category@system@boost@ @YAAEBVerror_category@12@XZ) C:\Users\aleblanc\projects\trunk\XDE\sandbox\alain\c-testing\test-64\x64\Release\test-64.dll : fatal error LNK1120: 2 unresolved externals ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== However, if I comment out the include for filesystem.hpp it compiles ok. I have included the path to the boost libraries in the 'Additional Library Directories' property for the linker. otherwise it complains about not finding the library for boost_regex. Compiling for 32 bit (with the path for the libraries to a 32-bit installation of boost) works fine. Any suggestion would be appreciated. Thanks, a

3 3

boost compiler warnings
by Dave Dyer 07 Feb '13

07 Feb '13

Using boost 52 on OSX / 64 and xcode 4, the new mac compiler produces a lot of "semantic issue" warnings. I assume these are all not consequential, but is this lint being addressed? The two issues it is complaining about is that "long" is compiled as int64, and that using string literals as char * is deprecated.

2 1

Serialization: BOOST_CLASS_EXPORT changes between 1.38 and 1.52
by Nathan Whitehorn 07 Feb '13

07 Feb '13

I'm upgrading a large data analysis project from boost 1.38 to 1.52 (see this 2008 Boostcon talk for details: http://www.icecube.umd.edu/~troy/talks/icefishing.pdf) Everything has gone remarkably smoothly, with a minimal degree of #if, except for one thing: a change in the semantics of BOOST_CLASS_EXPORT. The software is organized into a number of shared libraries each of which have serializable classes that generally inherit from a shared base class, through pointers to which the derived classes are almost always [de]serialized to/from a custom archive type. When using 1.38, the BOOST_CLASS_EXPORT directive was kept in the implementation file for each serializable class. This almost still works for 1.52 but can result in strange behavior that took me two days to track down. Some of our classes would report through unregistered class errors on [de]serialization. Which ones would depend on circumstances, compiler version, linker, and operating system. The reason turns out to be changes in handling of the class GUID. This is associated to the pointer serializer by BOOST_CLASS_EXPORT -- but also now apparently by the first instantiated code [de]serializing the class through that archive directly based on the presence of a template specialization of boost::serialization::guid<T>() currently in scope, which is NULL by default. Once NULL is set as the GUID, it stays that way, regardless of a proper BOOST_CLASS_EXPORT later. This occurred in our case as a result of def_pickle() calls in boost.python bindings that used the same classes and archive type. This can be fixed by BOOST_CLASS_EXPORT_KEY in all appropriate header files. Adding it is a sizeable amount of work (hundreds of classes) but I'm more concerned the mechanism is very fragile in the case of templates and I'm not sure what to do there. For example, we have a generic serializable container. Any specialization of it needs to be registered with BOOST_CLASS_EXPORT, which is fine, but anyone using that specialization needs to also include a header file BOOST_CLASS_EXPORT_KEY() in it for that particular specialization as well. In other words, you can't just use container<Foo> and expect it to work reliably and, moreover, if you use it *once* without having seen the right in-scope macro, it will break serialization of that type globally if you happen to have linked against a library that made this mistake. Probably. Depending on initialization order. So my questions: 1. Is it possible for things that would return GUIDs of NULL to try harder and look in a global registry instead of silently breaking things? This kind of global lookup was how 1.38 always worked and it seems considerably less fragile. 2. Is there a way to handle BOOST_CLASS_EXPORT_KEY() sanely in the case of templates without the risk of silent serialization failures -- in all instances of that class -- that depend on global initialization order? 3. Is it possible to change the GUID set in the extended type info object of a pointer_[i/o]serializer at runtime after the class has been added to the export registry? 4. Are there any suggested mechanisms for local hacks, given that we control the archive implementation, to implement 1-3 without changes to boost? -Nathan

2 3

[serialization] Support for Boost.Container?
by Jensen, Erik A 07 Feb '13

07 Feb '13

I see that Boost.Serialization has support for serializing STL containers, such as std::vector. However, I can't seem to serialize a boost::container::vector. Do I need to do something special to get this to work, or is it not supported? I need guaranteed support for incomplete types, so I can't use an STL vector. If it is not supported, what is my best bet, for now? Are there any plans to do so? Using Boost.Serialization with Boost.Container is something I would expect to just work, and it seems like most of the STL code could be reused. Thanks.

6 7