Re: [CMake] test depending on code compilation

[Franck Houssen]

OK, so I guess there is no way to do that like with autotools... 

- Mail original -

> De: "Franck Houssen" 
> À: "CMake Mail List" 
> Envoyé: Mercredi 10 Janvier 2018 12:22:39
> Objet: Re: [CMake] test depending on code compilation

> I tried to reduce the example:

> >> ls
> CMakeLists.txt main.cpp mytest.cpp mytest.sh

> >> more *
> ::
> CMakeLists.txt
> ::
> cmake_minimum_required(VERSION 3.7)
> enable_language(CXX)

> project(main)
> add_executable(main main.cpp)
> add_executable(mytestcpp mytest.cpp)

> include(CTest)
> enable_testing()
> configure_file("${CMAKE_CURRENT_SOURCE_DIR}/mytest.sh"
> "${CMAKE_CURRENT_BINARY_DIR}/mytest.sh")
> add_test(NAME mytestsh COMMAND ./mytest.sh WORKING_DIRECTORY
> "${CMAKE_CURRENT_BINARY_DIR}")

> add_custom_target(check COMMAND ${CMAKE_CTEST_COMMAND} DEPENDS mytestcpp)
> ::
> main.cpp
> ::
> int main() {return 0;}
> ::
> mytest.cpp
> ::
> int main() {return 0;}
> ::
> mytest.sh
> ::
> #!/bin/bash
> exit 0

> I want make to build only main => KO
> >> make
> [ 50%] Built target main
> [100%] Built target mytestcpp

> I want make check to build mytestcpp and run tests => OK but verbose is KO.
> >> make check ARGS="-V"
> [100%] Built target mytestcpp
> Test project /tmp/BUILD
> Start 1: mytestsh
> 1/1 Test #1: mytestsh . Passed 0.00 sec

> I want make test to run test only => OK and verbose is OK.

> - Mail original -

> > De: "Franck Houssen" 
> 
> > À: "CMake Mail List" 
> 
> > Envoyé: Mercredi 10 Janvier 2018 10:47:34
> 
> > Objet: [CMake] test depending on code compilation
> 

> > I need to design a test (= a bash script) such that :
> 
> > 1) run a dedicated executable for the test (to be compiled)
> 
> > 2) diff the run output with a reference log file
> 

> > The test is created with : add_test(mytest ./mytest.sh). The bash script
> > would look like:
> 
> > >> more mytest.sh
> 
> > /path/to/mytestexe > out.log
> 
> > diff out.log out.ref
> 

> > The dedicated executable for the test is created with :
> > add_executable(mytestexe mytestexe.cpp)
> 

> > Ideally, I would like mytestexe to be compiled when I type "make test"
> > (before to run the test) but not "make".
> 

> > Seems impossible to add a dependencie with : add_dependencies(mytest
> > mytestexe). I googled this and found
> > https://stackoverflow.com/questions/733475/cmake-ctest-make-test-doesnt-build-tests
> > but this was not really clear to me...I added : add_custom_target(check
> > COMMAND ${CMAKE_CTEST_COMMAND} DEPENDS mytestexe).
> 

> > The 2 unexpected problems I have left are:
> 
> > 1) mytestexe is compiled everytime I type "make" which is a solution but is
> > not really what I am looking for (also compiled when I type "make check"
> > which is expected).
> 
> > => is there a way for make not to compile mytestexe (note I didn't added
> > ALL
> > in add_custom_target so I am not sure to know why make builds mytestexe)
> 
> > 2) Also the verbosity is broken with check : make test ARGS="-V" is verbose
> > ,
> > but, make check ARGS="-V" is not.
> 
> > => how to deal with that ?
> 

> > --
> 

> > Powered by www.kitware.com
> 

> > Please keep messages on-topic and check the CMake FAQ at:
> > http://www.cmake.org/Wiki/CMake_FAQ
> 

> > Kitware offers various services to support the CMake community. For more
> > information on each offering, please visit:
> 

