Oh apologies, the linking error was isolated and fixed. You hinted at the issue - I had managed to forget to add the component registration macros into a *.cpp file for the data structure.
V/r, ct On Wed, Apr 19, 2017 at 12:21 PM, Hartmut Kaiser <[email protected]> wrote: > Chris, > > > Thanks for the quick response Hartmut, the contents of accumulator.cpp > > clarified everything! > > Well, the accumulator example does not expose those linker errors, so > there is something you did differently... It's really difficult to tell > from here without being able to look at the code. All I can say is that the > missing symbols are generated by those macros you have to add for each of > the actions and for your component. > > Regards Hartmut > --------------- > http://boost-spirit.com > http://stellar.cct.lsu.edu > > > > > > On Wed, Apr 19, 2017 at 11:21 AM, Hartmut Kaiser > > <[email protected]> wrote: > > > > > i'm in the process of implementing a user-defined type called "teststo" > > > which will reside in an hpx::partitioned_vector and am having a couple > > of > > > linker issues. > > > the implementation is based on the accumulator example from hpx 0.99. > > the > > > hpxcxx tool is being used to compile a component (the user-defined type > > > stored in the hpx::partitioned_vector) and an executable. > > > the component (defining the user-defined type) has a "clean" compile - > > no > > > issues. when the executable which instantiates the partitioned vector > > > compiles there is a set of linker errors. > > > 1 error that reads : undefined reference to > > > "hpx::traits::component_type_database<test::server::teststo, > > void>::get()" > > > and 3 errors that read: undefined reference to `char const* > > > > > hpx::actions::detail::get_action_name<test::server:: > teststo::update_action > > > >()" > > > the hpxcxx compile tool is given -lhpx_iostreams - > > lhpx_partitioned_vector > > > and -lteststo > > > for clarity teststo is a struct and has 1 method called "update" which > > > accepts a uint64_t. > > > > Chris, looks like that you're missing one of the macros needed for using > > your own actions. Can you show me the code? Or reduce it to a minimal > > reproducing test case, perhaps? > > > > Regards Hartmut > > --------------- > > http://boost-spirit.com > > http://stellar.cct.lsu.edu > > > > > > > > _______________________________________________ > > hpx-users mailing list > > [email protected] > > https://mail.cct.lsu.edu/mailman/listinfo/hpx-users > > >
_______________________________________________ hpx-users mailing list [email protected] https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
