- Boost-users - lists.boost.org

Fwd: Boost.Locale - Help linking to ICU static libraries please
by Brad Keifenheim 27 Feb '13

27 Feb '13

Hello, I'm building Boost 1.53.0 on FreeBSD using GCC. I wish to provide the ICU back-end to Boost.Locale using the static implementation only. This is the command line I used to configure and build ICU 49.1.2: runConfigureICU FreeBSD --prefix=/3rdParty/icu4c/release --bindir=/3rdParty/icu4c/release/bin64 --sbindir=/3rdParty/icu4c/release/sbin64 --libdir=/3rdParty/icu4c/release/lib64 --enable-static=yes --enable-shared=no --with-library-bits=64 CPPFLAGS=-DU_TIMEZONE=0 The DU_TIMEZONE flag is a workaround for ICU on FreeBSD for that particular version. For this discussion it may safely be ignored. The ICU build results as follows: /3rdParty/icu4c/release |_ bin64 |_ include |_ lib64 |_ sbin64 |_ share As intended, the shared (*.so) libraries are not built. Only static (*.a) libraries are present in lib64: libsicudata.a, libsicui18n.a, libsicuio.a, etc... I then attempt the following command to build Boost: b2 toolset=gcc link=static variant=release threading=multi address-model=64 --build-dir=obj --stagedir=bin/64 --without-python -sICU_PATH=/3rdParty/icu4c/release/ --layout=versioned -a -j8 With this setup the build reports as follows: *...* * * *Performing configuration checks* * * * - x86 : yes* * - has_icu builds : no* *warning: Graph library does not contain MPI-based parallel components.* *note: to enable them, add "using mpi ;" to your user-config.jam* * - iconv (libc) : no* * - iconv (separate) : no* * - icu : no* * - icu (lib64) : no* *- Boost.Locale needs either iconv or ICU library to be built.* * * *...* I do not have this problem when -sICU_PATH points to a directory containing the shared versions of the ICU libraries: libicudata.so, libicui18n.so, libicuio.so ... Unfortunately the constraints of the end product restrict me from delivering ICU as a shared library. Will Boost.Locale accept the ICU back-end as a static library implementation? If so, what have I configured improperly? Thank you in advance for your assistance. Brad

1 0

[CONFIG] static const definitions
by John M. Dlugosz 27 Feb '13

27 Feb '13

On 2/27/2013 1:23 PM, boost-users-request-at-lists.boost.org |Boost/Allow to home| wrote: > Exactly, hence my suggestion for performing a preprocessor check > around the out-of-line definition. I suppose it would be nice to have > a BOOST-y preprocessor def that could let you know if this is the > case... OK, now we're getting somewhere. You understand that this is exactly what I _am_ doing. My questions is, how does Boost determine which compilers in which it should withhold the definition? Do you know of an example of one someplace?

2 1

[CONFIG] static const definitions
by John M. Dlugosz 27 Feb '13

27 Feb '13

On 2/27/2013 10:35 AM, boost-users-request-at-lists.boost.org |Boost/Allow to home| wrote: > ...and then we use preprocessor checks to decide whether or > not to provide definitions in a cop [cpp?] file. It is best to provide them for > gcc, but not for msvc 2010 for example. Yes, exactly. So what macro does CONFIG provide to determine whether they should be present or absent?

1 0

Re: [Boost-users] Boost.MSM cc1plus.exe:: error: out of memory allocating 65532
by degoah 27 Feb '13

27 Feb '13