> > CMake Support: http://cmake.org/cmake/help/support.html
> 
> > CMake Consulting: http://cmake.org/cmake/help/consulting.html
> 
> > CMake Training Courses: http://cmake.org/cmake/help/training.html
> 

> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> 

> > Follow this link to subscribe/unsubscribe:
> 
> > https://cmake.org/mailman/listinfo/cmake
> 

> --

> Powered by www.kitware.com

> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ

> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:

> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html

> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html

> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://

[CMake] Creating a relocatable ProjectConfig.cmake when build uses absolute paths

[Lucas Soltic]

Hello,

I'm trying to create a relocatable package configuration file but I'm having a 
hard time with absolute paths that are used during the build.
Note that I use CMake 3.10.0.

First of all for the include path I'm using this:
target_include_directories(MyStaticTarget PUBLIC
   $
   $)

This does work but according to the doc it should not : 
https://cmake.org/cmake/help/latest/manual/cmake-generator-expressions.7.html?highlight=build_interface#output-expressions
 

The doc of BUILD_INTERFACE says: "Content of ... when the property is exported 
using export(), or when the target is used by another target in the same 
buildsystem. Expands to the empty string otherwise."
So according to the doc, when compiling the target MyTarget, the include dir I 
gave should not be used. Which seems consistent with the other uses of 
INTERFACE wording in CMake language. But it actually behaves like PUBLIC rather 
than INTERFACE. This is fine to me but inconsistent… :)
When exporting the target, the include dir uses what's given in for 
INSTALL_INTERFACE so it works fine. No problem on that part.


The second point is about libraries to link when using my project. My project 
exports a static library that depends on other libraries. These libraries are 
found (when generating my project through cmake) through calls like 
find_package(OpenGL). This provides a variable that contains an absolute 
non-relocatable path.

I've tried doing things like this:
target_link_libraries(MyStaticTarget PRIVATE
  $
  $)

According to https://cmake.org/pipermail/cmake/2016-May/063400.html 
, for static libraries, 
PRIVATE link dependencies become "PUBLIC", which is ok. And I could see that 
the link flag for this "private" dependency got exported in the generated 
config. But the problem is that whatever I put for INSTALL_INTERFACE, it is 
ignored and not written to the generated cmake config file. The generated CMake 
config file just takes into account what I put for BUILD_INTERFACE. Contrary to 
what happened with include directories. And I don't want to use only 
${OpenGL_relocatable_link_flag} because MyStaticTarget can be configured to be 
a dynamic library, in which case the library is really used during link and 
really want to link against the exact library that's referenced.

How can I have ${OpenGL_relocatable_link_flag} be used in the generated cmake 
config file?
Any other solution that would make the generated config relocatable is also 
fine.

Best regards,
Lucas -- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[CMake] Is a there a mean to check that all target are installed?

[Eric Noulard]

Is there a way to programmatically check whether
all (or some) CMake targets are installed?

I want to be able to check that all defined targets of a particular project
(at least libraries or executable) are installed.

I can recursively retrieve all targets using
https://cmake.org/cmake/help/v3.9/prop_dir/BUILDSYSTEM_TARGETS.html
directory property.

But then I want to know if a target has been installed or not by some
install(...) rules.

Is it possible?

-- 
Eric
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake support for MYS2

[Mojca Miklavec]

On 10 January 2018 at 11:56, Konstantin Tokarev  wrote:
> 10.01.2018, 11:40, "Mojca Miklavec" :
>> On 8 January 2018 at 17:38, Konstantin Tokarev wrote:
>>>  08.01.2018, 14:35, "Mojca Miklavec":
  Dear CMake developers,

  I installed msys2 from http://www.msys2.org/ and (after updating etc)
  installed cmake via
  pacman -S cmake
>>>
>>>  You should install mingw-w64-x86_64-cmake (or i686).
>>
>> Thank you very much. That package is missing ccmake though
>
> Please report it as a bug. cmake package should provide ccmake, or
> there should be a separate package if ncurses dependency is undesirable
> in the main package.

I can create a bug report, but I would like to clarify with CMake
developers first before I know what exactly to report in the first
place.

I'm pretty sure that this is a side-effect of CMake's own build
figuring out that it's being built on and for Windows, so it probably
skips building ccmake and builds cmake-gui.exe instead.

This all makes perfect sense for distributing the standalone
executable on Windows, but it's less suitable in the context of MSYS2.

>>, so I can
>> only run cmake directly and even then it strangely(?) defaults to
>> Visual Studio when I would expect it to go for Unix Makefiles.
>
> This is behavior of vanilla cmake, so it's reasonable that it is not altered.

I assume it belongs "to the same category" as the lack of ccmake.

I can imagine that it would make sense to offer to ways of building
cmake on Windows: the "standalone" mode without ccmake, with cmake-gui
and defaulting to Visual Studio. And the "command-line" mode with
ccmake and defaulting to "Unix Makefiles". Of course one could build
both ccmake and cmake-gui at the same time if desired.

We often have this problem with a Mac package manager. Many software
builds do "if this is mac, then standard unix tools don't exist, so do
something completely different" and they would create the app bundle,
but skip the rest of command-line friendliness and completely ignore
the fact that those unix tools may exist after all.

> You can use msys2 like a generic Windows software repository, not only
> for MinGW- or MSYS-based development.

I admit that I don't totally understand how exactly it's supposed to
work, but further discussion would be too off-topic for this list, I
assume.

>> (The "ccmake" from /usr/bin/ccmake is not helping in any way either, I
>> was hoping it would perhaps use mingw-w64-x86_64-cmake.)
>>
>> I later noticed that there is /mingw64/bin/cmake-gui.exe, but that one
>> doesn't really work either:
>>
>> $ cmake-gui
>> C:/msys/msys64/mingw64/bin/cmake-gui.exe: error while loading shared
>> libraries: librhash.dll: cannot open shared object file: No such file
>> or directory
>>
>>>  You've installed
>>>  package that targets MSYS environment, not native Windows.
>>
>> I still assume that others might run into exactly the same isuse in
>> the future. Since it's explicitly suggesting to write to the mailing
>> list, the reports might repeat.
>
> This is a packaging problem, so it should be reported to msys2
> maintainers first.

OK.

> in the meanwhile, you can edit CMakeCache.txt file directly, gui tools
> don't really add much :)

Well, I can always use
cmake -G "..." -Dwhatever ../source
but ccmake is useful to show what configuration options the program is
offering. Editing CMakeCache is a feasible workaround, but I would
like to have a proper fix at the end.

Thanks a lot for all the useful insights.

Mojca
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] test depending on code compilation

[Franck Houssen]

I tried to reduce the example: 

>> ls 
CMakeLists.txt main.cpp mytest.cpp mytest.sh 

>> more * 
:: 
CMakeLists.txt 
:: 
cmake_minimum_required(VERSION 3.7) 
enable_language(CXX) 

project(main) 
add_executable(main main.cpp) 
add_executable(mytestcpp mytest.cpp) 

include(CTest) 
enable_testing() 
configure_file("${CMAKE_CURRENT_SOURCE_DIR}/mytest.sh" 
"${CMAKE_CURRENT_BINARY_DIR}/mytest.sh") 
add_test(NAME mytestsh COMMAND ./mytest.sh WORKING_DIRECTORY 
"${CMAKE_CURRENT_BINARY_DIR}") 

add_custom_target(check COMMAND ${CMAKE_CTEST_COMMAND} DEPENDS mytestcpp) 
:: 
main.cpp 
:: 
int main() {return 0;} 
:: 
mytest.cpp 
:: 
int main() {return 0;} 
:: 
mytest.sh 
:: 
#!/bin/bash 
exit 0 

I want make to build only main => KO 
>> make 
[ 50%] Built target main 
[100%] Built target mytestcpp 

I want make check to build mytestcpp and run tests => OK but verbose is KO. 
>> make check ARGS="-V" 
[100%] Built target mytestcpp 
Test project /tmp/BUILD 
Start 1: mytestsh 
1/1 Test #1: mytestsh . Passed 0.00 sec 

I want make test to run test only => OK and verbose is OK. 

- Mail original -

