I'm not sure if that is the best fix. It's probably better for it to fail loudly and require people to pass -DBUILD_CRC32C=OFF
if that's what they want.
I don't know what your release process it like but you can also upload your own source tarballs to GitHub releases which might be a better solution? It's nice having them on GitHub as it makes it easier for generic updater bots to find new versions (I think conda-forge's bot is smart enough to also find it on http://xrootd.web.cern.ch/ but the point remains).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1