On 03/31/2017 07:46 AM, ウルヰ wrote:
../Utilities/cmlibarchive/libarchive/libcmlibarchive.a(archive_hmac.c.o):
In function `__hmac_sha1_init':
archive_hmac.c:(.text+0x25): undefined reference to `HMAC_CTX_new'
../Utilities/cmlibarchive/libarchive/libcmlibarchive.a(archive_hmac.c.o):
In function `_
2017-03-31 4:41 GMT+02:00 kipade :
> There are some files I do not want to build if the specified condition was
> ture.
> For example, for testing, I want build a new file witch include a main
> entry just
> for testing; if not, a new file would be compile for normal task.
> I do not want to write
Can confirm that this happens with the latest source from Github as well.
--
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 of
Trying to build CMake 3.8.0-rc4 from source on Ubuntu 16.10 gives the
following output:
$ make
[ 2%] Built target cmsys
[ 3%] Built target cmsysTestDynload
[ 4%] Built target cmsys_c
[ 4%] Built target cmsysTestProcess
[ 4%] Built target cmsysTestSharedForward
[ 5%] Built target cmsysTestsC
There are some files I do not want to build if the specified condition was ture.
For example, for testing, I want build a new file witch include a main entry
just
for testing; if not, a new file would be compile for normal task.
I do not want to write two main entries in the same file just using m
Miller,
Thank you for your input; I'm hoping we can use it to improve our
description of Spack at http://spack.io . I'm cross-posting to the Spack
list, maybe someone there can add to this.
https://github.com/LLNL/spack/issues/2115
There has been talk of a comparison; but I'm not familiar enou
Hi,
I hope this is a simple question and I'm just missing something fundamental.
I'm trying to emulate a binary build manager for an embedded Cortex-M0
target using a CMake project. I'm having some trouble figuring out how to
generate list files for each dependency of my executable target.
The c
I am using CMake 3.7.2 and playing around with the FindThread finder. The
following simple CMakeLists.txt works fine on various compilers: GCC,
clang, MSVC (tried 2013 and 2015).
CMAKE_MINIMUM_REQUIRED( VERSION 3.1 )
ADD_EXECUTABLE( mythread main.cpp )
SET( THREADS_PREFER_PTHREAD_FLAG TRUE )
F
I am proud to announce the fourth CMake 3.8 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.8
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.8/release/3.8.html
Some of the more significant c
30.03.2017, 18:15, "Miller Henry" :
> I have found the following projects which all seem to do some variation of a
> meta build so that you can build multiple projects that depend on each other
> and manage dependencies. (there are a couple others that seem to not be
> maintained as well)
>
>
I have found the following projects which all seem to do some variation of a
meta build so that you can build multiple projects that depend on each other
and manage dependencies. (there are a couple others that seem to not be
maintained as well)
https://gradle.org/
https://bazel.build/
https:
BTW,
I notice this too, if I use the following command line with an empty
cmakelists.txt file : cmake -G "Visual Studio 15 2017 Win64"
And it also generate the .sln (and other files) in the same folder, but
I don't request to build such a solution ! right ?
In reality, I only need a cmakeli
Apologies for not responding sooner... this fell off my radar and I found
it in my email.
On Thu, Jan 12, 2017 at 6:29 AM, David Cole wrote:
> Why not just use a BUILD_COMMAND which builds the VS project using the
> msbuild command line directly?
Do you have an example of this?
Even if this i
I do this using the spack autobuilder. Only problem is it doesn't run on
windows. Maybe Conda?
On Mar 30, 2017 9:45 AM, "Robert Dailey" wrote:
> On Thu, Mar 30, 2017 at 3:42 AM, Tamás Kenéz
> wrote:
> > An alternative to the CMake superbuild: leave your actual project intact.
> > Simply create
Do give it a BINARY_DIR, but do NOT give it a BUILD_COMMAND. Giving it
an empty BUILD_COMMAND means "do nothing" for the build step and using
"cmake --build ./LibraryBuild" does not work unless cmake is in your
PATH, and with a Visual Studio solution, you also need to specify
"--config Release" or
Hi,
I'm currently using one CMakeLists.txt file that will execute an
external CMakeLists.txt (and dependency).
For this I use the ExternalProject_Add command, but I can't find a way
to specify where the ".sln" file will be generated.
I have also created StackOverflow question here with more
On Thu, Mar 30, 2017 at 3:42 AM, Tamás Kenéz wrote:
> An alternative to the CMake superbuild: leave your actual project intact.
> Simply create a separate shell script which builds all the dependencies (by
> running cmake commands). Or, if you do like the ExternalProject stuff,
> create a superbui
An alternative to the CMake superbuild: leave your actual project intact.
Simply create a separate shell script which builds all the dependencies (by
running cmake commands). Or, if you do like the ExternalProject stuff,
create a superbuild which builds only the dependencies.
Tamas
On Thu, Mar 30
18 matches
Mail list logo
