Building release v1.5.8 with protolib v3.0b1 results in build errors about norm HOT 6 CLOSED

Protolib 3.0b1 is from August 2017. NORM 1.5.8 is from July 2018. We should probably create new releases of each. It's possible to upload additional downloads with each release (e.g. to include a version with Protolib like we did before), I just didn't know that was necessary in this case.

from norm.

Thanks for the tip on git submodule. That seems to be what is needed to manage protolib as part of NORM and other projects using it.

from norm.

Thanks for the comment. I suspect that Protolib release was created before or during the migration of our stuff to Github. At the moment, I recommend using the Protolib 'master' with the NORM 'master" (and same for other projects here that use Protolib). Our prior practice for packaging NORM source tree "releases" was to include the current Protolib tree tested with that NORM release as part of the NORM tarball. I will try to determine the best approach for this now that the code is being maintained on Github.

from norm.

Thanks. I will use the master for now.

Maybe adding protolib as a git submodule would suffice?

from norm.

In case it's useful, I just added the 1.5.8 source tarball that contains the corresponding (at the time) protolib from the original 'downloads.pf' site to the 1.5.8 release.

from norm.

That is useful. Thanks a lot.

from norm.