> De: "Franck Houssen" 
> À: "CMake Mail List" 
> Envoyé: Mercredi 10 Janvier 2018 10:47:34
> Objet: [CMake] test depending on code compilation

> I need to design a test (= a bash script) such that :
> 1) run a dedicated executable for the test (to be compiled)
> 2) diff the run output with a reference log file

> The test is created with : add_test(mytest ./mytest.sh). The bash script
> would look like:
> >> more mytest.sh
> /path/to/mytestexe > out.log
> diff out.log out.ref

> The dedicated executable for the test is created with :
> add_executable(mytestexe mytestexe.cpp)

> Ideally, I would like mytestexe to be compiled when I type "make test"
> (before to run the test) but not "make".

> Seems impossible to add a dependencie with : add_dependencies(mytest
> mytestexe). I googled this and found
> https://stackoverflow.com/questions/733475/cmake-ctest-make-test-doesnt-build-tests
> but this was not really clear to me...I added : add_custom_target(check
> COMMAND ${CMAKE_CTEST_COMMAND} DEPENDS mytestexe).

> The 2 unexpected problems I have left are:
> 1) mytestexe is compiled everytime I type "make" which is a solution but is
> not really what I am looking for (also compiled when I type "make check"
> which is expected).
> => is there a way for make not to compile mytestexe (note I didn't added ALL
> in add_custom_target so I am not sure to know why make builds mytestexe)
> 2) Also the verbosity is broken with check : make test ARGS="-V" is verbose ,
> but, make check ARGS="-V" is not.
> => how to deal with that ?

> --

> Powered by www.kitware.com

> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ

> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:

> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html

> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html

> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake support for MYS2

[Konstantin Tokarev]

10.01.2018, 11:40, "Mojca Miklavec" :
> On 8 January 2018 at 17:38, Konstantin Tokarev wrote:
>>  08.01.2018, 14:35, "Mojca Miklavec":
>>>  Dear CMake developers,
>>>
>>>  I installed msys2 from http://www.msys2.org/ and (after updating etc)
>>>  installed cmake via
>>>  pacman -S cmake
>>
>>  You should install mingw-w64-x86_64-cmake (or i686).
>
> Thank you very much. That package is missing ccmake though

Please report it as a bug. cmake package should provide ccmake, or
there should be a separate package if ncurses dependency is undesirable
in the main package.

>, so I can
> only run cmake directly and even then it strangely(?) defaults to
> Visual Studio when I would expect it to go for Unix Makefiles.

This is behavior of vanilla cmake, so it's reasonable that it is not altered.
You can use msys2 like a generic Windows software repository, not only
for MinGW- or MSYS-based development.

> (The "ccmake" from /usr/bin/ccmake is not helping in any way either, I
> was hoping it would perhaps use mingw-w64-x86_64-cmake.)
>
> I later noticed that there is /mingw64/bin/cmake-gui.exe, but that one
> doesn't really work either:
>
> $ cmake-gui
> C:/msys/msys64/mingw64/bin/cmake-gui.exe: error while loading shared
> libraries: librhash.dll: cannot open shared object file: No such file
> or directory
>
>>  You've installed
>>  package that targets MSYS environment, not native Windows.
>
> I still assume that others might run into exactly the same isuse in
> the future. Since it's explicitly suggesting to write to the mailing
> list, the reports might repeat.

This is a packaging problem, so it should be reported to msys2
maintainers first.

in the meanwhile, you can edit CMakeCache.txt file directly, gui tools
don't really add much :)

> (OK, I don't expect so many people to use the strange unix toolchains
> on windows platforms, but still.)
>
> Thank you,
> Mojca
>
>>>  as well as some other packages like "make", the gcc compiler etc.
>>>
>>>  But "ccmake" complains:
>>>
>>>   System is unknown to cmake, create:
>>>   Platform/MINGW32_NT-6.1 to use this system, please send your config file 
>>> to
>>>   cm...@www.cmake.org so it can be added to cmake
>>>
>>>   Your CMakeCache.txt file was copied to CopyOfCMakeCache.txt. Please
>>>  send that file to
>>>   cm...@www.cmake.org.
>>>
>>>  I believe I should additional set the compiler somehow, but I guess I
>>>  should be able to cope with that part. I just wanted to report the
>>>  failure to identify the platform while fighting with other problems.
>>>  (Meson works correctly out of the box.)
>>>
>>>  CopyOfCMakeCache is in attachment.
>>>
>>>  Thank you very much,
>>>  Mojca
>>
>>  --
>>  Regards,
>>  Konstantin

