-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use protobufs instead of Boost serialization. #54
Comments
JeffAbrahamson
added a commit
that referenced
this issue
May 2, 2015
Also test without old Boost serialization support. Maintain temporary support for reading Boost serialization format. Provide temporary --convert flag. Provide temporary access for forced rewrite of database. Use clang instead of g++. Clean up makefile: don't build unused libraries. Part of #54.
JeffAbrahamson
added a commit
that referenced
this issue
May 2, 2015
Also move README to README.md to permit some formatting. Part of #54.
JeffAbrahamson
added a commit
that referenced
this issue
May 2, 2015
JeffAbrahamson
added a commit
that referenced
this issue
May 3, 2015
Remove also support for converting from Boost to protobuf format. Remove URL import/export until it actually works. That development should have been on a branch, my bad. Replace golden archive and it's results for binary archive test. Part of #54.
JeffAbrahamson
added a commit
that referenced
this issue
May 3, 2015
Note that we need protobufs but not Boost serialization. Part of #54.
JeffAbrahamson
added a commit
that referenced
this issue
May 3, 2015
Fix dependency order so that protobufs are compiled before files that need them. Part of #54.
JeffAbrahamson
added a commit
that referenced
this issue
May 4, 2015
Fix initialization order bug in root.cpp. This closes #54.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
boost/serialization has a history of changing their file format without adequate and user-controlled forwards compatibility. That is, files written by new versions of the library are not always readable by older versions. This means a newer version of srd may write something that an older version (say, on another host) can not read.
The text was updated successfully, but these errors were encountered: