[CMake] CMAKE_C++_CREATE_SHARED_LIBRARY missing

2016-07-09 Thread Dvir Yitzchaki
Hi. I use cmake 3.3.1 on Red-Hat 5 and 6. When I generate a project I get the following error: CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_C++_CREATE_SHARED_LIBRARY However, after the error the generation succeeds

[Cmake-commits] CMake branch, master, updated. v3.6.0-351-g03a5096

2016-07-09 Thread Kitware Robot
_VERSION_MINOR 6) -set(CMake_VERSION_PATCH 20160709) +set(CMake_VERSION_PATCH 20160710) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[cmake-developers] [PATCH v4] For consoles output on Windows use our own std::streambuf

2016-07-09 Thread Dāvis Mosāns
Currently Microsoft's C++ libraries implementation of std::cout/cerr can't output Unicode characters but only ASCII or ANSI if locale is set so we implement and use our own ConsoleBuf which can output Unicode characters to console and it doesn't matter what locale or console's codepage is set. ---

Re: [CMake] Unable to find source files in different directory using target_sources(INTERFACE)

2016-07-09 Thread Robert Dailey
Thanks, I just verified that doing absolute path works. I find it frustrating though that relative paths aren't calculated to absolute at the time the function is called, though. I feel like CMake should be doing this for me. On Sat, Jul 9, 2016 at 7:23 PM, Craig Scott

Re: [CMake] Unable to find source files in different directory using target_sources(INTERFACE)

2016-07-09 Thread Craig Scott
Sorry, hit the send button prematurely. To achieve your desired goal of creating a header only library as a target in Visual Studio, it somewhat depends on what you want to do with that library. If you just want it to be there so you can see the header in the IDE, then simply defining a dummy

Re: [CMake] Unable to find source files in different directory using target_sources(INTERFACE)

2016-07-09 Thread Craig Scott
When using target_sources(), if you specify the source file(s) with a relative path, CMake does not convert that to an absolute path when storing it in the target's SOURCES property (that's my interpretation anyway). The end result is that the source you specify is going to be interpreted as being

[CMake] Unable to find source files in different directory using target_sources(INTERFACE)

2016-07-09 Thread Robert Dailey
I have the following: cmake_minimum_required(VERSION 3.1.0 FATAL_ERROR) project(foo) add_library(foo INTERFACE) target_sources(foo INTERFACE foo.h) add_subdirectory(subdir) And inside subdir, I specify add_executable() and then target_link_libraries(myexe foo). I get an error: Cannot find

Re: [CMake] Issues when cmake prints compiler messages

2016-07-09 Thread Jakob van Bethlehem
Hej Santiago, Before being able to help you further, I guess it makes sense to fill in some details here: which OS, which compiler (version), which version of CMake. Personally I have never seen anything like this on a broad range of OS/compiler combinations. Also, since you suspect the

[CMake] Issues when cmake prints compiler messages

2016-07-09 Thread Santiago Pagola
Hello everyone! I am new on this list, and I would like to ask if someone here has experienced the same error me: When I try to compile any project (or even simple programs), the compiler starts printing information. It seems normal except for the fact that when it comes to variable names,