Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is a boost binary archive “portable” from one Linux x86_64 machine to another Linux x86_64 machine?
The documentation suggests it is, by using the term native binary, however, I have not yet been able to do it. Is it “my fault”, or is such a thing not possible?
I do know about portable binary archives, but I understand they are not tested well…
EDIT: In addition to SoapBox’s answer, I figured out the boost library version needs to be the same on both machines
If both machines are The same version of 64-bit Linux on an x86-64 CPU, then you don’t need any special “portability” code or options. The binary formats of these two machines are, by definition, identical. If one machine can load the archive then the other one also can.
This is not guaranteed but still usually true on different OSes as long as the underlying hardware is the same. (That is, 64-bit windows on x86-64 should be able to load an archive created on 64-bit Linux x86-64.)
If the processors are different, then you’ll need to use a “portable” archive format. Boost.Serialization’s text archives should be portable because the conversion to the non-portable binary representation is done from the text in the archive at load time.