Hi, Roman!
You can use properties for each target:
C_STANDART
C_STANDARD_REQUIRED
CXX_STANDARD
CXX_STANDARD_REQUIRED
Read online:
https://cmake.org/cmake/help/latest/manual/cmake-properties.7.html#properties-on-targets
And this question is for cmake@cmake.org list :-)
04.03.2016, 16:20, "Rom
FYI verifying_app failed with main.exe failed (3.4.3) because toptool
depends on topdool.dll located only in toptoolfolder. The workaround is to
include toptoolfolder in libs folder for fixup_bundle(main.exe...)
David your answer was helpful to me. I know it's an expected behavior.
Would a patch
Hi Anton,
When I say clang-cl I mean how the official llvm package does it - a 50mb
executable named cl.exe and not clang-cl.exe.
Ninja believes it compiles with visual c++, but instead it compiles with
clang. That's why you need to put the path to clang INCLUDE and PATH first.
Simply rename cla
Indeed I was lucky : It worked with 3.3.1 but not anymore with 3.4.3..
I've got a strang bug with one .NET dll generated near a tool :
CMake Error at C:/Program Files
(x86)/CMake/share/cmake-3.4/Modules/GetPrerequisites.cmake:798 (message):
106>C:/Program Files (x86)/Microsoft Visual Studio
12
Hi Anton,
Zitat von Anton Yartsev :
Here are the results from 'CXX=clang-cl.exe CC=clang-cl.exe cmake -G
"Ninja" ..' :
$ set CXX=clang-cl
$ set CC=clang-cl
$ cmake -G "Ninja" ..
-- No build type selected, default to Debug
-- The C compiler identification is Clang 3.7.1
-- The CXX compiler
Hi,
On 4 March 2016 at 11:16, Anton Yartsev wrote:
Hi Cristian,
thanks for the replay. I have clang-cl first in PATH, the problem persists.
Just to check. Did you run cmake in a new (i.e. empty) build directory
when you fixed that? IIRC once a compiler has been picked
during configure you can
On 03/04/2016 12:42 PM, Dan Liew wrote:
Thanks for this. Shouldn't the fact that ``LINK_FLAGS`` is a string
property and not a list property be in the ``cmake-properties``
documentation? The version of the documentation for my version of
CMake (3.4.3) doesn't say what the property type is.
Perh
On 3 March 2016 at 22:02, Nils Gladitz wrote:
> On 03.03.2016 22:57, Dan Liew wrote:
>>
>> Hi,
>>
>> I noticed recently is you do something like this
>>
>> add_executable(foo a.cpp b.cpp)
>> set_property(TARGET shell APPEND PROPERTY LINK_FLAGS "-fopenmp")
>> set_property(TARGET shell APPEND PROPER
Hi,
On 4 March 2016 at 11:16, Anton Yartsev wrote:
> Hi Cristian,
>
> thanks for the replay. I have clang-cl first in PATH, the problem persists.
Just to check. Did you run cmake in a new (i.e. empty) build directory
when you fixed that? IIRC once a compiler has been picked
during configure you
Hi Cristian,
thanks for the replay. I have clang-cl first in PATH, the problem persists.
$ SET PATH
Path=D:\-Work-\llvm-3.7.1.src\-VS_build VS 2013-\Release\bin;...
$cd D:\-Work-\llvm-3.7.1.src\-VS_build VS 2013-\Release\bin
$dir
Directory of D:\-Work-\llvm-3.7.1.src\-VS_build VS 2013-\Release
The Third International Conference on Computer Science, Computer
Engineering, and Social Media (CSCESM2016)
Metropolitan College, Thessaloniki, Greece
May 13-15, 2016
http://www.sdiwc.net/conferences/cscesm2016/
csces...@sdiwc.net
The published proceedings will be submitted for indexing in Rese
Hi,
I want to use some required Qt component while others are optional. Apparently
if you specify REQUIRED in find_package OPTIONAL_COMPONENTS is ignored.
Here is a minimal CMakeLists.txt:
project(test)
cmake_minimum_required(VERSION 3.5)
find_package(Qt4 REQUIRED COMPONENTS QtCore QtGui OPTIONA
12 matches
Mail list logo
