On 9/14/2017 4:45 PM, Bill Hoffman wrote:
On 9/12/2017 1:11 PM, Robert Ramey wrote:
Could we get some response on Edward's suggestion here? It's a serious
obstacle to implementing support of CMake in Boost libraries.
I don't think it would be a problem to implement something like this in
CMak
On 9/14/2017 4:45 PM, Bill Hoffman wrote:
On 9/12/2017 1:11 PM, Robert Ramey wrote:
Could we get some response on Edward's suggestion here? It's a serious
obstacle to implementing support of CMake in Boost libraries.
I don't think it would be a problem to implement something like this in
CMak
On 9/7/2017 10:34 AM, paul via CMake wrote:
On Thu, 2017-09-07 at 02:58 -0400, Edward Diener wrote:
On 9/6/2017 11:39 PM, P F via CMake wrote:
The `add_test` function can run whatever command you want it to, including
compiling a target:
add_library(foo_compile_test STATIC EXCLUDE_FROM_ALL
COMMAND ${CMAKE_COMMAND} --build . --target foo_compile_test
--config $
WORKING_DIRECTORY ${CMAKE_BINARY_DIR})
should work properly ?
On 07/09/2017, 08:59, "CMake on behalf of Edward Diener" wrote:
On 9/6/2017 11:39 PM, P F via CMake wrote:
> The `add_test` fun
empts to compile source file(s) into object file(s), not
create static libraries.
On Sep 5, 2017, at 11:44 AM, Edward Diener
wrote:
On 9/5/2017 2:47 AM, Dvir Yitzchaki wrote:
There's already CheckCXXSourceCompiles and friends.
The only problem is that try_compile is not scriptable ot
CTest.
-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Roger Leigh
Sent: Monday, September 4, 2017 16:51
To: cmake@cmake.org
Subject: Re: [CMake] Adding compile and build type tests to CMake/CTest
On 04/09/17 14:40, Edward Diener wrote:
Boost Build has test
On 9/4/2017 9:51 AM, Roger Leigh wrote:
On 04/09/17 14:40, Edward Diener wrote:
Boost Build has tests for running an application successfully or not,
for compiling one or more source files successfully or not, and for
building one or more source files into an exe or not. These tests in
Boost
Boost Build has tests for running an application successfully or not,
for compiling one or more source files successfully or not, and for
building one or more source files into an exe or not. These tests in
Boost Build are the run/run-fail, compile/compile-fail, and
link/link-fail rules.
CMak
According to the CMake docs for an OBJECT library called, let's say,
'xxx', the reference to that OBJECT library is through
$. I understand this but I am curious about the
reason for such syntax. After all a STATIC or SHARED library 'xxx' you
can just use xxx to refer to the library. Why the di
On 1/30/2017 4:44 AM, Nils Gladitz wrote:
On 01/30/2017 12:44 PM, Edward Diener wrote:
Using the cmake gui program of the latest cmake 3.7.2 I add a cache
entry of CMAKE_CXX_FLAGS to some compile flag value, but as soon as I
hit the generate button the cache entry disappears and is no longer
Using the cmake gui program of the latest cmake 3.7.2 I add a cache
entry of CMAKE_CXX_FLAGS to some compile flag value, but as soon as I
hit the generate button the cache entry disappears and is no longer
retained. Is CMAKE_CXX_FLAGS no longer a valid cmake variable ? If it is
not a valid cmak
n a 32-bit and a 64-bit
version of a library when 'find_package(some_library)' is specified ?
- Chuck
On Tue, Jun 14, 2016 at 8:28 PM, Edward Diener
mailto:eldlistmaili...@tropicsoft.com>> wrote:
Building llvm/clang from source involves using CMake. I am building
llvm/cl
Building llvm/clang from source involves using CMake. I am building
llvm/clang from source on Windows using CMake 3.5.2. I am not a clang
developer, just a clang user. Similarly I just use CMake rather than
understand or write CMakeLists.txt files.
I reported a problem to clang where building
On 4/22/2016 4:51 AM, Mueller-Roemer, Johannes Sebastian wrote:
It is true that there is no official bundled installer with both, but
the official installer works just fine with mingw as long as you pass in
the correct target to clang(++)
For example
clang++ --target=x86_64-w64-mingw32 test.cpp
It would really be nice if the CMake GUI program could save and restore
configurations for whatever CMake setups the end-user uses. By this I
mean the ability to save the paths to the source code and where the
binaries should be built, as well as its corresponding cache
information, under a use
The code is not mine but I am trying to get it to work. On Windows the
code is calling into the FindBoost.cmake package via a find_package
call. Before calling find_package the code sets the Boost_INCLUDE_DIR
and Boost_LIBRARY_DIR to the respective Boost 'boost' and Boost 'libs'
subdirectories
On 7/11/2014 11:01 AM, Bill Hoffman wrote:
On 7/11/2014 10:33 AM, Edward Diener wrote:
Shouldn't there be a way to change the current generator in the CMake
GUI ? It seems like I can only do this if I choose a new "Where to build
the binaries" path. But what if I just want to cha
Shouldn't there be a way to change the current generator in the CMake
GUI ? It seems like I can only do this if I choose a new "Where to build
the binaries" path. But what if I just want to change the current
generator to something else using the current outpath path ?
--
Powered by www.kitwa
On 3/5/2014 3:19 AM, Kevin Funk wrote:
Am Mittwoch, 5. März 2014, 00:29:55 schrieb Edward Diener:
When trying to build llvm/clang on Windows using cmake I execute from a
build directory I created:
cmake -DCMAKE_BUILD_TYPE=Release -G "MinGW Makefiles" ..\llvm
only to receive:
C
When trying to build llvm/clang on Windows using cmake I execute from a
build directory I created:
cmake -DCMAKE_BUILD_TYPE=Release -G "MinGW Makefiles" ..\llvm
only to receive:
CMake Error: CMake was unable to find a build program corresponding to
"MinGW Makefiles". CMAKE_MAKE_PROGRAM is no
20 matches
Mail list logo
