he 'debug' folder (where the exe is
correctly being put).
$CMAKE_RUNTIME_OUTPUT_DIRECTORY and $RUNTIME_OUTPUT_DIRECTORY are
undefined.
How would I achieve this?
Which variable holds the exe output path: build_msvc/debug?
Best regards
David
--
Powered by kitware.com/cmake
Kit
Fixed using OBJECT libraries. Thank you to anyone here who answered on
StackOverflow.
On Fri, Nov 8, 2019 at 12:02 PM David Aldrich
wrote:
> Hi, I have a linker problem with a Windows C++ project that uses a static
> library. I have described the problem on StackOverflow here:
>
resolved by adjusting the CMakeLists.txt
file. Please could someone have a look at the above link and comment
either in StackOverflow or reply here?
I am using Ninja with the VS2019 C++ compiler on Windows 10.
Thanks in advance,
David
--
Powered by www.kitware.com
Please keep messages on-topic and
tar_lib_name}
> ${LibType}
> ...
> )
>
> (Feel free to modify the if(), use CMAKE__COMPILER_ID (
> https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_COMPILER_ID.html)
> etc. as necessary).
>
> Petr
>
> On Thu, 7 Nov 2019 at 12:28, David Aldrich
> wrote:
>
>>
I want to build a shared library for Linux and a static library for
Windows. So I have tried:
set (_star_lib_name "StdStars")
add_library(${_star_lib_name}
$<$:SHARED>
$<$:STATIC>
""
)
but that gives me error:
CMake Error at
C:/SVNProj/zodiac/branches/
a
get_filename_component call, (or otherwise), and pass in a string that
begins with "/" ...?
Hope this helps,
David C.
On Mon, Oct 28, 2019 at 4:36 PM Roman Wüger wrote:
>
>
>
> Hello,
>
>
>
> I tried to install a file/directory with productbuild on macOS whi
Just to say, I have fixed this problem, so no help needed now.
--
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 offering, ple
e source file, as it seems that the executable needs at
least one SOURCE file. Is there a way around this?
2) How can I tell CMake to use the
'-Wl,-whole-archive,-export-dynamic,--no-as-needed' flags?
Best regards
David
--
Powered by www.kitware.com
Please keep messages on-topic and
>
> >What generator are you using?
>
Ninja
> That thread seems to contain a lot of misunderstandings about the issue.
>
> If you are using the Makefile generator then refer to
> https://stackoverflow.com/questions/7461000/handling-header-files-dependencies-with-cmake.
> After building the projec
Hi again,
My CMakeLists.txt file for my shared library contains:
add_library(MyLib SHARED my_source.cpp etc.)
target_include_directories( MyLib PRIVATE ../MyHeaders)
The library builds ok, but there is no dependency on directory ../MyHeaders
- touching a header file does not result in a re-compi
>
> >Does just invoking ninja with -v not show verbosity? That should do it.
> > don't believe CMAKE_VERBOSE_MAKEFILE affects Ninja builds.
>
> >Kyle
>
Yes thanks, that does do it. I just wondered whether there was a neater way
for when CMake is invoked by an IDE such as VS Code with the cmake-too
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)
add_subdirectory(hello-exe)
Will the 'CMAKE_VERBOSE_MAKEFILE' option be inherited by the CMakeLists
Hi Eric
Thanks very much for your answer. I understand now.
David
On Fri, Oct 18, 2019 at 12:57 PM Eric Noulard
wrote:
>
>
> Le ven. 18 oct. 2019 à 12:53, David Aldrich
> a écrit :
>
>> Hi
>>
>>
>>
>> I'm learning how to use hierarchic
Hi
I'm learning how to use hierarchical directories in CMake and am trying to
get an example to work that I saw on YouTube. The example isn't doing what
I expect so I would be grateful for some help in understanding why.
I am running CMake 3.10.2 on Ubuntu 18.04 (Microsoft WSL) and using make
basics of CMake, the issue here is how to handle the make
of source code and libraries spread across a directory hierarchy).
Best regards
David
--
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
>
> David,
>
> I think a bit more explanation of the philosophy (at least how I
> interpret it) is needed. I see in your emails that you are “targeting
> makefiles”. With CMake you need to really stop thinking this way. Rarely do
> you need to target any specific build s
>
> > What would best practice be to provide convenient commands for our
> > developers to easily build the target ?
>
> For the Makefile generator, best practice is to use separate build
> directories (i.e., places where you run cmake) for different
> configurations (i.e., different settings recor
>
> > I would also like this to work if I use the make targets e.g. make
> > debug.
>
> I think that's outside the scope of the Makefile generator. For that
> generator, CMAKE_BUILD_TYPE is a configuration-wide setting. If you
> want a different configuration, you need a different build directory
Le 21/06/2019 à 15:42, David Aldrich a écrit :
Do never test CMAKE_BUILD_TYPE in CMakeLists.txt files, it is
ignored in
multiple generators (e.g. Visual Studio).
Does that mean I shouldn't have this in CMakeLists.txt? :
# Specify a Release build by default
if(NOT CMAKE_BUILD
>
> Do never test CMAKE_BUILD_TYPE in CMakeLists.txt files, it is ignored in
> multiple generators (e.g. Visual Studio).
>
Does that mean I shouldn't have this in CMakeLists.txt? :
# Specify a Release build by default
if(NOT CMAKE_BUILD_TYPE)
set(CMAKE_BUILD_TYPE "Release")
message(STATUS "Bu
Le 21/06/2019 à 15:19, David Aldrich a écrit :
I now want to support separate target directories: build/debug and
build/release. I've shown my CMakeLists.txt below. So far I've just
added an attempt to support build/debug:
if (CMAKE_BUILD_TYPE EQUAL "DEBUG")
Thanks for the help I have received in the past few days. I am making
incremental improvements to my CMake project and have a new challenge. I
am running CMake 3.13 on Centos 7.6, targeting make. My CMake file
successfully builds debug or release targets and puts the executable in an
out-of-sourc
Thanks for all the replies. I decided to set CC and CXX in .bashrc:
source scl_source enable devtoolset-7
export CXX="/opt/rh/devtoolset-7/root/usr/bin/g++"
export CC="/opt/rh/devtoolset-7/root/usr/bin/gcc"
For reference, the FAQ entry is:
https://gitlab.kitware.com/cmake/community/wikis/FAQ#how-
My Centos 7.6 machine has CMake 3.13.5 and g++ 4.8.5 installed:
$ /usr/bin/x86_64-redhat-linux-g++ --version
x86_64-redhat-linux-g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
I have a very simple CMakeLists.txt:
cmake_minimum_required(VERSION 3.5 FATAL_ERROR)
project(hello_world LANGUAGES CXX)
ad
19 at 10:06 AM Eric Dönges wrote:
> >
> > On 18.06.19 12:53, David Aldrich wrote:
> > > I have a simple CMake project that builds an executable using Visual
> > > Studio 2017:
> >
> >
> > &g
>
> > On Tue, Jun 18, 2019 at 3:07 PM Eric Dönges wrote:
> > On 18.06.19 12:53, David Aldrich wrote:
> > > I have a simple CMake project that builds an executable using Visual
> > > Studio 2017:
> >
> >
> > >
> > >
I have a simple CMake project that builds an executable using Visual Studio
2017:
#==
cmake_minimum_required(VERSION 3.5 FATAL_ERROR)
### Variables.
# Change if you want modify path or other values. #
##
or 'hiredis'
[ 6%] Performing download step (download, verify and extract) for 'hiredis'
-- Downloading...
dst='/home/david/projects/clipseekr/hiredis/v0.9.0.tar.gz'
timeout='none'
-- Using src='https://github.com/redis/hiredis/archive/v0.9.0.tar
set(HIREDIS_DIR ${CMAKE_CURRENT_SOURCE_DIR}/hiredis)
set(HIREDIS_INCLUDE_DIRS ${HIREDIS_DIR}/include)
ExternalProject_Add(hiredis
URL https://github.com/redis/hiredis/archive/v0.9.0.tar.gz
PREFIX ${CMAKE_CURRENT_BINARY_DIR}/hiredis
SOURCE_DIR ${CMAKE_CURRENT_BINARY_DIR}/hiredis
DOWNLOAD_DIR
to have the same layout as
the "app1" project which currently is not the case.
In the "build all" project, app1 is a directory
In the "app1" project, app1 is a binary
Thanks for your help
David
---
/CMakeLists.txt
till need to be able to build all applications in one
single command.
Do you think creating a "meta" cmake, equivalent to what we have right
now, but on top of those independent, per-app cmake, is feasible ?
(Again, I guess using ExternalProject_Add) ?
Thanks very much for your help
David
--
Hi there - I'm not a CMake person, but a Clang/LLVM developer who helped in
the implementation of Split DWARF in Clang/LLVM, so I know a bit about DWOs
and DWPs, etc & thought I'd offer a few extra details...
On Fri, Dec 21, 2018 at 3:39 AM David Jobet
wrote:
> Hello,
>
&g
revious to the install step itself ? (for the same
reason I don't want to manually define a POST_BUILD step on each
binaries, I don't want to manually define a custom INSTALL step that
would precede the INSTALL step of all our binaries)
- or another option ?
With regards
David
--
Powered
If you're willing to run a different command or flag when rebuilding after
upgrading system libraries, I would guess the thing to do would be to do a
clean and rebuild, perhaps?
On Sun, Dec 16, 2018, 4:24 PM Kris Thielemans Hi all
>
>
>
> I’ve just had a problem caused by an upgrade of my system
brary-config.cmake DESTINATION lib/cmake/yourlibrary)
And create yourlibrary-config.cmake with
include("${CMAKE_CURRENT_LIST_DIR}/yourlibrary-targets.cmake")
Regards
--
David
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org
es not
provide any .pc file.
Also, Gtk is much more tied to Linux than being portable. I think that's
why portable software don't use Gtk that much and thus, not CMake either.
Regards,
--
David
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
d me:
https://medium.com/@authmane512/how-to-do-android-development-faster-without-gradle-9046b8c1cf68
https://stackoverflow.com/questions/41132753/how-can-i-build-an-android-apk-without-gradle-on-the-command-line
Regards
--
David
--
Powered by www.kitware.com
Please keep messages on-topic and chec
ld
\"${CMAKE_BINARY_DIR}\" --target docs --config $)")
endif()
so long as care is taken within each directory's CMakeLists.txt to place the
above before any install() directives related to the generated documentation.
David
[1]: https://gitlab.kitware.com/c
Le 16/10/2018 à 23:04, Frank Tocci a écrit :
Hello,
I am trying to install Cmake and I am running into an error when I
enter the install directory and run
sudo ./bootstrap && make && make install
as specified in the README file
Hello,
You're not supposed to do sudo bootstrap. You should al
/apps/homefs1/USER/work/.../libllvm/icc/include
So if -isystem are searched last, then if there's a way to tweak
INTERFACE_INCLUDE_DIRECTORIES to use -I instead of -isystem that would
also work.
David
On Fri, Oct 12, 2018 at 9:02 AM Craig Scott wrote:
>
>
>
> On Fri, Oct 12, 2018 at
t the include directories needed by
global::llvm to be prepended (instead of appended) ?
With regards
David
--
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
l
configuration.
Along those lines:
1. Is there any ordering of INSTALL(CODE ...) relative to INSTALL(FILES ...)?
If it is guaranteed to run first, we could force the target to build that way.
2. Is there really nothing to replace the deprecated PRE_INSTALL_SCRIPT
property?
Thanks,
!
David
Le 25 septembre 2018 21:15:54 GMT+01:00, Alexander Neundorf
a écrit :
>On 2018 M09 25, Tue 16:53:27 CEST David Jobet wrote:
>> > What I do have a problem is rerunning protoc automatically on
>proto-files
>> > which import proto files that have been modified.
>
hat will
just list the imports recursively.
I will add that as DEPENDS to the add_custom_command.
David
On Thu, Aug 23, 2018 at 9:36 PM Alexander Neundorf wrote:
>
> On 2018 M08 23, Thu 12:50:14 CEST David Jobet wrote:
> > Hello,
> >
> > I'm trying to port an existing pro
Hello,
glad that could help you.
For your newer problem, you don't describe them, so it's tough to know
what kind of problems you're facing.
Maybe a small example of your CMakeLists.txt + a capture of the error
cmake gives you could help ?
David
On Fri, Sep 21, 2018 at 4:52 P
ppy to know of other ways)
David
On Thu, Sep 20, 2018 at 5:45 PM Ke Gao wrote:
>
> Hi,
>
> I have a project which includes many sub-projects. Each sub-project generates
> a static library. In the main project, I want to combine the generated objs,
> generated static libraries fr
And indeed, the namespace is now correct :
$ cat build/lib1/b.pb.h | grep AddDesc
void protobuf_AddDesc_lib1_2fb_2eproto();
friend void protobuf_AddDesc_lib1_2fb_2eproto();
Again, does anyone know how to make this works without the patch ?
If not, how do someone proposes a patch on cmake ?
ed in cmake ?
it defines a new option PROTO_PATH, so the decl above becomes
protobuf_generate_cpp(PROTO_SRCS PROTO_HRDS PROTO_PATH ${CMAKE_SOURCE_DIR}
a.proto b.proto)
With regards
David
$ diff share/cmake-3.10/Modules/FindProtobuf.cmake.orig
share/cmake-3.10/Modules/FindProtobuf.cmake
123c123
<
http://practice.deloresmontez.com
David Henderson
--
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 offering, please visit
http://moreover.singlepotatoes.com
David Henderson
--
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 offering, please
I'm trying to build the lapack library I obtained from
http://www.netlib.org/lapack/lapack-3.8.0.tar.gz. using the clang C
compiler and the xlf Fortran compiler with cmake 3.11. I'm using a Power 9
Linux system running Red Hat 7
The default behavior for the xlf compiler is to mangle Fortran so
> so it is deployed
>aside of CMake itself
This sounds like more of a reasonable proposal. CMake should by itself
not propose any Find* package anymore. A user-managed repository where
everyone could push their module could be a good idea (just like AUR,
PPA, copr, and such do for distributi
On Mon, Apr 30, 2018 at 3:30 PM Stephen Kelly wrote:
> On 04/20/2018 01:39 AM, David Blaikie wrote:
>
> Hi there,
>
> I'm experimenting with creating examples (& potential changes to CMake
> itself, if needed/useful) of building clang modules (currently using the
Hi there,
I'm experimenting with creating examples (& potential changes to CMake
itself, if needed/useful) of building clang modules (currently using the
semi-backwards compatible "header modules", with the intent of also/moving
towards supporting pre-standard C++ modules in development in Clang).
at! Nice catch. I'll reconsider using prefix then. I've
usually named my options WITH_FOO, do you recommend to use
PROJECT_WITH_FOO or WITH_PROJECT_FOO then?
--
David
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMa
over this?
I personally do not want to prefix all my options in my project with
the project name prefix, I think that would be a bit ugly, and I do
want this macro to build and install the documentation.
Any advice/comment is welcome.
Regards,
--
David
--
Powered by www.kitware.com
Please
On Sat, 2018-03-17 at 23:15 +0100, Volker Enderlein wrote:
> Hi David,
>
> Boost changed its naming scheme starting from version 1.66. So its
> not
> your fault but the FindBoost.cmake does not know how to handle the
> new
> scheme. Try to use one of the 3.11.0-rc[1-3]
log".
I can't understand what I am missing because it's not the first time I
use boost on Windows though. I've tried set BOOST_ROOT to the same value
as CMAKE_PREFIX_PATH with no results.
--
David Demelier
--
Powered by www.kitware.com
Please keep messages on-topic and check
Read all about it in this blog post:
https://blog.kitware.com/events/march2018-free-vtk-paraview-and-cmake-training-courses-kitware
There are a few seats available in case you can make it up to visit us.
https://goo.gl/forms/M3WmJcV9W6qKTK8x2
Thanks and hope to see you here.
David E DeMarle
On Sun, 18 Feb 2018, David Adam wrote:
> Our project installs an empty directory for other programs to drop files
> in, the location of which is overrideable with a cache variable. Some
> environments set the location of this directory outside the writeable
> area and create it th
at fails if the destination is not writeable.
Is there an idiomatic way of ignoring a failed installation step? At the
moment, I'm trying various install(script code execute_process(...
incantations, but I'm aware there's lots of corner cases with DESTDIR and
so on.
Thanks
David
x27;m not
entirely certain yet, but I think the CMake slides will be too.
In the next run through we will very likely open it up and at least post
videos after the fact.
thanks
David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
O
preferable (all other things being equal) for C3 to be chosen as the C compiler
since it maximizes the number of Fortran compilers with which the software can
be built.
Does CMake current offer any support in this area? Are there any plans to
implement / extend such support?
Many tha
and Friends"
all day: w/ Bill Hoffman
To reserve a seat for the course, please fill out this google form and
we'll get back to you to confirm your reservation.
https://goo.gl/forms/M3WmJcV9W6qKTK8x2
David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 120
omething like 5 or 6 years now...), but
still people write new find modules.
Thanks,
David C.
On Sun, Oct 1, 2017 at 11:52 AM, Alexander Neundorf
wrote:
> On 2017 M08 29, Tue 11:33:15 CEST David Cole via cmake-developers wrote:
>> That's correct:
>>
>> find modul
le that's associated with the project
containing the source you changed and delete it.
Then run the build from the top and that one and everything that
depends on it afterwards should rebuild.
HTH,
David C.
On Thu, Sep 21, 2017 at 7:09 AM, J Decker wrote:
> how do I make sure that ext
to find the exact
one you already know you have...
On Tue, Aug 29, 2017 at 11:49 AM, Brad King wrote:
> On 08/29/2017 11:33 AM, David Cole wrote:
>> That's correct:
>>
>> find modules do what they want, and most do not pay attention to
>> CMAKE_PREFIX_PATH.
&g
ause I have other libraries that get installed in
>> that directory, each with their own directory to contain their
>> installation files. If find_package() is appending to
>> like it says it should, it should find each one of them without
>> switching the value of CMAKE_PR
lib and all your other stuff too by using two directories
as your CMAKE_PREFIX_PATH value.
HTH,
David C.
On Tue, Aug 29, 2017 at 11:11 AM, Robert Dailey
wrote:
> What I'm hoping for is that find_package() follows the rules it
> documents here:
> https://cmake.org/cmake/help/v3.6/comman
Shouldn't the "/zlib" at the end be included in your CMAKE_PREFIX_PATH?
On Tue, Aug 29, 2017 at 11:01 AM, Robert Dailey
wrote:
> On Tue, Aug 29, 2017 at 9:56 AM, Brad King wrote:
>> On 08/29/2017 10:55 AM, Brad King wrote:
>>> On 08/29/2017 10:48 AM, Robert Dailey wrote:
CMAKE_PREFIX_PATH:
ake
--version"...
If you want to force the one you've downloaded to run instead of that
one, you could **prepend** to the PATH instead of appending to it.
HTH,
David C.
On Mon, Aug 7, 2017 at 9:07 PM, Adam Getchell wrote:
> Hi all,
>
> The CMake 3.9.0 Windows zip file gi
t:if(CMAKE_CONFIGURATION_TYPES)
On Wed, Aug 2, 2017 at 2:42 PM, Marcus D. Hanwell
wrote:
> On Wed, Aug 2, 2017 at 1:32 PM, David Cole wrote:
>> Very cool, Marcus. Thanks for the blog post.
>>
>> Florian, when you "message(${CMAKE_CONFIGURATION_TYPES})" it is
empty,
and you should not give it contents in that case.
HTH,
David C.
On Wed, Aug 2, 2017 at 11:55 AM, Marcus D. Hanwell
wrote:
> On Wed, Aug 2, 2017 at 3:03 AM, Bo Zhou wrote:
>>
>> It depends on the Generator.
>>
>> To the Makefile, the actual type was controlle
irectory "mapping" relative to that file
(which is down in the mapping/config dir)
On Tue, Aug 1, 2017 at 6:47 AM, Florian Lindner wrote:
> Hi,
>
> Am 01.08.2017 um 18:32 schrieb David Cole via CMake:
>> What source files include the header?
>
> It's in
ed in some
conditionally compiled block. (So the typical problem is an extra
dependency, not a missing one...)
Perhaps passing along the includers and the exact lines and context of
being included will give us a hint about why the dependency is not
generated properly in your case.
HTH,
David C.
On
Le 27/07/2017 à 13:08, Eric Noulard a écrit :
2017-07-27 12:28 GMT+02:00 David Demelier <mailto:demelier.da...@gmail.com>>:
Hello,
I'm still trying to find a correct solution to handle user specified
installation paths.
Let's conside
t to do
if paths are absolute, especially on Windows.
What are your thoughts on that, recommandations?
Regards,
--
David Demelier
--
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
You don't have to ask for a specific version. You can just do:
find_package(VTK REQUIRED)
if you don't really care what version is found.
Or if you need >= 7, you can do it like that and then check what
version was actually found, and error out yourself if it is too old.
the Windows system directories inside your bundle. Almost
certainly not what you intended.
Cheers,
David C.
On Wed, Jul 19, 2017 at 9:57 AM, Elvis Stansvik
wrote:
> 2017-07-19 13:42 GMT+02:00 Roman Wüger :
>> The problem with BundleUtilities which Inder is that it doesn't support
We recently converted some software, comprising about 300 projects, to use
OBJECT libraries from SHARED libraries so we could create "conveneince"
libraries that were cominations of some of the 300 projects. Not being
able to use target_link_libraries with thier transitive nature made this
very pai
ks.
On Mon, Jul 10, 2017 at 12:09 PM, Petr Kmoch wrote:
> Hi David.
>
> In your particular case, you don't have build everything twice. Just make
> the SHARED libraries thin wrappers around the OBJECT libraries. Like this:
>
> add_library(obj1 OBJECT a.cpp b.cpp ...)
> a
Currently you can create an OBJECT library using "add_library(
OBJECT ...)" this populates $ which can then
later be used using something like
"target_sources(name PUBLIC $)". I am wondering if
there is some reason that $ can't be populated when
you create a shared or static library, for instance
? (I noticed the forward
slash is being used in the set PATH statements in your build
output...)
HTH,
David C.
On Thu, Jun 22, 2017 at 6:02 AM, James Turner wrote:
> Hi,
>
> We’re trying to debug a failure of a custom build command, in a Cmake project
> using Visual Studio 2015.
ossible to get a release build
directly out of the bootstrap procedure?
Thanks,
David
--
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
is building, then it's possible the
> post-build event run by B that deletes the 'libs' directory also
> deletes some files copied by 'copy_dlls', which means those files will
> not get packaged when 'A_package' invokes `ant release` for the APK
> packag
then I could simplify step 1.
>
> Sorry if this is too much information or if I've not explained things
> clearly, but I wanted to hash out the details because maybe there is a
> better approach. I'm willing to start from scratch on this if it
> improves the design of
Sorry.
Why does this need to run after the build of any individual target?
Why not just say there are two ways to get it to run: build "all" or
explicitly build it after you build the other individual thing you
want?
On Thu, May 18, 2017 at 10:24 AM, Robert Dailey
wrote:
> David
ts" besides the new "last" target.)
So it's not pretty, but it's possible.
HTH,
David C.
On Wed, May 17, 2017 at 11:36 AM, Robert Dailey
wrote:
> I have a custom target that must meet the following requirements:
>
> * It must always run, regardless of what
e batch file.
HTH,
David C.
> On Apr 10, 2017, at 6:44 PM, Robert Dailey wrote:
>
> When I execute a CMake script as a custom command, message() logs are
> not shown in stdout from that script.
>
> Is there a way to make it pipe out messages?
> --
>
> Powered by www.
interface of B to add A as described in
my first email : that will properly pull any transitive include or libs but
that won't make sure that link order is preserved.
Please help.
David
Le 7 avril 2017 15:27:23 GMT+01:00, David Jobet a écrit :
>INTERFACE_LINK_LIBRARIES won't
mported libs ?
With regards,
David
PS : as to why I had to have 2 stages (A_imported and A), this is because I
wanted to add an alias which is not possible on an imported target
Le 7 avril 2017 12:32:52 GMT+01:00, David Jobet a écrit :
>Well not quite.
>I tried that, but my cu
rface B_imported A)
Then linking against B does add B_imported and A, but it does not keep the link
order and might put B_imported before A on the command line.
I'll try with property INTERFACE_LINK_LIBRARIES instead, and will also try to
remove those 2 stages...
With regards
David
Le 6
transitive dependencies for include and link on A. That
would be my prefered choice... But I don't know how to do it.
Is it possible ? How ?
Tx for your help.
David--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMa
quot;--config Release" or "--config Debug"
Also posted on SO.
HTH,
David C.
On Thu, Mar 30, 2017 at 10:10 AM, Christophe Demez
wrote:
> Hi,
>
> I'm currently using one CMakeLists.txt file that will execute an external
> CMakeLists.txt (and dependency).
>
&
, assembled into a ctest -I string to run just
those numbered tests:
#echo $testnums
echo Running command line:
echo ""
echo " ctest -I \"0,0,0,$testnums\" -N"
echo ""
echo Run it without the -N to actually execute the tests...
echo ""
ctest -I &q
ctest.
D
On Fri, Mar 24, 2017 at 3:11 PM, Eric Noulard wrote:
> Hi David,
> Thank you for you for checking the code. Would you think adding such a
> command line option would be acceptable upstream?
>
> Le 24 mars 2017 18:43, "David Cole" a écrit :
>
> This code:
dispatches that in the code just above there.
So. I think you have not much choice other than to propose adding a
new command line argument for such purpose, or wrapping existing ctest
with your own script or program of some sort.
HTH,
David C.
On Fri, Mar 24, 2017 at 6:04 AM, Eric Noulard w
I would like to create a custom target to run UnitTest++ based unit tests that
has builtin default parameters.
For example:
make unit_test verbose=1 xml-output=1 run=test_name suite=suite_name
The actual parameters passed to the unit_test are:
unit_test --verbose --xml-output --run=test_
I would like to create a custom target to run UnitTest++ based unit tests that
has builtin default parameters.
For example:
make unit_test verbose=1 xml-output=1 run=test_name suite=suite_name
The actual parameters passed to the unit_test are:
unit_test --verbose --xml-output --run=test_
he variables like so:
>
> cmake -G Ninja -DCCACHE_DIR=${CCACHE_DIR} ../src
>
> This saves the value in the cache and then it is preserved regardless of what
> environment I have when I do subsequent build steps.
>
>
>
>
> On Fri, Jan 20, 2017 at 7:44 AM, David
1 - 100 of 3201 matches
Mail list logo