Hi Christophe, I will check the thing with the cstor. FYI: my library that uses the boost.msm-based state machine mechanism shall be released as shared library. It is used to realize Remote Procedure Calls. So my library consists of one Master state machine (which consists of 5 submachines and together 21 states) and one Slave state machine (which consists of 4 submachines and 19 states). The user application linking against my library has the possibility to choose if the slave state machine or the master state machine part shall be used. Now the problem could be, that I use a boost::variant type to store the 44 different application event types. This variant type I pass to the process_event method of each state machine (master and slave) although the slave state machine doesn't support the same event types like the master and vice-versa. This produces unnecessary template invocations and memory allocation. So the solution could be, to split my single shared library into two shared libraries: one for the master and one for the slave logic and each of it has a reduced boost::variant type( just with the event types of the concrete state machine). Or I keep the solution with the single shared library and I split the single boost::variant type into two different ones: one for the master and one for the slave state machine. And each boost::variant type will just be forwarded to the appropriate process_event method of the corresponding state machine. Doing so, will also prevent unnecessary template invocations for each event type on the corresponding state machine. Maybe this will also reduce the memory consumption... What is your opinion about this two putative solutions? Best regards (viele grüsse), Rafael Christophe Henry <christophe.j.henry(a)googlemail.com> schrieb: ----- Original Message ----- From: "RaRi" <degoah(a)gmx.de> Newsgroups: gmane.comp.lib.boost.user To: <boost-users(a)lists.boost.org> Sent: Wednesday, February 27, 2013 6:44 PM Subject: Re: Boost.MSM cc1plus.exe:: error: out of memoryallocating 65532 > Thank you all so far, > > I will investigate, how I can simplify my state machine and reduce the > number of events. > > Damn, I spent 1 month on that machine and now I have to change it... > > On linux there is no problem with that. Okay, the memory exceeds 1 GB > while > compiling my boost.msm based library. But it works fine! > > The problem what remains is to compile the stuff for windows. > > I have already just test one thing: Cross-compilation of my boost.Msm > state > machine on linux for windows with mingw32msvc-g++. But already doing this > produced some errors: > > *../src/TransportLayer/Statemachine/Master/CStateMasterHandshaking.hpp:33: > error: class ‘CStateMasterHandshaking_’ does not have any field named > ‘BaseStateMachineFrontEnd’ > ../src/TransportLayer/Statemachine/Master/CStateMasterHandshaking.hpp:33: > error: no matching function for call to > ‘BaseStateMachineFrontEnd<CStateMasterHandshaking_>::BaseStateMachineFrontEnd()’ > ../src/TransportLayer/Statemachine/Master/../Common/BaseStateMachineFrontEnd.hpp:48: > note: candidates are: > BaseStateMachineFrontEnd<TYPE>::BaseStateMachineFrontEnd(EventQueue&) > [with > TYPE = CStateMasterHandshaking_] > ../src/TransportLayer/Statemachine/Master/../Common/BaseStateMachineFrontEnd.hpp:26: > note: > BaseStateMachineFrontEnd<CStateMasterHandshaking_>::BaseStateMachineFrontEnd(const > BaseStateMachineFrontEnd<CStateMasterHandshaking_>&)* > > I think, the MSVC-specific cross compiler is responsible for this error. > > I don't now, how to continue with this problem. At the worst I have to > change the state machine completely..... > > Thanks so far, > > Rafael Hi, not sure how to help you there without code, but from what I see, I'd say that BaseStateMachineFrontEnd has a ctor which hides the default-ctor. Try to provide one and see if that helps. I don't think you have to change it completely. Probably replacing a bunch of events by a single one containing an id as attribute, then checking it in a guard to see what event you really posted would probably be enough. Cheers, Christophe _____________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] [parallel graph] error building parallel BGL
by The Maschine 27 Feb '13

27 Feb '13

Yes I have that. What I did is first build the full build and then try to build the example with the line you gave me. I did something like this: ➜ boost-trunk ./b2 threading=multi Performing configuration checks - 32-bit : no - 64-bit : yes - arm : no - mips1 : no - power : no - sparc : no - x86 : yes error: No best alternative for libs/coroutine/build/allocator_sources next alternative: required properties: <link>static <target-os>windows <threading>multi not matched next alternative: required properties: <link>static <segmented-stacks>on <threading>multi not matched next alternative: required properties: <link>static <threading>multi not matched - has_icu builds : no - gcc visibility : yes - long double support : yes Building the Boost C++ Libraries. error: No best alternative for libs/coroutine/build/allocator_sources next alternative: required properties: <link>static <target-os>windows <threading>multi not matched next alternative: required properties: <link>static <segmented-stacks>on <threading>multi not matched next alternative: required properties: <link>static <threading>multi not matched - iconv (libc) : no - iconv (separate) : yes - icu : no - icu (lib64) : no Component configuration: - atomic : building - chrono : building - context : building - coroutine : building - date_time : building - exception : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - system : building - test : building - thread : building - timer : building - wave : building ^C ➜ boost-trunk

2 1

