On 08/18/2016 09:30 PM, Christian Convey wrote: > Hi Karl, > > I'll need to let Yury answer your original question regarding the best > way to report CMake-related bugs. > > Regarding the errors you're getting... I just looked at CMake's > online documentation regarding your "target_compile_definitions" > error. > > From what I can tell, the "target_compile_definition" property was > introduced in CMake 2.8.11. It sounds like your version of CMake is > just a little too old.
Well - "too old" is a relative term - cmake 2.8.10 was released in only october 2012 and cmake 2.8.11 in may 2013 so it is not even 4 years old, the oldest currently supported (though for not much longer) postgresql release 9.1 was released in september 2011 and 9.2 was also released before october 2012. So while Cmake compat might only make it for v10, I dont think that we can depend on bleeding edge version like that for our buildtools... > > Regarding how one can know the required CMake version: My modus > operandi for CMake projects in general is (1) read the project's > how-to-build docs, and if that's not heplful, (2) hope that the > project's CMake files contain a "cmake_minimum_required" call to give > me a clear error message. I didn't find any such indication in Yuri's > files, although perhaps I missed it. > > > Yury: Would it make sense to add a call to "cmake_minimum_required" in > one or more of your CMakeLists.txt files? it would make sense nevertheless but I dont think that 2.8.11 is old enough - looking at the release information and the feature compatibily matrix it would seems we should more aim at something like 2.8.0 or 2.8.3... Stefan -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers