[CMake] Reentrant-safe includes

2017-06-09 Thread Robert Dailey
So I have a series of common CMake scripts I use: pre-setup.cmake post-setup.cmake I include pre-setup.cmake at the beginning of the root CMakeLists.txt and post-setup.cmake is included at the bottom. add_subdirectory() and other target stuff is done inbetween. One issue I run into is that these

Re: [CMake] CMake problem with intel parallel studio 2017

2017-06-09 Thread Mamales, Petros via CMake
Thank you very much! I saw it to be along these lines, by doing (quite) a few "greps" and reading the documentation. The last step is the one I was trying to pin down -;) All the best, Petros -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Friday, June 09, 2017 12

Re: [CMake] Forcing CMake to find static library

2017-06-09 Thread Michael Ellery
if you know exactly where the library is (via the ENV), then I guess you want to specify the NO_DEFAULT_PATH option to find_library. Alternatively, see if you can use the standard find module included with cmake: https://github.com/Kitware/CMake/blob/master/Modules/FindLAPACK.cmake ..and in tha

[CMake] Forcing CMake to find static library

2017-06-09 Thread Matthias Redies
Hello, I am trying to force CMAKE to include a specific static lapack library, set through the environment variable $LAPACK_LIB: > ls $LAPACK_LIB libblas_extra.a libcblas.a liblapack.a liblapacke.a libtmglib.a > echo $LAPACK_LIB /bgsys/local/lapack/3.7.0/lib This is how I am trying to do

Re: [CMake] CMake problem with intel parallel studio 2017

2017-06-09 Thread Brad King
On 06/09/2017 11:51 AM, Mamales, Petros wrote: > how is the specification of the toolset (from command line) translates > to the modules folder in CMake? The -T option specifies the CMAKE_GENERATOR_TOOLSET: https://cmake.org/cmake/help/v3.9/variable/CMAKE_GENERATOR_TOOLSET.html That value tel

Re: [CMake] CMake problem with intel parallel studio 2017

2017-06-09 Thread Mamales, Petros via CMake
Hi Brad, Thank you for the one-to-one answers! Much appreciated! I was afraid of 3) as a reasonable answer. Unfortunately intel PSXE installation process has some desirables as a process, and things do not always work as intended, hence I was hoping for a workaround. In case you would like to ob

Re: [CMake] CMake problem with intel parallel studio 2017

2017-06-09 Thread Brad King
On 06/08/2017 03:02 PM, Mamales, Petros via CMake wrote: > I try to create Visual Studio 2015 (VS2015) solutions with the > intel c++ compiler from Intel Parallel Studio XE (iPSXE) 2017. > a) How does the identification of the toolset proceed? (I used the –T > command line option) It works

Re: [CMake] Choosing Toolset v140 for Generator VS 15 2017 Win64

2017-06-09 Thread Mamales, Petros via CMake
Generator: Visual Studio 14 2015 Win64 Toolset:Intel C++ Compiler 17.0 -Original Message- From: Robert Maynard [mailto:robert.mayn...@kitware.com] Sent: Friday, June 09, 2017 10:26 AM To: Mamales, Petros [CCC-OT NE] Cc: Valmiki Rampersad; cmake@cmake.org Subject: Re: [CMake]

Re: [CMake] Choosing Toolset v140 for Generator VS 15 2017 Win64

2017-06-09 Thread Robert Maynard
So to clarify when using the intel compiler what is the exact generator and toolset you are specifying to CMake? On Fri, Jun 9, 2017 at 10:05 AM, Mamales, Petros wrote: > Hi Robert, > Thank you for your response. > However, this mail was superseded by another one - actually this being my > first

Re: [CMake] Choosing Toolset v140 for Generator VS 15 2017 Win64

2017-06-09 Thread Mamales, Petros via CMake
Hi Robert, Thank you for your response. However, this mail was superseded by another one - actually this being my first email to the mailing list I received notification that it would not get published as I was not yet a member. As it turns out, it does find the toolset (I am very curious as to h

Re: [CMake] Choosing Toolset v140 for Generator VS 15 2017 Win64

2017-06-09 Thread Robert Maynard
Hi, Can you provide the contents of the build directory file CMakeFiles/CMakeError.log . That might help us figure out why the toolset is not found On Tue, May 30, 2017 at 10:44 PM, Valmiki Rampersad wrote: > I have Visual Studio 2017 Community, with toolsets v141 and v140, installed. > > > If I

Re: [CMake] my first experiences

2017-06-09 Thread Andrew Bell
Sounds like you had a bad day. Hope you have a better one tomorrow. On Fri, Jun 9, 2017 at 2:40 AM, Xen wrote: > I just want to tell you what terrible software CMake is. > > The newest version won't compile on my system. The bootstrapping just > won't complete. > > It hangs on 100% CPU while tr

Re: [CMake] my first experiences

2017-06-09 Thread Bo Zhou
I always compile CMake on Linux but never meet any issues, please make sure you had installed a complete working Linux development environment, with g++, libstdc++-devel etc. The only special thing is just about enabling GUI with Qt, but that's so easy, just install the Qt development libraries t

Re: [CMake] my first experiences

2017-06-09 Thread Eric Noulard
Hi xen, Sorry to hear you lost so much time. Could you provide us with the version of your system and compiler? Did you try any source of precompiled version of CMake either from cmake.org or from your favorite system repo? If no why? Average CMake user don't ever compile CMake itself. Le 9 jui

Re: [CMake] my first experiences

2017-06-09 Thread Raymond Wan
Hi Xen, On Fri, Jun 9, 2017 at 3:40 PM, Xen wrote: > I just want to tell you what terrible software CMake is. > > The newest version won't compile on my system. The bootstrapping just won't > complete. Just out of curiosity but is there any reason why you need the "latest version"? I usually

[CMake] my first experiences

2017-06-09 Thread Xen
I just want to tell you what terrible software CMake is. The newest version won't compile on my system. The bootstrapping just won't complete. It hangs on 100% CPU while trying to link cmake. Maybe that is a deficit of this system. I take an older version but it needs ncurses. I have ncurse