Re: [Boost-users] [parallel graph] error building parallel BGL
by The Maschine 27 Feb '13

27 Feb '13

To be honest I thought that boost.build will include the link to MPI automatically. Isn't this suposed to include mpi?> ./b2 libs/graph_parallel/example Ill try to test it by hand. ThanksTasos

2 1

Unable to build 1.53.0 Ubuntu Linux 10.04
by Michael Powell 27 Feb '13

27 Feb '13

Hello, I am running GCC 4.4.3 (default?) distributed with Ubuntu Linux 10.04 LTS. I would like to build the latest Boost to keep up with the language and library standards, because we'll need those on a project we're working on (obviously), but it seems that we'll need to upgrade the GCC tool chain in order to do this: plus it us necessary even helpful to have access to lambda functors, expressions, etc, access Boost Phoenix (for Spirit2), and so on. I've read how it's possible to upgrade the GCC tool chain, but it worries me for obvious reasons. Also, building is one thing, the front end tool chain. We'll be cross compiling to ArchLinux running on ARM. I've done some reading about this issue and it seems that this is more of a back end concern. In other words, as long as the thing builds, compiles and links with whatever tool chain, language standard, compiler, etc, the cross compile should go well. Specifically, I believe we're going with CodeBench, but if there are other cross compilers available, that would be helpful to know as well. Any wisdom approaching an issue like this? Regards, Michael

2 2

[MSM] Unable to retrieve correct value of attribute of a state from within actions. (Possible Bug?)
by Deniz Bahadir 27 Feb '13

27 Feb '13

Hi everyone, Hi Christophe, Using Boost.MSM with eUML I tried to access the attribute of a state from within an action. However, the value is not what I expected when accessing the attribute of the state given as argument to the action. (It seems to be the default-parameter.) If I access the state directly (by name) and retrieve the value from it, it is set correctly as expected. Could it be that an action gets its arguments as copies? If so, I guess, the attributes of the copied arguments should be copied, too. This is the case for events. The attributes of an event given to the action seems to be set correctly. But the attributes of a state seem to be default-initialized. For clarification a simple example (this time tested and successfully compiled): #include <iostream> #define BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS #include <boost/msm/back/state_machine.hpp> #include <boost/msm/front/euml/euml.hpp> using namespace boost::msm::front::euml; namespace msm = boost::msm; namespace mpl = boost::mpl; using namespace std; namespace { // The attribute: BOOST_MSM_EUML_DECLARE_ATTRIBUTE(int, Number) BOOST_MSM_EUML_ATTRIBUTES((attributes_ << Number), NumberAttr) // An event containing the attribute: BOOST_MSM_EUML_EVENT_WITH_ATTRIBUTES(event1, NumberAttr) // Two states with attributes: BOOST_MSM_EUML_STATE((no_action, no_action, attributes_ << Number), state1) BOOST_MSM_EUML_STATE((no_action, no_action, attributes_ << Number), state2) // Entry-action which initializes the attributes: BOOST_MSM_EUML_ACTION(init_events_and_states) { template <class Evt, class Fsm, class State> void operator()(Evt const&, Fsm&, State&) { event1.get_attribute(Number) = 100; state1.get_attribute(Number) = 1; state2.get_attribute(Number) = 2; }; }; // Action that prints the Number-attributes of event and state. // NOTE: The state-Numbers differ! BOOST_MSM_EUML_ACTION(printNumber) { template <class Fsm, class Evt, class SourceState, class TargetState> void operator()(Evt const& evt, Fsm&, SourceState& source, TargetState& target) { std::cout << "In action \"printNumber\"." << "\n event1.Number == " << event1.get_attribute(Number) << "\n evt.Number == " << evt.get_attribute(Number) << "\n state1.Number == " << state1.get_attribute(Number) << "\n source.Number == " << source.get_attribute(Number) << "\n state2.Number == " << state2.get_attribute(Number) << "\n target.Number == " << target.get_attribute(Number) << std::endl; }; }; // The transition table: BOOST_MSM_EUML_TRANSITION_TABLE(( state1 + event1 / printNumber == state2 ), stt) // The FSM front-end and back-end: BOOST_MSM_EUML_DECLARE_STATE_MACHINE(( stt, init_ << state1, init_events_and_states ), FsmFrontend); typedef msm::back::state_machine<FsmFrontend> Fsm; void test() { Fsm fsm; // needed to start the highest-level FSM. // This initializes all attributes. fsm.start(); // emit event1 fsm.process_event(event1); } } // namespace int main() { test(); return 0; } // This prints the following (except "//") on the cmdline : // In action "printNumber". // event1.Number == 100 // evt.Number == 100 // state1.Number == 1 // source.Number == 0 // state2.Number == 2 // target.Number == 0 As you can see, the attribute-values of "event1" and "evt" are the same. However, the attribute-values of "state1" and "source" differ although they should be the same, too. (The same applies to "state2" and "target".) I tried this example with a custom type as attribute-type which prints each constructor-call and assignment-call and I realized, the copy-constructor was never called. If you want to try it yourself, just replace the declaration of the attribute in the above example with the following code: class MyInt { int val_; public: MyInt() : val_(50) { std::cout << "MyInt()" << std::endl; } MyInt(const MyInt& obj) : val_(obj.val_) { std::cout << "MyInt(const MyInt&) - val_=" << val_ << std::endl; } MyInt(const int& i) : val_(i) { std::cout << "MyInt(const int&) - val_=" << val_ << std::endl; } MyInt& operator=(const MyInt& obj) { val_ = obj.val_; std::cout << "op=(const MyInt&) - val_=" << val_ << std::endl; return *this; } MyInt& operator=(const int& i) { val_ = i; std::cout << "op=(const int&) - val_=" << val_ << std::endl; return *this; } }; // The attribute: BOOST_MSM_EUML_DECLARE_ATTRIBUTE(MyInt, Number) This looks like a bug, but I am not sure. Maybe I have to write my transition-table differently? Ciao, Deniz PS: I am using Boost 1.53.0 with GCC 4.7.2 (and C++11 support activated, most of the time.)

