Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Executation error encountered when activating SOLAR_USE_TEXT_SERIALIZATION #66

Open
yzhou-bcom opened this issue Jul 19, 2023 · 0 comments

Comments

@yzhou-bcom
Copy link
Contributor

Solar uses boost serialization. By default, boost binary archive is used. However, it is not portable between linux/windows. I wanted to obtain a map which is portable between linux/windows, i.e. the same map file can be loaded from both linux (ubuntu) and windows 10.

So, I uncommented this line https://github.com/SolarFramework/SolARFramework/blob/develop/interfaces/core/SerializationDefinitions.h#L43 in order to switch to text serialization (portable cross platform). Then, I rebuilt solarframework, grpcremote, all the pipelines and the services.

When I launched the mapping, I got an error message "./SolARServiceTest_MappingAndRelocFrontend: symbol lookup error: /home/xxxx/.remaken/packages/linux-gcc/SolARBuild/SolARFrameworkGRPCRemote/1.0.0/lib/x86_64/shared/release/libSolARFrameworkGRPCRemote.so: undefined symbol: _ZNK5SolAR13datastructure5Image4saveIN5boost7archive15binary_oarchiveEEEvRT_j
"
libSolARFrameworkGRPCRemote should not depend on boost binary archive any more.
It seems to be related to https://github.com/SolarFramework/SolARFramework/blob/develop/interfaces/datastructure/Image.h#L308 where the macro DECLARESERIALIZE only declares serialize() method. However in Image.h save()/load() is used instead of serialize() https://github.com/SolarFramework/SolARFramework/blob/develop/interfaces/core/SerializationDefinitions.h#L66
to be further investigated...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant