On 25 July 2018 at 23:47, Michael Hennebry
wrote:
> Emphasis on curse.
>
> from CMakeLists.txt:
>
> file (GLOB_RECURSE ards ./ArduinoCore/src *.cpp *.c)
> file (GLOB_RECURSE apps ./SensorUnit *.cpp *.c)
Your syntax is wrong. `./ArduinoCore/src`, ` ./SensorUnit`, `*.cpp`,
`*.c` are all being treat
On 24 June 2017 at 05:06, Sean Wayland wrote:
> Hi all,
> I am having trouble getting an application to build.
> I keep getting this error "cannot find source file"
>
>
> /Users/seanwayland/Desktop/CATSMAT-masterfri/catsmat/catsmat/Analysis/src/*.cpp
>
> This is the first folder containing sources
On 5 May 2017 at 19:45, Konstantin Tokarev wrote:
> Hello,
>
> Is there any clear way to build specific target in "Debug" mode with flags
> that it would have in "Release"?
>
> In particular, build this specific target without effect of
> CMAKE_CXX_FLAGS_DEBUG and CMAKE_C_FLAGS_DEBUG, while pres
Hi,
I recently added support to a project to build its API documentation [1].
The documentation is generated by doxygen.
I used `add_custom_command()` to run doxygen and I use `BYPRODUCTS` to
specify the output directory that will be generated by doxygen in the
hope that this would tell ninja to
Hi,
On 13 April 2017 at 01:35, mike lojkovic wrote:
> I have a script I'm using to figure out which headers should be in my
> precompiled header. It requires the clang -H flag passed to work. I'm
> able to get the output on the console without issue, but can't figure
> out how to just pass clang'
> Where Am I going wrong ?
> Can anyone please help me out ?
You don't link against fftw which is why you get linking errors. The
`${fftw}` variable is empty.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware of
On 2 March 2017 at 12:07, aishwarya selvaraj
wrote:
> Hi all ,
> I was trying to build my .cpp file in windows in Windows platform (windows
> 10) using cmake .
> My .cpp file makes use of two external libraries 1)armadillo 2)libsnd file.
> I have written a corresponding cmakelist.txt to compile an
Hi,
On 16 February 2017 at 09:06, wrote:
> Hello,
>
> My question is related to CMAKE_*_FLAGS.
> I've got a project under linux fedora 24 and, in release mode, this project
> compiles with the -O2 flag.
> But when I switched to other platform (ubuntu, fedora 16 - I now this one is
> quite old
> What's weirder (and I forgot to mention) is that if I just build the project
> normally outside of my regression testing script (ie. "make -j5"), I don't
> get the jobserver warning.
The reason for this error message from make is given at [1].
I've seen something like this before when my build
> I was also doubting about libstdc++ versions, is there maybe a way of asking
> Cmake to statistically include it in the built library?
I assume you mean statically. If so then you could try invoking cmake
like this on the command line.
```
mkdir new_build_dir
cd new_build_dir
CXXFLAGS="-static-
On 23 Dec 2016 7:58 pm, "Lev" wrote:
Hi list,
I have this:
FIND_PACKAGE(PythonInterp)
and cmake finds this:
-- Found PythonInterp: /usr/bin/python (found version "2.7.9")
However, 3.4 is also installed. How can I specify to find 3.4?
If I say:
set(Python_ADDITIONAL_VERSIONS 3.4)
FIND_PACK
Hi Aishwarya,
On 21 December 2016 at 11:51, aishwarya selvaraj
wrote:
> Hi Everyone,
> Myself Aishwarya .I wanted to make use of Cmake , but I'm really new to this
> and doesn't have a clear idea about it.
>
> 1) My Goal :
> I'm using Praat a speech Processing Software to create plug - in for my
On 5 December 2016 at 14:05, Brad King wrote:
> On 12/03/2016 06:52 AM, Dan Liew wrote:
>> There was a post about this 10 years ago [1], has anything changed since
>> then?
>
> No. From my response back then:
>
>>> The "clean" target is not a first c
Hi,
As part of a project I work on we use CMake's `ExternalProject()` to
build a set of runtime libraries that the project needs via a second
build system (Makefile based) that knows how to build the runtime
libraries. The code (which is full of hacks... sorry) is at [1].
What I want to do is whe
> What would be the suggested way to handle this?
Couldn't you build the examples using CMake's ``ExternalProject``
module [1] and have that build after the main project has finished
building?
[1] https://cmake.org/cmake/help/v3.5/module/ExternalProject.html
--
Powered by www.kitware.com
Pleas
Hi,
On 28 March 2016 at 15:05, Brad King wrote:
> On 03/27/2016 06:11 AM, Dan Liew wrote:
>> OUTPUT does not accept generator expressions, why?
>
> It hasn't been implemented. At least at one time it would have been
> very hard to implement. I'm not sure now becau
Hi,
I tried writing a add_custom_command statement that will output the
generated file into the same directory as another target
```
set(OUTPUT_NAME "$/MyThing.dll")
add_custom_command(OUTPUT "${OUTPUT_NAME}"
COMMAND "csc.exe" "/output:$" "MySource.cs"
)
```
This doesn't work. CMake emits thi
On 26 March 2016 at 09:30, Dan Liew wrote:
> On 26 March 2016 at 01:15, Mike Lui wrote:
>> When I use tmux and set my TERM to either 'tmux' or 'tmux-256color', I don't
>> get colorized output of from cmake generated Makefiles.
>
> My TERM is set to
On 26 March 2016 at 01:15, Mike Lui wrote:
> When I use tmux and set my TERM to either 'tmux' or 'tmux-256color', I don't
> get colorized output of from cmake generated Makefiles.
My TERM is set to "xterm-256color" and with that coloured output when
running ``make`` in Tmux works fine for me.
I'
> -- check which cl.exe is used:
> $which cl
> D:\CL\cl.EXE
>
> -- trying to build:
> $cmake -G "Ninja" -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang ..
If your goal is use your renamed clang-cl (cl.exe) then why are you
telling CMake to use to use clang.exe ?
You can clearly see if
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 &q
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,
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 PROPERTY LINK_FLAGS "-static")
then the flags that end up being passed to the compiler during linking
are like th
> I fail to see why that should not work. Producing LLVM bitcode from
> C++ with Clang is just adding -emit-llvm flag, right? So, why can't
> the SuperBuild configure the child build to use Clang and this flag?
> And Bob's your uncle...
Hmm, to be honest I hadn't tried. It works better than expect
>> There is an alternative which I suggested in the post. Have CMake
>> determine the dependencies of the files passed to ``IMPLICIT_DEPENDS``
>> at configure time and spit that into the build files of the generator
>> (that would work for any generator). Then have any changes made to the
>> files
> For other generators that are Makefile or Ninja based I guess that
> approach wouldn't work.
Sorry that should read
For other generators that **aren't** Makefile or Ninja based I guess
that approach wouldn't work.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMak
On 30 November 2015 at 18:35, Brad King wrote:
> On 11/30/2015 01:32 PM, Dan Liew wrote:
>> It works but only for makefile generators... That's an annoying
>> limitation. I'll file a feature request to get this implemented for
>> other generators.
>
> It ha
Hi,
On 30 November 2015 at 18:03, Dan Liew wrote:
> Hi,
>
> On 30 November 2015 at 08:09, Petr Kmoch wrote:
>> Hi Dan,
>>
>> you could look into the IMPLICIT_DEPENDS argument of add_custom_command:
>> https://cmake.org/cmake/help/latest/command/add_custom_comma
Hi,
On 30 November 2015 at 08:09, Petr Kmoch wrote:
> Hi Dan,
>
> you could look into the IMPLICIT_DEPENDS argument of add_custom_command:
> https://cmake.org/cmake/help/latest/command/add_custom_command.html
>
> I don't have direct experience with it, but it looks like it could do what
> you're
Hi Michael,
> Not going into detail as I'm typing on the phone, but this really sounds
> like a case where a "SuperBuild"
> (http://www.kitware.com/media/html/BuildingExternalProjectsWithCMake2.8.html)
> can help you to simplify things a lot.
Thanks for the suggestion but this certainly is not a
Hi,
# TL;DR
I need a way of determining the header file dependencies of a source
file and inform CMake about them. CMake doesn't do this automatically
because I'm using custom commands for the compilation step so CMake
doesn't do it's usual magic of automatically inferring source file
header depe
Hi,
> - If not, what is the best/official way to get exact control over the compiler
> and linker options used?
I had to do something similar recently where I didn't want
``-DNDEBUG`` to be in any of the configurations.
I used ``CMAKE_USER_MAKE_RULES_OVERRIDE `` to set the path to file
contain
>> I haven't seen that documented anywhere. IMHO this
>> behavior is counter-intuitive, in general I expect the scope of a
>> target to not depend on the cmake command I am trying to use.
>
>
> I think it is sensible that the definition of a target is scoped to one
> single directory.
> Where the
On 4 August 2015 at 14:32, Iosif Neitzke wrote:
> And:
>
> "A target created in the same directory (CMakeLists.txt file) that
> specifies any output of the custom command as a source file is given a
> rule to generate the file using the command at build time."
>
> http://www.cmake.org/cmake/help/v
On 4 August 2015 at 14:20, Iosif Neitzke wrote:
> "Dependencies listed with the DEPENDS argument may reference files and
> outputs of custom commands created with add_custom_command() in the
> same directory (CMakeLists.txt file)."
>
> http://www.cmake.org/cmake/help/v2.8.8/cmake.html#command:add_
For reference I've opened up a bug report
http://www.cmake.org/Bug/view.php?id=15681
--
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
> foolib is defined in this CMakeLists.txt:
> https://github.com/delcypher/cmake_add_custom_command_bug/blob/master/lib/CMakeLists.txt
>
> That is the (only) context in which you can extend the definition of the
> target with custom commands.
Since when? I haven't seen that documented anywhere. IM
executable links against it and also it is
possible to read properties of the target.
Seems like there's some sort of weird scope issue going on here.
Thoughts?
[1] https://github.com/delcypher/cmake_add_custom_command_bug
[2]
https://github.com/delcypher/cmake_add_custom_command_bug/blob/
Hi,
On 18 June 2015 at 12:16, Robert Dailey wrote:
> On Thu, Jun 18, 2015 at 12:02 PM, Dan Liew wrote:
>>> Can you explain what you mean by "strong" and "weak" symbols?
>>
>>
>> Google is your friend
>>
>> https://en.wikipedia
> Can you explain what you mean by "strong" and "weak" symbols?
Google is your friend
https://en.wikipedia.org/wiki/Weak_symbol
http://stackoverflow.com/questions/2290587/gcc-style-weak-linking-in-visual-studio
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake F
> The reason I'm asking this question is because of how I handle unit
> tests in CMake right now. Instead of just defining an executable
> target for the test and then adding a link dependency on the library
> containing the class or set of classes to be tested, I am manually
> pulling in the CPP a
> This is the approach that the LLVM project uses which is very simple
> and very clean (take a look at the sources). This also works very well
> for installing your header files, the contents of ${CMAKE_SOURCE_DIR}
> just need to be copied into /usr/include .
Oops I meant to say the contents of
On 17 June 2015 at 12:28, Robert Dailey wrote:
> Is there a way to only take (recursively) the include directiories from
> a target or set of targets? I know that include directories propagate
> when passing targets to target_link_libraries(), but I do not want to
> link the libs; I only want the
Hi,
On 21 May 2015 at 23:00, wrote:
> Hello,
>
> I am trying to compile a code written in C, but using an external library
> that contains C++ functions. I am on a Cray system and everything works if I
> manually link with the cray CC wrapper. When I change the linker language
> with this comman
Hi,
I'm not sure if this is actually a bug but I've been relying on the
OBJECT library[1] feature as a convenient way of having source code in
multiple directories be put into a shared library. I now have a need
to hide the symbols in my libraries but I've found that using OBJECT
libraries means t
45 matches
Mail list logo
