15 Apr
2016
15 Apr
'16
8:44 p.m.
Paul wrote:
This would be unfortunate, as it would make it a pain to use a lot of tools(cmake, travis, appveyor, etc) with boost libraries just because of an arbitrary rule 15 years ago.
Right. It would be better if the Boost guidelines were less restrictive. The approach I would prefer is: Instead of restricting the contents of the library repository root directory, restrict the contents of the '.boost' (or 'boost', or 'meta') directory. There should be sufficient specification in there to inform the Boost build and release process about the library. Glen -- View this message in context: http://boost.2283326.n4.nabble.com/CMake-what-to-do-now-tp4685286p4685403.ht... Sent from the Boost - Dev mailing list archive at Nabble.com.