Re: [CMake] CMake fixup_bundle for ubuntu 16.04

2017-12-12 Thread Miklos Espak
Hi, you need to add the directory where the Qt libs have been installed (along with your application binaries) to the LD_LIBRARY_PATH. In your case it is '/home/waldo/Developer/install/Release/bratumia/bin/', as I see. Also, you do *not* need to add the Qt plugin directories to the library path.

[CMake] Using CMake include does not seem to work intuatively

2017-12-12 Thread Saad Khattak
Hi, Let's say I have the following directory structure: ~/Repos/MyRepo/CMakeLists.txt ~/CMakeFiles/Foo.cmake ~/CMakeFiles/Bar.cmake In the CMakeLists.txt I have the following command: include(~/CMakeFiles/Foo.cmake) And in Foo.cmake I have the following command: include(Bar.cmake) Turns out t

Re: [CMake] FortranCInterface not working with 3.9.0 with Intel 2015

2017-12-12 Thread Brad King
On 12/11/2017 04:34 PM, John Cary wrote: > Bill Hoffman wrote: >> LINK: command "xilink ... /out:FortranCInterface.exe ..." failed (exit code >> 1169) >> LIBCMT.lib(winapisupp.obj) : error LNK2005: >> __crtSetUnhandledExceptionFilter already defined in MSVCRT.lib(MSVCR120.dll) >> >> Did you change

Re: [CMake] INTERFACE library and path to source.

2017-12-12 Thread Eric Noulard
I did file a bug report then: https://gitlab.kitware.com/cmake/cmake/issues/17556 2017-12-11 15:12 GMT+01:00 Oleksii Vilchanskyi < oleksii.vilchans...@gmail.com>: > > I'm not that sure that this is the "expected" behavior > > Yes, now it looks like a bug to me, too. Being written as it was in th