Re: [CMake] Advice on converting legacy project to modern CMake

2017-08-10 Thread Robert Maynard
> Which leads to a question I have for the Kitware types here. What should I suggest to my Linux enterprise distribution users? Can they simply download and use the latest Linux binary version of CMake that is distributed by Kitware or are there library version incompatibilities that make that

Re: [CMake] Advice on converting legacy project to modern CMake

2017-08-07 Thread Alan W. Irwin
On 2017-08-07 11:35- Björn Blissing wrote: 1. Which version if CMake should I target? I.e. Which version should I require in my cmake_minimum_required() statement? I would suggest either cmake_minimum_required(VERSION 3.6.2 FATAL_ERROR) or cmake_minimum_required(VERSION 3.7.2

Re: [CMake] Advice on converting legacy project to modern CMake

2017-08-07 Thread Rolf Eike Beer
Am 2017-08-07 11:57, schrieb Björn Blissing: Hi Eike, 3. Some of my legacy projects have all source in the same directory, i.e. both source and header files are in the same directory. Others have both private and public headers in the same directory. How do I handle this with

Re: [CMake] Advice on converting legacy project to modern CMake

2017-08-07 Thread Rolf Eike Beer
Am 2017-08-07 11:35, schrieb Björn Blissing: Hi, I have some legacy projects which I intend to update to modern CMake. The documentation is good but do not really cover "best practices". So I have some questions which I hope some of you could help to answer: 1. Which version if CMake should I

[CMake] Advice on converting legacy project to modern CMake

2017-08-07 Thread Björn Blissing
Hi, I have some legacy projects which I intend to update to modern CMake. The documentation is good but do not really cover "best practices". So I have some questions which I hope some of you could help to answer: 1. Which version if CMake should I target? I.e. Which version should I require