- Boost-users - lists.boost.org

Problem building boost::filesystem on vxworks 6.8 using windriver's workbench
by Reger, Paul 15 Mar '10

15 Mar '10

Hi, We are trying to build version 1.41 of boost::filesystem on vxworks 6.8 using windriver's workbench, using gnu c++ compiler system version 4.1.2 and we are using the build configuration: -D__VXWORKS__ -DBOOST_ASSERT_CONFIG -DBOOST_PLATFORM_CONFIG=\"$(WS_ROOT_DIR)/ThirdParty/Boost/flir//vxworks- 68.hpp\" (We generated vxworks-68.hpp from 1.41's boost/config/platform/vxworks.hpp, and it appears below). But, we are getting the compiler error: C:/AccuRev/Boost/Boost_141_Vx_Port/ThirdParty/Boost/libs/filesystem/src/ operations.cpp:62:30: error: sys/statvfs.h: No such file or directory Anyone see this problem? Got a solution? Thanks, Paul Software Engineer FLIR Systems, Inc. 27700 SW Parkway Ave. Wilsonville, OR 97070 Ph: 503.498.3069 Fx: 503.498.3910 paul.reger(a)flir.com vxworks-68.hpp follows: // Taken from boost 1.41.0 version of the vxworks.hpp platform file. // Modified for use with VxWorks 6.8 // vxWorks specific config options: #define BOOST_PLATFORM "vxWorks 6.8" // disable wide char support // we don't use it anyway #define BOOST_NO_CWCHAR #define BOOST_NO_INTRINSIC_WCHAR_T #define BOOST_NO_STD_WSTRING // added for 6.8 #define BOOST_NO_CWCTYPE // added for 6.8 #define BOOST_NO_STD_WSTREAMBUF // added for 6.8 #define BOOST_NO_SWPRINTF // added for 6.8 // Strict ansi eliminates 64-bit integers - #if defined(__GNUC__) && defined(__STRICT_ANSI__) #define BOOST_NO_INT64_T #warning - 64-bit integer support disabled. #endif // Header file inclusions #define BOOST_HAS_UNISTD_H // these allow posix_features to work, since vxWorks doesn't // define them itself //#ifndef _POSIX_TIMERS //#define _POSIX_TIMERS 1 //#endif //#ifndef _POSIX_THREADS //#define _POSIX_THREADS 1 //#endif // We use the posix schduler in priority mode // #define _POSIX_PRIORITY_SCHEDULING // vxworks doesn't work with asio serial ports // TODO: verify this is still true in 6.8 #define BOOST_ASIO_DISABLE_SERIAL_PORT // boilerplate code: #include <boost/config/posix_features.hpp> Notice to recipient: This email is meant for only the intended recipient of the transmission, and may be a communication privileged by law, subject to export control restrictions or that otherwise contains proprietary information. If you receive this email by mistake, please notify us immediately by replying to this message and then destroy it and do not review, disclose, copy or distribute it. Thank you in advance for your cooperation.

1 0

IOService and socket CAN under Linux
by Andreas Wehrmann 15 Mar '10

15 Mar '10

Hello! I'm currently working with socket CAN under Linux 2.6.25 and was wondering how I can use these with the very handy boost ioservice facility. Socket CAN is simply a raw socket created like this: socket(PF_CAN, SOCK_RAW, CAN_RAW); Does someone maybe already have a socket CAN implementation for Boost? Is there a way I can add a socket descriptor to an IOService and get a callback when the socket becomes readable, so that I can read data from the socket? The peculiarity about raw CAN sockets is, that when they become readable, you don't read the payload of the received CAN frame(s) but a struct that represents the received CAN frame. So it behaves like a datagram socket: You only read full frames. What I actually need is a notification mechanism using the IOService facility. Best regards, Andreas

2 2

[iterator] Help needed understanding output_iterator requirements
by Thomas Klimpel 15 Mar '10

15 Mar '10