-- 
Regards,
Konstantin
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[CMake] test depending on code compilation

[Franck Houssen]

I need to design a test (= a bash script) such that : 
1) run a dedicated executable for the test (to be compiled) 
2) diff the run output with a reference log file 

The test is created with : add_test(mytest ./mytest.sh). The bash script would 
look like: 
>> more mytest.sh 
/path/to/mytestexe > out.log 
diff out.log out.ref 

The dedicated executable for the test is created with : 
add_executable(mytestexe mytestexe.cpp) 

Ideally, I would like mytestexe to be compiled when I type "make test" (before 
to run the test) but not "make". 

Seems impossible to add a dependencie with : add_dependencies(mytest 
mytestexe). I googled this and found 
https://stackoverflow.com/questions/733475/cmake-ctest-make-test-doesnt-build-tests
 but this was not really clear to me...I added : add_custom_target(check 
COMMAND ${CMAKE_CTEST_COMMAND} DEPENDS mytestexe). 

The 2 unexpected problems I have left are: 
1) mytestexe is compiled everytime I type "make" which is a solution but is not 
really what I am looking for (also compiled when I type "make check" which is 
expected). 
=> is there a way for make not to compile mytestexe (note I didn't added ALL in 
add_custom_target so I am not sure to know why make builds mytestexe) 
2) Also the verbosity is broken with check : make test ARGS="-V" is verbose , 
but, make check ARGS="-V" is not. 
=> how to deal with that ? 
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] CMake support for MYS2

[Mojca Miklavec]

On 8 January 2018 at 17:38, Konstantin Tokarev wrote:
> 08.01.2018, 14:35, "Mojca Miklavec":
>> Dear CMake developers,
>>
>> I installed msys2 from http://www.msys2.org/ and (after updating etc)
>> installed cmake via
>> pacman -S cmake
>
> You should install mingw-w64-x86_64-cmake (or i686).

Thank you very much. That package is missing ccmake though, so I can
only run cmake directly and even then it strangely(?) defaults to
Visual Studio when I would expect it to go for Unix Makefiles.
(The "ccmake" from /usr/bin/ccmake is not helping in any way either, I
was hoping it would perhaps use mingw-w64-x86_64-cmake.)

I later noticed that there is /mingw64/bin/cmake-gui.exe, but that one
doesn't really work either:

$ cmake-gui
C:/msys/msys64/mingw64/bin/cmake-gui.exe: error while loading shared
libraries: librhash.dll: cannot open shared object file: No such file
or directory

> You've installed
> package that targets MSYS environment, not native Windows.

I still assume that others might run into exactly the same isuse in
the future. Since it's explicitly suggesting to write to the mailing
list, the reports might repeat.
(OK, I don't expect so many people to use the strange unix toolchains
on windows platforms, but still.)

Thank you,
Mojca

>> as well as some other packages like "make", the gcc compiler etc.
>>
>> But "ccmake" complains:
>>
>>  System is unknown to cmake, create:
>>  Platform/MINGW32_NT-6.1 to use this system, please send your config file to
>>  cm...@www.cmake.org so it can be added to cmake
>>
>>  Your CMakeCache.txt file was copied to CopyOfCMakeCache.txt. Please
>> send that file to
>>  cm...@www.cmake.org.
>>
>> I believe I should additional set the compiler somehow, but I guess I
>> should be able to cope with that part. I just wanted to report the
>> failure to identify the platform while fighting with other problems.
>> (Meson works correctly out of the box.)
>>
>> CopyOfCMakeCache is in attachment.
>>
>> Thank you very much,
>> Mojca
>
> --
> Regards,
> Konstantin
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake