Re: [CMake] How to build fully correctly versioned shared object files with cmake

2018-08-06 Thread Hendrik Sattler
Am 6. August 2018 22:29:21 MESZ schrieb Alexander Neundorf : >On 2018 M08 6, Mon 21:54:33 CEST Hendrik Sattler wrote: >> Am 6. August 2018 20:27:23 MESZ schrieb Philip Van Hoof >: >> >Hello everyone, >> > >> >I noticed that it sometimes happens that I find a package for a >shared >> >object fil

Re: [CMake] Using Different Computers for cmake and ctest

2018-08-06 Thread Bo Zhou
Maybe you could improve the CTest system to allow execute remotely, by a shared file system to hold the all built binary files, and do a RPC-like test, and redirect the all output and terminate code from the target GPU machine, it should be able to work. On Wed, Jul 18, 2018 at 10:50 PM Brian S w

Re: [CMake] How to build fully correctly versioned shared object files with cmake

2018-08-06 Thread Philip Van Hoof
Alexander Neundorf wrote: > On Mon, 2018-08-06 at 21:54 +0200, Hendrik Sattler wrote: > > Is there ANY reason to use libtool library versioning? It might > > surprise people but it really is not any kind of standard. > >  > > Just change the SOVERSION when you make incompatible ABI changes > > a

Re: [CMake] How to build fully correctly versioned shared object files with cmake

2018-08-06 Thread Alexander Neundorf
On 2018 M08 6, Mon 21:54:33 CEST Hendrik Sattler wrote: > Am 6. August 2018 20:27:23 MESZ schrieb Philip Van Hoof : > >Hello everyone, > > > >I noticed that it sometimes happens that I find a package for a shared > >object file(s) (or DLLs, on platforms like Windows) that have a build > >set up us

Re: [CMake] How to build fully correctly versioned shared object files with cmake

2018-08-06 Thread Philip Van Hoof
On Mon, 2018-08-06 at 21:54 +0200, Hendrik Sattler wrote: Hello Hendrik, > > https://github.com/pvanhoof/dir-examples/tree/master/cmake-example > > > > The idea is that the examples are as correct as possible. That > > means the examples should simple and educational. Easing (some > > amount) of

Re: [CMake] Using Different Computers for cmake and ctest

2018-08-06 Thread Juan E. Sanchez
Hi, CTest should work. You would just need to set the paths to the executable you want to test. In my case, I have my tests in a different repository than my source code. Regards, Juan On 8/6/18 3:00 PM, Alexander Neundorf wrote: On 2018 M07 18, Wed 09:49:47 CEST Brian S wrote: I curren

Re: [CMake] simple find_package example

2018-08-06 Thread Alexander Neundorf
On 2018 M08 2, Thu 10:01:39 CEST Randy Heiland wrote: > Hi, > > I'd like to figure out how to modify the simple "hello" demo ( > https://cmake.org/examples/) so that the Hello project is a library with an > accompanying FindHello.cmake and then the Demo project uses that > information and "find_pa

Re: [CMake] Using Different Computers for cmake and ctest

2018-08-06 Thread Alexander Neundorf
On 2018 M07 18, Wed 09:49:47 CEST Brian S wrote: > I currently use cmake/ctest to build and test my software. The software is > C++/CUDA. During the build step I don't need a GPU but in the test step I > do. I would like to build the code with cmake on a cluster with many CPUs > and then run the te

Re: [CMake] How to build fully correctly versioned shared object files with cmake

2018-08-06 Thread Hendrik Sattler
Am 6. August 2018 20:27:23 MESZ schrieb Philip Van Hoof : >Hello everyone, > >I noticed that it sometimes happens that I find a package for a shared >object file(s) (or DLLs, on platforms like Windows) that have a build >set up using cmake, that doesn't set everything that should be set. > >Usua

Re: [CMake] Install interface

2018-08-06 Thread Robert Maynard
Installing interface libraries has no effect without the 'EXPORT' keyword as they have no artifacts, you will need to install the actual archives to get any artifacts. To generate a CMake file containing the correct import targets for consumers of your project you should like at the 'EXPORT' keywo

Re: [CMake] cmake fails on first run but succeeds when run again after make

2018-08-06 Thread Robert Maynard
The error sounds like the file needs to be marked as GENERATED ( https://cmake.org/cmake/help/latest/prop_sf/GENERATED.html ) but I would have thought qt5_add_resources would do that for you. You might look at using CMake built in rc support ( https://cmake.org/cmake/help/latest/prop_tgt/AUTORCC.h

[CMake] How to build fully correctly versioned shared object files with cmake

2018-08-06 Thread Philip Van Hoof
Hello everyone, I noticed that it sometimes happens that I find a package for a shared object file(s) (or DLLs, on platforms like Windows) that have a build set up using cmake, that doesn't set everything that should be set. Usually as packagers of various popular open source softwares correct en