- Boost-users - lists.boost.org

Errors building boost 1.35.0 under mingw (serialization related)
by Jose Manuel Pulido 30 May '08

30 May '08

Hello, this is my firs try to build boost under windows vista using mingw-3.4.5, so I'm totally newbie, and I'm getting several compiling errors. The first one is this: *gcc.link.dll bin.v2\libs\serialization\build\gcc-mingw-3.4.5\release\threading-multi\boost_serialization-mgw34-mt-1_35.lib Creating library file: bin.v2\libs\serialization\build\gcc-mingw-3.4.5\release\threading-multi\boost_serialization-mgw34-mt-1_35.lib bin.v2\libs\serialization\build\gcc-mingw-3.4.5\release\threading-multi\codecvt_null.o:codecvt_null.cpp:(.rdata$_ZTVN5boost7archive12codecvt_nullIwEE[vtable for boost::archive::codecvt_null<wchar_t>]+0x14): undefined reference to `std::codecvt<wchar_t, char, int>::do_unshift(int&, char*, char*, char*&) const' *After googling for a while, I found this discussion: http://thread.gmane.org/gmane.comp.lib.boost.user/34741 where removing the line #47 from libs/serialization/build (this line's content is codecvt_null) was proposed as a solution. It seems this didn't completely work since the previous error disappeared, but I got a new one and I haven't been able to find a possible solution. The error message is this: * gcc.compile.c++ bin.v2\libs\serialization\build\gcc-mingw-3.4.5\release\threading-multi\basic_text_wiprimitive.o libs\serialization\src\basic_text_wiprimitive.cpp:14:2: #error "wide char i/o not supported on this platform" *Any help will be appreciated. Regards: J. Pulido

2 1

Re: [Boost-users] Problems using pre-compiled boost libraries
by Fanara, Mark A (GE Infra, Transportation) 30 May '08

30 May '08

I tried changing Configuration Properties->Linker->Manifest File->Generate Manifest setting to No. When executing the program, I get the following error message. Debug Error! Program: ... R6034 An application has made an attempt to load the C runtime library without using a manifest. This is an unsupported way to load Visual C++ DLLs. You need to modify your application to build with a manifest. For more information, see the "Visual C++ Libraries as Shared Side-by-Side Assemblies" topic in the product documentation.

2 1

Precompiled Boost.Thread libs for Linux?
by CSB 30 May '08

30 May '08

I see references to pre-compiled Boost libs but I'm unable to find them. I'm interested in the latest Boost.Thread for Linux. Can someone tell me where to find this? Thanks.

4 3

filesystem headers
by Christian Holmquist 30 May '08

30 May '08

Hi, I found the filesystem headers to be very confusion, the grouping of classes and functions into headers seems to have been chosen arbitrary. basic_recursive_directory_iterator in convenience.hpp? basic_directory_iterator in operations.hpp? shouldn't they use headers of their own, or at least use filesystem/iterator.hpp ? create_directories is in convenience.hpp, but create_directory in operations.hpp? the free function extension(path) is in convenience.hpp, although I think most users would expect it to be a member of the basic_path class instead. a rather highlevel (IMO) function copy_file is in operations.hpp, while others like change_extension is in convenience.hpp. what should I expect to find in convenience.hpp that is not in operations.hpp? basic_filesystem_error, which is an std::exception derived class is in path.hpp, shouldn't it go into exceptions.hpp? maybe someone could shed some light on how I should understand the api in order to include the correct header.. More about path.hpp.. I think the use of iterator_facade in path.hpp is unfair to users, since it pulls in so much of complicated headers (have a look at iterator_facade.hpp) only to ease the task of implementing that path::iterator. I think that iterator_facade is a great tool for users that quickly wants to design a working iterator, but in a header such as filesystem::path that -should- be used everywhere where a file reference is needed, it should be rather lightweight (instead we use std::string, because it compiles with reasonable speed. I think we are not alone on this choice). The inclusion of iosfwd only for stream operators is again not what I would prefer, better off putting that stuff in path_io.hpp is type_traits/is_same.hpp, throw_exception.hpp, static_assert.hpp used in path.hpp at all? Sorry for all the complains, I wouldn't write them unless I really, really wanted to use boost::filesystem. Finally there's a better way to do file and path operations in c++, but it's not practical in its current form. I've been trying with no success incorporating filesystem more in our very large code base, but compilation times and confusion about headers have made me redraw most of that code. Regards, Christian

5 9

[Serialization] Serialization of a class in a DLL
by Cyril Picat 29 May '08

29 May '08

Hi everybody, I have just tried a simple example of a class serialization in a DLL and did not manage to make it work. I have been using Boost serialization since a while but until now I was putting all the serialization code in the .hpp. By the way thanks Robert (and Boost) for this great library. I am using MSVC 8.0 and Boost 1.34.1. I have tried the same with Boost Serialization 1.36 (head of Boost) without any success. My test is the following. The class MyClass in declared in a DLL boost-example.dll built from Example.cpp. A test program Example.t.cpp linked with boost-example.dll try to serialize MyClass to an XML archive. The files are the following: //////// Example.hpp #if _MSC_VER > 1000 #pragma once #endif // Do NOT include any headers after this point #if (defined(__COMPILING_Example_CPP__) && defined(WIN32)) #define _LIBSPEC __declspec(dllexport) #else #define _LIBSPEC #endif class _LIBSPEC MyClass { public: MyClass(); private: friend class boost::serialization::access; template <class Archive> void serialize(Archive & ar, const unsigned int version); std::string m_str; }; //////// Example.cpp #include <string> #include "boost/archive/xml_oarchive.hpp" #include "boost/archive/xml_iarchive.hpp" #include "boost/serialization/nvp.hpp" #include "boost/serialization/export.hpp" #include "Example.hpp" using namespace std; BOOST_CLASS_EXPORT(MyClass); // should explicity instantiate template for // xml_oarchive and xml_iarchive MyClass::MyClass() : m_str("MyClass") {} template <class Archive> void MyClass::serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(m_str); } //////// Example.t.cpp #include <iostream> #include <fstream> #include "boost/archive/xml_oarchive.hpp" #include "boost/serialization/nvp.hpp" #include "Example.hpp" using namespace std; int main(int argc, char* argv[]) { MyClass myClass; // try to serialize MyClass using an XML archive ofstream ofs("myClass.xml"); if( !ofs ) { cout << "ERROR: Could not open myClass.xml for writing"; return EXIT_FAILURE; } try { boost::archive::xml_oarchive oa(ofs); oa << BOOST_SERIALIZATION_NVP(myClass); } catch (const std::exception& e) { cout << "failed to serialize MyClass with xml_oarchive: " << e.what(); ofs.setstate(ios::failbit); } return EXIT_SUCCESS; } When compiling this, I got an error at link time for Example.t: Example.t.obj : error LNK2019: unresolved external symbol "private: void __thisc all MyClass::serialize<class boost::archive::xml_oarchive>(class boost::archive: :xml_oarchive &,unsigned int)" (??$serialize@Vxml_oarchive@archive@boost@@@MyCla ss@@AAEXAAVxml_oarchive@archive@boost@@I@Z) referenced in function "public: stat ic void __cdecl boost::serialization::access::serialize<class boost::archive::xm l_oarchive,class MyClass>(class boost::archive::xml_oarchive &,class MyClass &,u nsigned int)" (??$serialize@Vxml_oarchive@archive@boost@@VMyClass@@@access@seria lization@boost@@SAXAAVxml_oarchive@archive@2@AAVMyClass@@I@Z) I have taken a look at boost-example.dll with Dependency Walker and there are quite a few symbols exported for MyClass and boost::archive::xml_oarchive. Any clue of what is going on? The strange thing is that I have another more complex example with an abstract class and derived classes in separate DLLs where I serialize to the base pointer and everything is compiling and working fine (both with 1.34.1 and HEAD). I have read the doc ('Exporting Class Serialization') and have seen in the logs that a lot have changed regarding export since 1.34.1. In what I have understood, the fix was concerning cases where the macro BOOST_CLASS_EXPORT() is used in the .hpp, leading to multiple registrations, and not in the .cpp as I am doing. Am I right? By the way, I have noticed a little typo in the doc concerning void_cast_register. In the doc the proposed syntax is 'boost::serialization::void_cast_register<derived, base>(static_cast<base *>(NULL), static_cast<derived *>(NULL))' although in my experience the correct syntax is: 'boost::serialization::void_cast_register<derived, base>(static_cast<derived*>(NULL),static_cast<base*>(NULL))' Thanks in advance, Cyril Picat

3 5

Re: [Boost-users] Problems using pre-compiled boost libraries with Visual Studio 2005
by Igor R 29 May '08

29 May '08

> I am building a VC8.0 (Visual Studio 2005) application that is making > use of boost::program_options and boost::filesystem. My application > links fine, but when I try to execute the program, I get an error > message about a missing "MSVCP80D.dll" (or "MSVCP80.dll" when building > for release). I don't have those .dlls on my machine. MSVCPXX.dll is dynamically-linked STL. It's pretty strange that the standard VS installation didn't install it. > Next error message received is "This application has failed to start > because the application configuration is incorrect. Review the manifest > file for possible errors. Reinstalling the application may fix this > problem. For more details, please see the application event log." Well, you can just disable the manifest in your project properties (something like Properties-->Manifest-->generate manifest = No).

1 0

Is there a limit for the number of threads created by thread_group.create_thread() ?
by Li, PingShan (Kansas City) 29 May '08

29 May '08

Here is what I learned for Linux. In Linux, a thread is the same as process. For redhat, the default stack size for a process is 10240k. this can be checked and changed by "ulimit " command. Setting different stack size will affect how many threads can be created for Linux.

1 0

ASIO question
by Andrej van der Zee 29 May '08

29 May '08

Hi, I am thinking how to use ASIO for my specific situation. Well, I'll try to explain: I have a client that is connected to multiple remote daemons. Now the client can initiate alternating "start" and "stop" messages to it's daemons like this: * send a "start" message to all daemons * send a "stop" message to all the daemons * send a "start" message to all the daemons * send a "stop" message to all daemons etc I want to be able to have multiple threads sending a "start" or a "stop" to all connected daemons using boost::asio::async_write(). But this has to be in phases, so all threads handling a "start" should finish first before a "stop" can be initiated. I was wondering if this is solvable using ASIO and if so, hopefully somebody can point me in the right direction. Cheers, Andrej __________________________________________________________ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html

2 1

what's up with the logging libraries?
by Jeff 29 May '08

29 May '08

Hello everyone, When will a logging library make it out of sandbox and into an official release? Can we expect to get a logging library in 1-36 ? Thanks!

5 7

[Serialization][Archive] Namespace leakage problem
by Anders Sundman 29 May '08

29 May '08

Hi! The following code compiles fine with boost 1.34.1 (as it should) but fails to compile with 1.35.0 and the boost trunk (rev. 45896) #include "boost/archive/binary_iarchive.hpp" namespace detail { struct fu {}; } struct bar : detail::fu {}; Visual studio 2005 generates the following error message: 1>c:\dev\sandbox\using_scope_test\using_scope_test\test.cpp(7) : error C2872: 'detail' : ambiguous symbol 1> could be 'detail' 1> or 'boost::detail' It seems to me that the include file is some how leaking the boost namespace to it's surrounding? Explicitly qualifying the line: struct bar : ::detail::fu {}; works as expected. But I'm also allowed to write: struct bar : boost::detail::fu {}; which gives the error "'fu' : is not a member of 'boost::detail'" and not the expected "'boost' : is not a class or namespace name". Is this a known problem, and if so is there also a known patch? Best Regards, Anders Sundman

1 1