Dear iterator experts, Jesse Perla recently reported that boost::multi_array fails compilation for many basic tasks on MSVC 2010. I investigated the failures, because I had already investigated other failures on MSVC 2010 reported by Jesse Perla for boost::ublas. While I'm quite familiar with boost::ublas, I'm a complete novice with respect to boost::multi_array and boost::iterator. I could track the failures to a specific (intentional?) behavior of iterator_facade from Boost.Iterator (more specifically of facade_iterator_category.hpp): http://lists.boost.org/Archives/boost/2010/03/163039.php Thomas Klimpel wrote: > What effectively happens it that the iterator gets the category > "input_iterator", but std::copy wants to have an "output_iterator". I > think I understand why the iterator doesn't satisfies the requirement > of a "forward_iterator", but it's unclear to me why it didn't qualify > as an "output_iterator". There is an "input_output_iterator_tag" in > "boost/iterator/detail/facade_iterator_category.hpp", so it would have > been possible for the iterator to be both "input_iterator" and > "output_iterator". However, it seems to me that > "input_output_iterator_tag" is never used in the Boost.Iterator > library. I would have to read more about "output_iterator" to > understand whether Boost.Iterator is correct here. With my current > understanding of "output_iterator", I would say it's a bug in > "boost/iterator/detail/facade_iterator_category.hpp". > > Perhaps somebody with more knowledge about "output_iterator" and > Boost.Iterator can explain to me why an iterator using the > "boost::random_access_traversal_tag" for the "CategoryOrTraversal" > template parameter of "iterator_facade" will never get the category > "output_iterator" (or "input_output_iterator_tag"). Of course I could go on and read more about "output_iterator", or find out whether the Boost.Iterator documentation has to say something about this issue, but since I only came to this problem because I wanted to help Jesse Perla on a problem with boost::multi_array, I would much prefer if an "iterator expert" could "take over". Regards, Thomas

1 0

Re: [Boost-users] ranking of ublas vector
by Kraus Philipp 14 Mar '10

14 Mar '10

Hi, I think the problem is: we discuss about the "rank" and the "rank index". I my problem I only need the rank index and the value to calculate a new value like: exp( -rank_index) * vec(rank_index) So the smallest element in vec will be multiply with 1 and other elements with values < 1 Phil

2 4

Re: [Boost-users] ranking of ublas vector
by Kraus Philipp 14 Mar '10

14 Mar '10

> Oops. I guess I didn't understand exactly what you wanted. The > temp vector, should contain the result you want. > > In Christ, > Steven Watanabe There is an error: I create a random vector like: [4](0.405121, 0.943918, 0.887914, 0.338921) I think it's clear that: 0.338921 < 0.405121 < 0.887914 < 0.943918 The code returns: [4](2,0,1,3) and that's wrong because the 2nd element is not the smallest value. The (mathematical) rank is: 3, 0, 2, 1 because the 3rd element is the smallest and the first the largest in the original vector. I hope that's clearer Thanks Phil

2 1

Clever simultaneous iteration over multiple containers
by Joseph Wakeling 14 Mar '10

14 Mar '10

Dear Boost users, A (possibly naïve) question, as I'm a reasonably competent C programmer but only a relative novice with C++, and just starting to get used to concepts from libraries like Boost. The BOOST_FOREACH macro provides a nice way to iterate over all the contents of a container like a vector, list, etc. But what about when several containers are involved? I'll give a concrete-ish example from a problem I'm working on. I have two vectors, vector<myClass *> v1 and vector<double> v2 where myClass is a base class and v1.size()==v2.size(). Then, what I want to do is, for(unsigned int i=0;i<v1.size();++i) v1.at(i)->func(v2.at(i)); That works, of course; I'm just wondering if there is a more elegant or compiler-friendly way of writing this along the lines of the BOOST_FOREACH macro. Initialising separate iterators for both v1 and v2 seems ugly/lots of boilerplate. I have seen the solution here: http://permalink.gmane.org/gmane.comp.lib.boost.user/31954 ... but that seems less desirable because it involves using an extra library which I don't think is standard in Linux distros. I have the impression that the zip_iterator boost lib is useful here, but did not fully understand if or how. Can anyone advise? Thanks & best wishes, -- Joe

2 2

serialization error for a struct
by alev mutlu 14 Mar '10

14 Mar '10

Hi all, I am very new to boost. I am getting a serialization error, and I have no idea about what to do #include <boost/serialization/string.hpp> //some other headers struct field { std::string field_name; std::string field_type; std::string field_ref; std::string field_colType; }; int main(int argc, char* argv[]){ vector<field> C; // other definitions // populating the C vector scatter(world, C, relMyValues, w_mySize, 0); } and I got error: struct field has no member named serialize what should I do? thank you in advance

