On Sat, 2018-12-29 at 09:01 -0500, Donald MacQueen [|] wrote:
> My machine shows up as M6800 under Site in my remote dashboard.
>
> I want to use my local dashboard, so I did this in
> CTestConfigCTestConfig.cmake:
>
> IF (${SITE} STREQUAL "M6800")
> set(CTEST_DROP_SITE "192.168.49.128") #
On Mon, 2018-12-31 at 13:50 -0500, Donald MacQueen [|] wrote:
> Thanks very much Kyle. I guess I am not real clear about when vars
> should be used as var versus ${var}.
Generally speaking, you use var when setting a variable, and ${var}
when reading its value. It's a lot like how shell variables
On Mon, 2018-12-31 at 16:16 -0500, Donald MacQueen [|] via CMake wrote:
> First, CMake is quite impressive. Nice job.
>
> I am using it in a non-standard way where I set a bunch of variables
> and
> then go straight to CTest thatI installs our software and then runs
> several hundred tests on
On Wed, 2019-01-02 at 12:01 -0500, Donald MacQueen [|] wrote:
> I looked at the example of Using ctest and cdash without cmake
> (https://gitlab.kitware.com/cmake/community/wikis/doc/ctest/Using-CTE
> ST-and-CDASH-without-CMAKE#steercmake)
> and I think I will try to go in that direction.
Micha,
Unfortunately, the WiX generator does not currently support component
installation, which is what's needed to make the INSTALL_TYPES argument
work.
We would welcome a merge request which adds this support.
Kyle
On Thu, 2019-01-17 at 19:28 +0100, Micha Renner wrote:
> With the NSIS
Hello all,
I recently wrote a set of scripts to integrate QtTest into CMake,
similar to the work that Matthew Woehlke did with Google Test a while
back. The script that I wrote runs the test executable in the post-
build stage, records the list of tests in the executable, and generates
a CTest
On Tue, 2019-01-01 at 16:55 -0500, Donald MacQueen [|] wrote:
> No. CMakelists.txt does nothing but download the correct installer
> (32 or 64 bit) from our server, set a bunch of variables, and then
> run CTest. I invoke the InstallShield installer from a command line
> in a CTest.
> There is no
All,
I am pleased to announce that Kitware is now offering an
officially-supported set of Ubuntu packages for CMake. These CMake
packages can be installed with apt-get, just like other Ubuntu
packages. We currently support Ubuntu 16.04 and 18.04.
The following packages are available:
* cmake -
On Thu, 2019-03-28 at 14:58 -0400, Norton Allen wrote:
> because mygeneratedfile is not a 'target', and I can't make it into a
> target with add_custom_target() because that's talking about
> something else entirely (commands that will be run unconditionally,
> not based on dependencies)
What
On Thu, 2019-03-28 at 16:07 -0400, Norton Allen wrote:
> Kyle,
> What you say makes sense, and I can even understand why
> add_custom_target might do that, but I cannot get this to actually
> work. Here is a minimal CMakeLists.txt. mysourcefile is just and
> empty file.
> I have these files in
On Thu, 2019-03-28 at 15:26 -0400, Norton Allen wrote:
> On 3/28/2019 3:11 PM, Kyle Edwards wrote:
> > On Thu, 2019-03-28 at 14:58 -0400, Norton Allen wrote:
> > > because mygeneratedfile is not a 'target', and I can't make it
> > > into a target with add_custom_target() because that's talking
> >
You could build CMake with -DBUILD_TESTING=OFF. This will skip the unit
tests altogether.
Kyle
On Thu, 2019-03-28 at 02:24 +, Scott Bloom wrote:
> Note, Im running from inside visual studio… I do realize for a
> makefile based system, I can run make install from inside the
> executable’s
On Thu, 2019-03-28 at 16:38 -0400, Norton Allen wrote:
> Related to that, I noticed in another thread the mention of
> 'CMAKE_SKIP_INSTALL_ALL_DEPENDENCY'. If that were set in this case,
> how could I indicate that install depends on mygeneratedtarget?
There is no way to do this. C/C++ targets
On Tue, 2019-03-05 at 10:01 -0700, Olivier Gomez wrote:
> Hello,
>
> I have been searching for a way to remove a custom command
> (POST_BUILD
> event) from a target in CMake but, so far, I've found nothing.
>
> I tried to add another custom command to override the first one but
> it seems
> to
On Fri, 2019-03-01 at 17:49 +0800, Yu, Mingli wrote:
> Hi Expert,
>
> I encounter build issue when compile mariadb from
> https://downloads.mariadb.org/mariadb/10.3.13/
>
>
> make[2]: *** No rule to make target 'sql/sql_yacc.cc', needed by
>
On Fri, 2019-03-15 at 17:03 +0100, workbe...@gmx.at wrote:
> Hi everyone,
>
> i try to use find_packages for clang, i'm on debian and have
> installed
> libclang-4.0-dev package, now i've the files in
> /usr/lib/llvm4-0/lib/libclang-4.0.so and the include in
> /usr/lib/llvm-4.0/include/clang -
On Thu, 2019-03-14 at 14:37 -0400, Sean McBride wrote:
> On Thu, 14 Mar 2019 11:58:16 -0400, Robert Maynard via CMake said:
>
> >
> > I am happy to announce that CMake 3.14.0 is now available for
> > download at:
> > https://cmake.org/download/
> Pi version on Pi Day. Nicely done! :)
On Mon, 2019-03-11 at 17:59 +0100, Micha Renner wrote:
> In CPack I can add a component with cpack_add_component and describe
> the component with the additional arguments of the macro.
> I can also describe the component if I use the varibales of type
> CPACK_COMPONENT__XXX (e.g.
>
On Wed, 2019-03-20 at 16:57 -0400, J. Caleb Wherry wrote:
> I was also surprised when "cmake --trace" gave 0 information related
> to the generate step. I assume this is expected behavior?
The purpose of --trace is to debug CMake scripts. No scripts get run
during the generate step, so yes, this
On Mon, 2019-02-18 at 17:04 +0100, workbe...@gmx.at wrote:
>
>
>
> Forwarded Message
> Subject: Re: [CMake] Question about CMAKE_MODULE_PATH
> Date: Mon, 18 Feb 2019 16:58:26 +0100
> From: workbe...@gmx.at
> To: Kyle Edwards
>
> here is my code:
>
>
>
On Mon, 2019-02-18 at 17:59 +0100, Andreas Naumann wrote:
> Hey,
>
> I would introduce a list with the allowed values and introduce a
> macro
> "checked_set", which tests the setting or aborts.
>
> Regards,
> Andreas"
>
> Am 18.02.19 um 15:06 schrieb workbe...@gmx.at:
> >
> > Hi everyone,
> >
On Mon, 2019-02-18 at 16:50 +0100, workbe...@gmx.at wrote:
> Doesn't the content of CMAKE_MODULE_PATH should also include the path
> to
> the default modules ??
The default modules are automatically checked by CMake, independently
of the contents of CMAKE_MODULE_PATH. They should not normally be
Hex,
Can you see what else is in /opt/arm-none-eabi/lib/thumb/v7-
ar/fpv3/hard (the same directory as libc.a)? There might be another
system library that contains the _exit() implementation that isn't
being linked due to your use of the -nostartfiles flag.
Kyle
On Fri, 2019-02-01 at 22:15 +,
Andrew,
FindOpenSSL provides an "OPENSSL_ROOT_DIR" variable which allows you to
specify the root directory of your installation (assuming a traditional
layout within that directory.) Hopefully this will do what you need.
Good luck!
Kyle
On Fri, 2019-02-01 at 16:18 -0500, Andrew Bell wrote:
> I
; libcurl4?
> >
> > Unfortunately libcurl3 conflicts with libcurl4, and I need to keep
> > the later installed for packages that depend on it. The Ubuntu-
> > provided CMake package appears to be built against libcurl4.
> >
> > Steven
> >
> > On 4/5/19
On Tue, 2019-06-04 at 19:38 +0530, vinay kumar Kotegowder wrote:
> The original intent of the snippet is to find the required tool chain
> (On windows : arm-none-eabi-gcc.exe or armclang.exe; On Linix :
> arm-none-eabi-gcc or armclang) path which can later be used to build
> the project.
>
> I
On Tue, 2019-06-04 at 19:07 +0530, vinay kumar Kotegowder wrote:
> Hi Everyone,
>
> This is simple code running on Windows machine:
>
> if(WIN32)
> message(STATUS "On windows")
> find_program(_TOOL
> arm-none-eabi-gcc.exe
> PATHS "C:"
> )
> endif()
>
On Tue, 2019-06-04 at 16:39 +0200, Steven Truppe wrote:
> Hi everyone,
>
>
> i had the same question a few days ago but can't rember the command
> (and
> can't find it in the cods):
>
> I have a regular expression like "WITH_LIB${lib}_EXAMPLE_([A-Za-z]+)"
> and i want the get the content of the
On Tue, 2019-06-04 at 17:11 +0200, Steven Truppe wrote:
> I want the output not to be 'in' but 'glade' ...
>
>
> On 04.06.19 17:10, Steven Truppe wrote:
> >
> > Hi everyone again,
> >
> >
> > i've the following code:
> >
> > https://paste.debian.net/1086040/
> >
> > and i just try to
On Tue, 2019-06-04 at 19:19 +0200, Steven Truppe wrote:
> I found the solution:
> get_cmake_property(_vars VARIABLES)
> foreach(_var ${_vars})
> string(TOUPPER ${lib} lib_upper)
> if(_var MATCHES "^WITH_LIB_${lib_upper}_EXAMPLE_([A-Za-
> z]+)$")
>
On Fri, 2019-05-31 at 19:07 +0200, Steven Truppe wrote:
> The problem is the line:
> if(${_var} MATCHES "^WITH_LIB_([AZaz]+)$")
> cmake_print_variables(CMAKE_MATCH_0)
>
> doesn't print me any output ...
There are two problems with the following line:
if(${_var} MATCHES "^WITH_LIB_([AZaz]+)$")
On Fri, 2019-05-31 at 20:43 +0200, Steven Truppe wrote:
> macro(bsAddLibrary lib)
> # get all WITH_LIB varables
> message(STATUS "${lib}")
>
> get_cmake_property(_variables VARIABLES)
> foreach(_var ${_variables})
>
> -->> (${lib} is "WITH_LIB_GLAD" but allways return
All,
I am pleased to announce that we are now offering Ubuntu builds of the
CMake release candidates, in addition to the production releases. The
first available release candidate build is 3.15.0~rc1-0kitware2.
If you would like to receive release candidate builds, follow the
instructions at
On Fri, 2019-05-10 at 12:06 -0500, Dustyn Blasig wrote:
> Hi All,
>
> I'm curious if anyone has had success allowing two testing paths to
> coexist well.
>
> Currently, we are using CTest to run our test executables with `make
> test`. However, on our Jenkins system, the build machines have the
On Wed, 2019-05-08 at 00:52 +0300, Maris Razvan wrote:
I apologize for the spelling error in the subject of this thread.
I was told that this sentence actually states that lines inside a
(single) command argument cannot end in a line comment.
I initially thought that "Command Arguments" in this
On Thu, 2019-08-29 at 18:27 +0100, hex wrote:
> hello community,
>
> CMake builds a C project with gcc -o target_name. I have a compiler
> very similar to GCC and I am trying configure CMake C language for
> it.
>
> The compiler does not support the -o argument when linking objects. I
> wonder
On Wed, 2019-09-04 at 14:12 -0400, fdk17 wrote:
> https://github.com/microsoft/vscode-cmake-tools/issues/752 states
> that it ran out of stack and the log shows what looks like to be
> involved with a recursive loop in some CMakeLists.txt. A call depth
> of 27491 seems a bit excessive.
>
> After
On Wed, 2019-09-11 at 21:40 +0300, Avraham Shukron wrote:
> Hi!
>
> I'm pretty new to cmake and I came across a question which I could
> not find any information about in the official documentation or blog
> posts.
>
> When adding a target through add_library / add_executable - should
> the
On Wed, 2019-09-11 at 22:00 +0300, Avraham Shukron wrote:
>
>
> On Wed, Sep 11, 2019 at 9:49 PM Kyle Edwards m> wrote:
> > You can list them or not list them. CMake will recognize them as
> > header
> > files and ignore them (not attempt to compile them.) It's a matter
> > of
> > personal
On Wed, 2019-09-11 at 17:33 -0400, Michael Jackson wrote:
> Already looked on google and at the CMake documentation but
> everything listed does not seem to work so here is the setup.
>
> I am using MKL and I have a home grown FindMKL since there isn’t an
> official one. Inside that is the
On Fri, 2019-09-13 at 15:25 +, Stephen Morris wrote:
> Suppose I have a class that derives from QObject, and contains the
> Q_OBJECT macro in its header file. When I compile it using AUTOMOC
> enabled, a "moc_myClass.cpp" file is created; if I manually include
> that file at the end of my
On Sun, 2019-09-08 at 14:07 -0500, Isuru Fernando wrote:
> Hello,
>
> I can use the following to get try_compile to include one directory.
>
> CMAKE_FLAGS "-DINCLUDE_DIRECTORIES=dir1"
>
> How do you use try_compile when I have multiple directories to pass
> to it?
>
> Isuru
Use a semicolon:
On Thu, 2019-12-12 at 15:15 +0100, René J.V. Bertin wrote:
> Hi,
>
> If I understand correctly, configuring CMake for building means
> bootstrapping a basic version of itself which is then run on the
> included CMakeLists.txt file. That takes a lot of time
> (comparatively) which begs the
On Sun, 2019-10-20 at 19:25 +0200, Sérgio Agostinho wrote:
> Hey everyone,
>
> I’m shipping a config file for my library and inside I set push/pop
> specific policies so that me and the consumers of my library can
> target different policies without us clashing against each other.
> However I’m
On Mon, 2019-10-21 at 10:23 +0100, David Aldrich wrote:
> I have a simple CMake project with subdirectories:
>
> cmake_minimum_required(VERSION 3.10)
> project(MyProject VERSION 1.0.0)
>
> set(CMAKE_VERBOSE_MAKEFILE ON CACHE BOOL "ON")
>
> add_subdirectory(say-hello)
>
On Mon, 2019-10-21 at 21:39 +0200, Sérgio Agostinho wrote:
> For further users with the same problem, you likely do not need need
> to invoke cmake_policy(PUSH)/cmake_policy(POP) from your shipped
> Config file, so just delete them and set whatever policies you need
> without concerns.
This has
On Wed, 2019-11-20 at 00:54 +0100, cen wrote:
> Hi
>
> I have an existing c++ exe project which I want to test with gtest.
> I
> have not yet found an easy way to keep the project as is and test it
> directly since gtest insists (obviously) to link against the code
> being
> tested. I found a
On Tue, 2019-09-24 at 23:41 +0300, Avraham Shukron wrote:
> Hi!
>
> I have a library which I want to distribute in both shared object and
> static library forms.
> Is there a modern way to do it without creating two completely
> separate library targets?
> Since I want to be a good CMake citizen
On Thu, 2019-10-03 at 17:08 -0400, stefan wrote:
> Yes, that is exactly what I'm trying to do, but it doesn't seem to
> have any effect. That is, `dpkg --info ...` doesn't list the
> additional dependency, and correspondingly, running `apt-get install
> ...` on the component package file will
On Thu, 2019-10-03 at 16:30 -0400, stefan wrote:
> Hi Kyle,
> thanks for the quick followup.
> On 2019-10-03 4:23 p.m., Kyle Edwards wrote:
> > Please take a look at cpack_add_component():
> > https://cmake.org/cmake/help/latest/module/CPackComponent.html
> I'm not sure what specifically I should
On Thu, 2019-10-03 at 16:15 -0400, stefan wrote:
> I'm trying to generate (debian) packages for a project of mine using
> cmake. I need to generate multiple components ("runtime",
> "development", etc.). What is the expected way to have the
> "development" package depend on the "runtime" package ?
On Fri, Oct 11, 2019 at 1:36 AM Alan W. Irwin
wrote:
> The source files that have COMPILE_OPTIONS, COMPILE_DEFINITIONS,
> COMPILE_FLAGS, or INCLUDE_DIRECTORIES will also be skipped."
This is by far the most likely reason. We added this restriction
because we don't want files that have different
On Mon, 2020-02-10 at 12:49 +, hex wrote:
> hello,
>
> My build step is not thread-safe (the instruction in the COMMAND
> part). Every build step depends on one source file:
>
> add_custom_command(
> DEPENDS on_source.file
> OUTPUT
>
On Sun, 2018-12-30 at 13:09 -0800, Saleem Abdulrasool wrote:
> Hi,
>
> I was looking at supporting Swift as a language in CMake. I know
> that CMake has some preliminary support that assumes that you are
> building on macOS with Xcode. I am trying to support building swift
> libraries and
Hello everyone,
One of the things that's long been requested of CMake is the ability to
have multiple toolchains - for instance, one host toolchain and one
cross toolchain, so that "utilities" needed for build can be built with
the host toolchain and then the "real" software can be built with the
Eric,
Thanks for the feedback. See comments below.
On Mon, 2018-12-17 at 22:06 +0100, Eric Noulard wrote:
> > This has some common design issue as my proposal:
> > enable_cross_target(...)
> > for which Eike has valuable doubt:
> >
On Tue, 2018-12-18 at 06:14 -0500, frodak17 wrote:
> What first cross my mind with '"utilities" needed for build' is when
> you have to build the cross-compiler in the first place before you
> build anything for the target.
> If so how do you handle verification of the tool-chain can build a
>
On Sat, 2018-12-22 at 16:57 +0100, Torsten Robitzki wrote:
> What I’m still missing is support to define dependencies between
> different targets (build by different toolchains), so that I can
> describe that I require a tool that is build with the HostToolChain,
> to generate a file that is
On Tue, 2018-12-18 at 16:12 -0500, frodak17 wrote:
> So it would be something like project( [TOOLCHAIN
> [LANGUAGES] [...]) where TOOLCHAIN
> and its supported languages can be repeated for each tool chain. i.e
> project(whatever TOOLCHAIN default LANGUAGES cpp TOOLCHAIN cross
> LANGUAGES c)
I
On Tue, 2018-12-18 at 20:53 -0500, frodak17 wrote:
> I have thought about it which is why I asked. The original
> assumption of one toolchain per CMake project is being extended. So
> why not think of extending the build type. Sure it's simpler to
> ignore the build type. However, it doesn't
On Tue, 2018-12-18 at 14:10 -0500, frodak17 wrote:
> How does this work with multiple languages and the project() command
> and enable_language() commands?
Both project() and enable_language() could be extended with an optional
TOOLCHAIN argument.
> For instance you want to use the host c++
On Thu, 2019-01-24 at 12:31 -0800, Venedict Tchistopolskii wrote:
> Nevermind, fixed the cmake-gui.
Ah OK, then disregard my response.
> Would be nice to know how to triger the proper install/release config from
> VStudio, atm I do this:
> cmake . --target install --config Release
This looks
On Thu, 2019-01-24 at 12:25 -0800, Venedict Tchistopolskii wrote:
> The install command auto-installs release right?
> How do I trigger this 'install' from VStudio?
> Is building in VStudio enough before install?
> e.g. generate solution -> build in VStudio -> run install
> command in CLI?
All,
I am pleased to announce that Kitware is now offering an
officially-supported set of Ubuntu packages for CMake. These CMake
packages can be installed with apt-get, just like other Ubuntu
packages. We currently support Ubuntu 16.04 and 18.04.
The following packages are available:
* cmake -
On Sat, 2019-04-06 at 10:56 +0200, Rolf Eike Beer wrote:
> Nice!
>
> The magic spell for TravisCI is:
>
> addons:
> apt:
> sources:
> - sourceline: 'deb https://apt.kitware.com/ubuntu/ xenial main'
> key_url: 'https://apt.kitware.com/keys/kitware-archive-2019.a
> sc'
>
On Fri, 2019-01-25 at 09:18 +0100, Gößwein Matthias / eeas gmbh wrote:
> However, the manual does not describe this behavior, maybe it should
> be
> mentioned there.
> (https://cmake.org/cmake/help/v3.13/manual/cmake-gui.1.html)
Even better, perhaps we should add explicit -B and -S options the
Venedict,
Currently, cmake-gui only lets you specify a build or source directory,
not both.
I've opened https://gitlab.kitware.com/cmake/cmake/merge_requests/2863
to add explicit -S and -B options to cmake-gui, which will allow you to
specify both.
Kyle
On Fri, 2019-01-25 at 08:10 -0800, Venedict
On Fri, 2019-01-25 at 13:23 -0800, Venedict Tchistopolskii wrote:
> Get 2 CMake projects.
>
> Get CMake GUI to 'configure' one of them. Close/re-open and it will
> automatically point to this configured project source and build
> locations, regardless of what build/version/cmake-gui.exe you use.
On Fri, 2019-01-25 at 12:55 -0800, Venedict Tchistopolskii wrote:
> Cherry picked and tested. Works great, thank you!
Great, glad to hear it!
> Now, if only the source/build path would stick around, without requiring
> config to be triggered. :P
Can you clarify what you mean by this?
Kyle
>
--
Venedict,
To relocate cmake.exe, it's not sufficient to just copy the executable
- you have to install all of the modules along with it. You do this by
running the "install" target.
Given a path to where you want to put CMake, you would build it like
this:
cmake C:/Path/To/CMake/Source
I forgot to mention - building it this way doesn't require the use of a
toolchain file - it was in response to this:
> Trying to do so because building CMake without toolchain gives me the
below; After I move cmake.exe to another directory:
If you build it as I laid out below, you won't need a
On Thu, 2019-01-24 at 09:23 -0800, Venedict Tchistopolskii wrote:
> I was building it via VStudio and generating the solution via CMake,
> is that wrong?
Nope! You're building it just fine. The only problem is in the
installation - you were installing cmake.exe without all of the
external files it
On Thu, 2019-01-24 at 12:36 -0500, Kyle Edwards wrote:
> cmake --build . --target install
> windeployqt C:/Path/To/Where/I/Want/To/Install/bin/cmake.exe
Oops - this should obviously be
C:/Path/To/Where/I/Want/To/Install/bin/cmake-gui.exe.
Kyle--
Powered by www.kitware.com
Please keep messages
On Thu, 2019-01-24 at 09:27 -0800, Venedict Tchistopolskii wrote:
> Er, lemme clarify.
>
> Can cmake-gui.exe be built along with cmake if using the install path
> setting? I currently use windeployqt to handle gui dependencies.
Yes, like I mentioned, just build with BUILD_QtDialog=ON. You can
On Fri, 2019-01-25 at 14:06 -0800, Venedict Tchistopolskii wrote:
> Could you clarify on saving the build-directory section?
>
> I'm not sure how it knows which cache or build directory to load. In
> my setup here the issue I noted applies even if build directory is
> generated on both
All,
I am pleased to announce that we are now offering Ubuntu builds of the
CMake release candidates, in addition to the production releases. The
first available release candidate build is 3.15.0~rc1-0kitware2.
If you would like to receive release candidate builds, follow the
instructions at
On Fri, 2019-08-30 at 17:36 +0300, Eugene Karpov wrote:
> Hello all,
>
> I'm working on a cross platform project. On Ubuntu I would like to
> save all the compiler options, definitions and other complier related
> stuff to a generated file to use it later for precompiled header
> generation.
> My
On Fri, 2019-08-30 at 17:54 +0300, Eugene Karpov wrote:
> I've tried this. But then it fails to compile due to `INTERFACE
> API=${API_EXPORT_MACRO}` target compile definition.
Ah right, you want the file contents to be escaped while the compile
flags are not. My next suggestion was going to be to
On Fri, 2019-08-30 at 19:01 +0300, Eugene Karpov wrote:
> Not working too.
> The failed lines in a generated make file looks like this
> ---
> CMakeFiles/mkflags_test:
> /usr/bin/cmake -DDEFINITIONS=-
> DAPI=__attribute__((visibility("default"))) -
>
On Fri, 2019-09-13 at 22:08 +0530, Tushar Maheshwari wrote:
> Hi,
>
> I am a C++ developer and a modern-C++ enthusiast. In the interest of
> modernizing the codebase, I propose using smart pointers to handle
> dynamically allocated memory. I would like to get the feedback from
> the developers if
Please open an issue at https://gitlab.kitware.com/cmake/cmake/issues
to request support for this.
Kyle
On Tue, Oct 29, 2019 at 9:58 AM Nicolas Desprès
wrote:
>
> Hi there,
>
> Generator expressions are allowed in the FILES/PROGRAMS and DESTINATION part
> of an install command.
>
> Would that
81 matches
Mail list logo