2 4

Please help make this boost::bind example compile
by Chris Stankevitz 27 Feb '13

27 Feb '13

Hello, In the code below, the last function, "GetFunctionThatReturnsRefX_2", does not compile. It is attempting to use boost::bind to produce a boost::function that takes a pointer to an object and returns one of the object's member variables by reference. If it is possible, would you modify it so that it does compile? Note 1: No problem when returning a copy as in "GetFunctionThatReturnsCopyX_2" Note 2: I employ a workaround in "GetFunctionThatReturnsRefX_1" that uses a helper "facade" function. I'm hoping to avoid this. Similarly I'm hoping to not have to add member function TCObject::GetX. Invoked with "g++ -c test.cpp" using gcc 4.6.3. Thank you, Chris #include <boost/bind.hpp> #include <boost/function.hpp> //------------------------------------ //------------------------------------ struct TCObject { int x; }; //------------------------------------ //------------------------------------ int GetCopyX(TCObject* pClass) { return pClass->x; } //------------------------------------ //------------------------------------ boost::function<int(TCObject*)> GetFunctionThatReturnsCopyX_1() { return boost::bind(GetCopyX, _1); } //------------------------------------ //------------------------------------ boost::function<int(TCObject*)> GetFunctionThatReturnsCopyX_2() { return boost::bind(&TCObject::x, _1); } //------------------------------------ //------------------------------------ int& GetRefX(TCObject* pClass) { return pClass->x; } //------------------------------------ //------------------------------------ boost::function<int&(TCObject*)> GetFunctionThatReturnsRefX_1() { return boost::bind(GetRefX, _1); } //------------------------------------ //------------------------------------ boost::function<int&(TCObject*)> GetFunctionThatReturnsRefX_2() { //return boost::ref(boost::bind(&TCObject::x, _1)); return boost::bind(&TCObject::x, _1); }

1 1

Can boost help me organize/parse lots of binary data?
by Chris Stankevitz 27 Feb '13

27 Feb '13

I am receiving a "live" stream of binary data that represents the states of various objects. Sort of like this: Car Speed (m/s): float32 Temperature (deg): uint16 ... My real packets have hundreds of items in them. I will be decoding many of these "packets" and doing various things with them like printing their values to console, etc. My plan is just to make classes: class Car { public: void Decode(istream&); private: float speed; unsigned temperature ... }; But it will not be very extendable. Unfocused open-ended question: Does boost offer something that will help me with this? Thank you, Chris

6 16