2 2

Compilation problems with MinGW
by Benjamin Lau 14 Mar '10

14 Mar '10

Hello everyone, I successfully compiled Boost with MinGW (GCC 4.4.0 - it came installed with the Qt SDK) with all the settings on, so it has generated both dynamic and static libraries, debug and release versions, multithreaded and non-multithreaded runtimes etc. I tried to compile a small program that uses the serialization library (http://www.boost.org/doc/libs/1_42_0/libs/serialization/doc/tutorial.html#s…) and tried to link it statically with these libraries (in different compilations): libboost_serialization-mgw34-1_40.lib libboost_serialization-mgw34-mt-1_40.lib libboost_serialization-mgw34-mt-s-1_40.lib libboost_serialization-mgw34-mt-s.lib libboost_serialization-mgw34-mt.lib libboost_serialization-mgw34-s-1_40.lib libboost_serialization-mgw34-s.lib libboost_serialization-mgw34.lib Each time I compiled, it would always give me linker errors like so: undefined reference to `__gxx_personality_sj0' undefined reference to `_Unwind_SjLj_Register' undefined reference to `_Unwind_SjLj_Unregister' undefined reference to `_Unwind_SjLj_Resume' These are repeated over and over again. The compiler command and flags that I use are g++ test.cpp -o test -Ipath/to/boost/include path/to/static/library However, if I compile it with an import library like boost_serialization-mgw34.lib I don't get such errors. Searching online seems to suggest I am missing a compiler flag, but I cannot determine which one I am missing. Perhaps my Google-Fu isn't strong enough, so if I did miss out something patently obvious that could have been found online I offer my due apologies. Thanks a lot anyway! Benjamin

2 2

[serialization] installed documentation bug and suggestions.
by Mostafa 14 Mar '10

14 Mar '10

Bugs: I've had bad internet connection so I had to resort to using the installed boost docs and noticed some bugs. 1) /share/doc/boost/libs/serialization/doc/index.html has broken links in the left frame. 2) /share/doc/boost/libs/serialization/doc/archive_reference.html has broken links in the following paragraph: //Start As a convenience, small header files have been included which contain typedef for polymorphic implementation for each corresponding templated one. For example, the headers polymorphic_text_iarchive.hpp and polymorphic_text_oarchive.hpp. contain the typedef for the polymorphic implementation of the standard text archive classes text_iarchive.hpp and text_oarchive.hpp respectively. All included polymorphic archives use the same naming scheme. //End Suggestion: 1) It's not readily apparent that there's a polymorphic implementation of the serialization classes, may be this should be mentioned in the tutorial? 2) Or have a section in the Overview page categorizing the available categories of serializors as intrusive, non-intrusive, polymorphic, giving a short definition of each type, and their pros/cons. Basically what is missing is an eye-ball summary of the available serializors that this library offers, and why one would choose one over the other and vice versa. The information is there, but it is scattered and it took some digging to get to it. For example, from the overview page one cannot deduce that there exists an intrusive, or polymorphic version. It is only from Tutorials page can one immediately deduce that there is an intrusive version, and to figure out there is a polymorphic version one has to navigate the following path: Reference link in left frame -> Archive Class Reference. Also, best practices/potential pitfalls like the following suggestion: //Start // /share/doc/boost/libs/serialization/doc/tutorial.html#nonintrusiveversion Note the serialization of the base classes from the derived class. Do NOT directly call the base class serialize functions. Doing so might seem to work but will bypass the code that tracks instances written to storage to eliminate redundancies. It will also bypass the writing of class version information into the archive. For this reason, it is advisable to always make member serialize functions private. //End should be made more eye grabbing. It's very easy to accidentally skip over such information. Thanks, - Mostafa

3 4

Boost.Thread idiom
by anony 14 Mar '10

14 Mar '10

Is is possible to inherit from boost::thread and then store pointers to instantiated objects of such classes in say ptr_vector<>? I need to interrupt() a specific thread now and then and once you commit a thread to thread_group you can only interrupt them all at once.

2 4