Re: [ANN] AEON 2nd gen cryptonote, anon, mobile-friendly, scalable, pruning
@smooth:
I used Boost 1.59 for the aeon-light test binaries. Should we expect trouble anytime we switch between binaries that were compiled on different Boost versions?
If that's the case, I'd appreciate some official direction as to what version to use, so that I'd always use the same as anyone that will produce official binaries, thus preventing similar complications in the future.
Thanks!
I used Boost 1.59 for the aeon-light test binaries. Should we expect trouble anytime we switch between binaries that were compiled on different Boost versions?
If that's the case, I'd appreciate some official direction as to what version to use, so that I'd always use the same as anyone that will produce official binaries, thus preventing similar complications in the future.
Thanks!
I'm not sure, as I was only vaguely aware of this issue, and the boost documentation is rather poor. Looking in the release notes, I see nothing about version incompatibility since 1.45, which is quite old (none of the AEON builds would have used something older than that right?):
http://www.boost.org/doc/libs/1_59_0/libs/serialization/doc/release.html
So I don't see a good reason for the "unsupported version" failure to occur at all. Maybe there is another explanation.
Still, let's get Arux to report on the boost version being used for the official Windows builds and people can try to use the same version for unofficial builds as well.