17 Jun
2017
17 Jun
'17
4:58 p.m.
On 17/06/2017 17:51, Peter Dimov via Boost wrote:
Niall Douglas wrote:
So tl;dr; I strongly recommend placing all cmake complexity into runnable scripts which generate .cmake files to be include()d to avoid boilerplate, and keep the CMakeLists.txt etc completely free of any custom macros or functions.
Niall, could you please show how an idiomatic CMakeLists.txt file should, in your opinion, look like, for a run-of-the-mill Boost library? Pick some existing library to illustrate the point, such as for example System, or SmartPtr, or even the simplest one, Assert. Or any other, if you prefer.
+1 --- This email has been checked for viruses by AVG. http://www.avg.com