If you want to add support to your specific compiler, you could add or extend
another Fujitsu-DetermineCompiler.cmake
file and append your CMAKE_MODULE_PATH in order to CMake to find it. You
probably also need to adjust
*Fujitsu-CXX.cmake, Fujitsu-CXX-FeatureTests.cmake and so on.
I gave a talk
<https://github.com/conan-io/conan/issues/4467>
--
Kai Wolf
Kai Wolf - SW Consulting
www.kai-wolf.me <http://kai-wolf.me/>
XING <https://www.xing.com/profile/Kai_Wolf14> · LinkedIn
<https://www.linkedin.com/in/kw0lf/> · GitHub <https://github.com/NewProggie>
> Am
--
Kai Wolf
Kai Wolf - SW Consulting
www.kai-wolf.me <http://kai-wolf.me/>
XING <https://www.xing.com/profile/Kai_Wolf14> · LinkedIn
<https://www.linkedin.com/in/kw0lf/> · GitHub <https://github.com/NewProggie>
> Am 19.02.2019 um 11:56 schrieb Craig Scott :
>
>
>
You can ask a CMake build target for its properties using get_target_property().
For instance, to retrieve the linker flags for a given target foo, you’d write:
get_target_prooperty(foo_linker_flags foo LINK_FLAGS)
See [1] for a list of valid parameters.
Greetings,
Kai
[1]
https://cmake.o
The CMAKE_BUILD_TYPE variable only makes sense for single-configuration
generators (such as Makefile or Ninja) and is not used for IDE type generators.
You should rather look for CMAKE_CONFIGURATION_TYPES as well as
CMAKE_CFG_INTDIR.
Greetings,
Kai
http://kai-wolf.me
http://effective-cmake.com
They (Kitware) typically write custom .cmake files to test the function/macro
under test coupled together with a CMakeLists.txt file and/or a small C/C++
implementation file. Look here [1] for some examples, for instance
CMake/Tests/MacroTest.
Greetings,
Kai
http://kai-wolf.me
http://effectiv
You probably need to manually add a dependency from your ExternalProject to
your target that needs the libraries.
For instance
ExternalProject_Add(fetch_win32_libs ...)
add_library(your_other_target ...)
add_dependencies(your_other_target fetch_win32_libs)
Greetings
Kai Wolf
http
r, it seems that even though the tests are indeed not executed when
running CTest, they're also not put into the XML file, for instance with
. Is this behaviour expected or am I missing
something?
Thanks in advance
Kai Wolf
http://kai-wolf.me/
kai.w...@gmail.com
--
Powered by www.kitware.c
he case, I will submit a patch for it right away. I just want
to make sure, I’m not misunderstanding something here?
Greetings,
Kai Wolf
<http://kai-wolf.me/> <http://kai-wolf.me/>
<http://kai-wolf.me/>http://kai-wolf.me/ <http://kai-wolf.me/>
[1]
https://cmake
tware project. So you might want to reconsider a more cleaner layout.
For inspiration you may have a look at the CMake configuration of the
OpenChemistry project [1].
Greetings
[1] https://github.com/OpenChemistry/openchemistry
Kai Wolf
http://kai-wolf.me/
kai.w...@gmail.com
2018-03-05 11:59 GMT+
scale quite well and managing a large set of
(external) thirdparty dependencies is usually not as bad as it might look.
Greetings,
Kai Wolf
<http://kai-wolf.me/> <http://kai-wolf.me/> <http://kai-wolf.me/>
<http://kai-wolf.me/> http://kai-wolf.me/
2018-02-20 15:41 GMT+01:00 Bo
g CMake in a correct
and scalabale manner.
As a shameless self-plug: I am currently writing a book[1] on exact this
topic and really hope, I'll be able to release it by summer 2018 :-(
Greetings,
Kai
[1] http://effective-cmake.com/
<https://github.com/NewProggie>
2018-02-20 14:
I've fixed some (mentioned) issues already and opened up a PR on
GitHub. You might want to check that out, otherwise I'll just delete
my PR.
2018-01-22 22:20 GMT+01:00 Alexander Neundorf :
> On 2018 M01 22, Mon 15:16:50 CET Sik wrote:
>> Hello CMake users and devs,
>>
>> In openmeeg we are review
Hi,
I need to integrate an externally built (shared) library as a logical
build target into my CMake configuration which consists of several
shared library files (dlls/dylibs).
Usually I'd do the following:
find_path(MyLib_INCLUDE_DIR mylib.h HINTS ${MyLib_PATH}/include)
find_library(MyLi
Hi all,
a common approach for dealing with larger dependencies in a project is using a
superbuild approach, where all dependencies get downloaded in a separate
repository using ExternalProject_Add() and the actual project is included as a
sub repository (e.g. using git submodules) and also buil
ded a few directories to the dirs parameter of
fixup_bundle, but fixup_bundle doesn't seem to be pulling it in.
-- Analyzing
app='/Users/wolf/wnl/kicad/kicadmacbuilder/silly/bin/kicad.app/Contents/MacOS/kicad'
-- bundle='/Users/wolf/wnl/kicad/kicadmacbuilder/silly/bin/k
On , tonka tonka wrote:
> I have a little problem with files which has to be UTF 16 instead of UTF 8,
> f.e. Visual studios .rc files. They must be utf16 and git detect it as bin
> files.
> So my question is: how do you handle these files?
> My rc files has to be generated with configure_file, so m
Hi all,
I'm trying to setup OBJECT library for the first time and I've run into
problem that include directories are not transient. Let me illustrate:
add_library(foo-object OBJECT src/cache.cpp)
target_include_directories(foo-object PUBLIC include)
add_library(foo SHARED
Hello,
I'm using CMake 3.2.2 on Solaris 10 x86. I've built a toolchain to
cross compile for SPARC, which is working fine for software with GNU
autotools.
But now I'm trying to compile Synergy, which is based on CMake, and I
have lots of troubles with double declarations:
[sepp@synergy /home/sepp/
If this gets looked at, maybe we can add my Linux FindPythonLibs
improvements at the same time? ;)
http://cmake.3232098.n2.nabble.com/FindPythonLibs-Bug-0013794-fix-td7584055.html
Adam Wolf
On Fri, May 31, 2013 at 11:54 AM, Jeremy Carter wrote:
> Hi,
>
> It has been established
ther other system that has newer libraries installed than
the default interpreter.
This appears to fix Bug #0013794.
http://public.kitware.com/Bug/view.php?id=13794
I have attached the patch as a file, but I can also do a pull request
or any other requested code submission process.
Adam Wolf
Wayne
CMake only caches this kind of information in the CMakeCache.txt file
in the build tree. You might want to take a look at the -C option of
CMake. Alternatively, you can also try to play around with the
CMAKE_SYSTEM_PREFIX and CMAKE_SYSTEM_*_PATH variables as documented the
man-page.
Michael
Hi
Hi,
is there a way to disable the global caching mechanism of cmake?
I mean the caching where cmake stores where a certain
software package can be /was found once successfully built.
I have a closed standalone build (suitable for e.g. a buildserver and
automatic testing) and want to make sure
On 28.09.2011 17:58, Jean-Christophe Fillion-Robin wrote:
Hi Thomas,
You will find below few points that should help you to address your issues:
1) CTK build system can be build with the option CTK_SUPERBUILD set to
OFF, in that case the project will be built as a "regular" cmake project.
2) Y
Hi there,
I have some serious trouble to get a makefile running, comprising of
MITK, VTK, ITK, CTK, Log4Qt, DCMTK, GDCM, etc...
Because most of the makefiles have some imperfections regarding being
built under windows and x64 with the project environment of Visual
Studio 2008, we use direct
Addition:
if i try to fake the contents of the CTK use file, like
set_found true
usefile_included 1
find_package still tries to include the CTKConfig.cmake. I always thougt
if the Find-variable is set to true find_package just assumes that
everything went fine and continues (silent mode). Or is
Hello all,
i think i stumbled upon something that keeps me occupied for quite some
time now:
I have a quite large CMake based project, wich is intended to generate a
Visual Studo 2008 solution. The problem is, that I use mixed internal
and external projects, which depend on each other, like VTK,
On 15.09.2011 18:30, David Cole wrote:
> Luigi is correct:
>
> To use an existing source directory (just use the source in its place
> without any copy operations), simply say:
>
> DOWNLOAD_COMMAND ""
> SOURCE_DIR ${Log4Qt_SOURCE_DIR}
>
> The default behavior of copying the source tree when
On 15.09.2011 17:48, Luigi Calori wrote:
> Did you tried specifying SOURCE_DIR without any URL and / or
> DOWNLOAD_COMMAND ""
> UPDATE_COMMAND ""
>
> Not sure this is correct but for my case seems to work
>
> HTH
mhm,
i swapped URL for the SOURCE_DIR, yes, and there is also no
DOWNLOAD_COMMAND
small correction:
i DO indeed want to have them compiled, but by taking the sources from
the original location, not copying them to another directory and then
have them compiled..
Regards,
Thomas
___
Powered by www.kitware.com
Visit other Kitware open-
Hello,
i am wondering if it is possible to have an external project building
from local sources, *without* attemtping to download (in that case,
copy) to a specific location.
My sources of the externals are already in my repository, i do not want
to have them compiled.
I looked around for some w
follow up:
with an additional:
>>>
set( QT_INCLUDE_DIR $ENV{QTDIR}/include )
set( QT_HEADERS_DIR $ENV{QTDIR}/include )
set( QT_LIBRARY_DIR $ENV{QTDIR}/lib )
set( QT_BINARY_DIR $ENV{QTDIR}/bin )
set( QT_LIBRARY_DIR_TMP
>
> Sure, the find_program() call in FindQt4.cmake has registry keys first, but
> if
> you look at the docs for find_program(), all of those paths are looked at
> last.
>
> The CMAKE_PREFIX_PATH and PATH variables have a higher priority, and you can
> set those to control which Qt you want fo
Dear all,
i want my build system for our project (several heavy libraries) to
build both 32 and 64 bit windows versions. Everything is integrated and
working, except one thing:
QT 4.7 is used, but installed independently (standard library, not
committed to repository). So everyone has it installe
On 8/13/10 1:12 PM, Martin Costabel wrote:
> Chris Wolf wrote:
> []
>> Have you actually built shared libraries on MacOS with CMake? If so,
>> maybe an example
>> of yours would be more helpful.
>
> The following settings work for me
On 8/15/10 12:43 PM, Michael Wild wrote:
>
> On 15. Aug, 2010, at 13:22 , Chris Wolf wrote:
>
>>
>>
>>
>>>>
>>>> No, the two mechanisms are fundamentally different.
>>>>
>>>> On Linux the RPATH is a search pat
On 8/14/10 4:01 PM, Michael Wild wrote:
>
> On 14. Aug, 2010, at 18:26 , Chris Wolf wrote:
>
>>
>>
>> On 8/14/10 10:31 AM, Michael Wild wrote:
>>>
>>> On 14. Aug, 2010, at 15:13 , Chris Wolf wrote:
>>>
>>>>
>>>>
&g
On 8/14/10 10:31 AM, Michael Wild wrote:
>
> On 14. Aug, 2010, at 15:13 , Chris Wolf wrote:
>
>>
>>
>> On 8/14/10 3:35 AM, Michael Wild wrote:
>>>
>>> On 13. Aug, 2010, at 20:58 , Michael Wild wrote:
>>> [...]
>>>>
>>&g
On 8/14/10 3:35 AM, Michael Wild wrote:
>
> On 13. Aug, 2010, at 20:58 , Michael Wild wrote:
> [...]
>>
>> Sure, http://repo.or.cz/w/freefoam.git/shortlog/refs/heads/pu, but it's
>> pretty complex...
>>
>> Michael
>
> Attached is a tiny project which works for me on both Linux and Mac.
>
> Mi
On 8/13/10 11:21 AM, Michael Wild wrote:
>
> On 13. Aug, 2010, at 16:32 , Chris Wolf wrote:
>
>>
>>
>> On 8/13/10 10:23 AM, Chris Wolf wrote:
>>>
>>>
>>> On 8/13/10 9:29 AM, Michael Wild wrote:
>>>>
>>>> On 13. Aug,
On 8/13/10 10:23 AM, Chris Wolf wrote:
>
>
> On 8/13/10 9:29 AM, Michael Wild wrote:
>>
>> On 13. Aug, 2010, at 15:25 , Chris Wolf wrote:
>>
>>>
>>> I have confirmed that the RPATH handling, as documented here:
>>>
>>> http://www.c
On 8/13/10 9:29 AM, Michael Wild wrote:
>
> On 13. Aug, 2010, at 15:25 , Chris Wolf wrote:
>
>>
>> I have confirmed that the RPATH handling, as documented here:
>>
>> http://www.cmake.org/Wiki/CMake_RPATH_handling
>>
>> Is only accurate for the Li
I have confirmed that the RPATH handling, as documented here:
http://www.cmake.org/Wiki/CMake_RPATH_handling
Is only accurate for the Linux case and *NOT* for MacOS.
Here is the summary of my findings:
"Default RPATH":
http://www.cmake.org/Wiki/CMake_RPATH_handling#Default_RPATH_settings
li
On 8/13/10 3:47 AM, Michael Wild wrote:
>
> On 12. Aug, 2010, at 22:37 , Chris Wolf wrote:
>
>> I have a project which creates a shared library and a utility which uses this
>> shared library. I would like to be able to run the utility within the build
>> tree and
I have a project which creates a shared library and a utility which uses this
shared library. I would like to be able to run the utility within the build
tree and also from the final install directory. I can do this, it works,
but the path hard-coded path in the executable is always the build tre
On 8/12/10 10:20 AM, Carlos Gonçalves wrote:
> Hi,
>
> I have already looked everywhere possible (so to speak) on how to create a
> Framework + Unix tools as described in [1] but found no examples. So far I
> was able to create a Framework only [2].
>
> I'm trying to add Mac OS X support to G
On 8/12/10 1:30 PM, Óscar Fuentes wrote:
> Michael Wild writes:
>
How to know the compiler arguments set by include_directories,
add_definitions, etc?
CMAKE__FLAGS (with and whitout the uppercase build_type suffix)
doesn't contain anything that was set by the cmake comm
On 8/11/10 4:29 PM, Michael Wild wrote:
>
> On 11. Aug, 2010, at 22:16 , Michael Jackson wrote:
>
>>
>>
>> On Aug 11, 2010, at 3:52 PM, Michael Wild wrote:
>>
>>>
>>> On 11. Aug, 2010, at 21:44 , Erik Lindahl wrote:
>>>
Hi,
Sound technical answers from both David & Clinton - I se
On 8/11/10 5:39 PM, Eric Noulard wrote:
> 2010/8/11 Thawan Kooburat :
>> Hi Eric,
>>
>> I read though this thread and also two bug reports related to this issue.
>>
>> It seems like it will take a while because of CPack design issue. Do
>> you think there will be any workaround or small hack to m
On 8/9/10 2:22 PM, Eric Noulard wrote:
> 2010/8/9 Chris Wolf :
>>
>>
>> On 8/9/10 12:11 PM, Kishore wrote:
>>> On Friday 06 Aug 2010 4:18:36 am Eric Noulard wrote:
>>>> 2010/8/4 Kishore :
>>>>> On Monday 02 Aug 2010 4:59:47 pm Eric Noul
On 8/9/10 12:11 PM, Kishore wrote:
> On Friday 06 Aug 2010 4:18:36 am Eric Noulard wrote:
>> 2010/8/4 Kishore :
>>> On Monday 02 Aug 2010 4:59:47 pm Eric Noulard wrote:
Hi All,
I did add a patch for the "multiple file problem"
http://public.kitware.com/Bug/view.php?id=10736
>>
On 8/7/10 12:13 PM, David Cole wrote:
> On Sat, Aug 7, 2010 at 11:55 AM, Chris Wolf wrote:
>
>>
>>
>> On 8/7/10 11:22 AM, David Cole wrote:
>>> On Sat, Aug 7, 2010 at 11:02 AM, Chris Wolf wrote:
>>>
>>>>
>>>>
>>>
On 8/7/10 11:22 AM, David Cole wrote:
> On Sat, Aug 7, 2010 at 11:02 AM, Chris Wolf wrote:
>
>>
>>
>> On 8/7/10 9:44 AM, David Cole wrote:
>>> On Sat, Aug 7, 2010 at 9:26 AM, Chris Wolf wrote:
>>>
>>>>
>>>>
>>>> On
On 8/7/10 9:44 AM, David Cole wrote:
> On Sat, Aug 7, 2010 at 9:26 AM, Chris Wolf wrote:
>
>>
>>
>> On 8/7/10 7:14 AM, Eric Noulard wrote:
>>> 2010/8/7 Chris Wolf :
>>>> On 8/6/10 8:55 PM, Eric Noulard wrote:
>>>>&
On 8/7/10 9:50 AM, David Cole wrote:
> On Sat, Aug 7, 2010 at 9:44 AM, David Cole wrote:
>
>> On Sat, Aug 7, 2010 at 9:26 AM, Chris Wolf wrote:
>>
>>>
>>>
>>> On 8/7/10 7:14 AM, Eric Noulard wrote:
>>>> 2010/8/7 Chris Wolf :
>>&
On 8/7/10 9:44 AM, David Cole wrote:
> On Sat, Aug 7, 2010 at 9:26 AM, Chris Wolf wrote:
>
>>
>>
>> On 8/7/10 7:14 AM, Eric Noulard wrote:
>>> 2010/8/7 Chris Wolf :
>>>> On 8/6/10 8:55 PM, Eric Noulard wrote:
>>>>&
On 8/7/10 7:14 AM, Eric Noulard wrote:
> 2010/8/7 Chris Wolf :
>> On 8/6/10 8:55 PM, Eric Noulard wrote:
>>>
>>> Did you try the command line?
>>>
>>> cpack -D CPACK_PACKAGING_INSTALL_PREFIX="/opt" -G DEB
>
On 8/6/10 8:55 PM, Eric Noulard wrote:
> 2010/8/6 Chris Wolf :
>> Earlier, I identified a problem with the "PackageMaker" (Apple) packager,
>> and now, I see the same exact problem with the "DEB" (Debian)
>> packager - it keeps prefixing
On 8/6/10 8:43 PM, Eric Noulard wrote:
> 2010/8/6 Chris Wolf :
>> I am trying the ZIP package type and I get the same error on MacOS and Linux:
>>
>> CPack Error: archive_write_header:Filetype not supportedNo such file or
>> directory -25
>> CPack Error: arc
be the case
here) I'm no expert, so I could be missing things, but I think the
behavior should be:
CMAKE_INSTALL_PREFIX - controls "make install", does NOT effect "make package"
CPACK_PACKAGING_INSTALL_PREFIX - controls "make package", has no effect on
"make
On 8/6/10 6:30 PM, David Cole wrote:
> On Fri, Aug 6, 2010 at 5:49 PM, Chris Wolf wrote:
>
>> I'm still unclear what you're suggesting here (quote, below). If
>> I run "make package", doesn't that make target invoke cpack with the
>> cmak
CPackOptions.cmake")
>
>
> See CMake's "CMakeCPack.cmake" and "CMakeCPackOptions.cmake.in" files in the
> top level directory for more CPack magic than you'll be able to absorb on a
> Friday afternoon :-)
>
>
> HTH,
> David
>
>
&
's "CMakeCPack.cmake" and "CMakeCPackOptions.cmake.in" files in the
> top level directory for more CPack magic than you'll be able to absorb on a
> Friday afternoon :-)
>
>
> HTH,
> David
>
>
> On Fri, Aug 6, 2010 at 4:45 PM, Chris Wolf wrot
Earlier, I identified a problem with the "PackageMaker" (Apple) packager,
and now, I see the same exact problem with the "DEB" (Debian)
packager - it keeps prefixing "./usr" to all the paths.
Changing CPACK_PACKAGING_INSTALL_PREFIX doesn't do anything
(even when it's at the top of the file)
This
I am trying the ZIP package type and I get the same error on MacOS and Linux:
CPack Error: archive_write_header:Filetype not supportedNo such file or
directory -25
CPack Error: archive_write_data(): tried to write 16384
write 0
I searched around in case this was a known issue. The Wiki says:
"
On 8/6/10 12:57 PM, Chris Wolf wrote:
>
>
> On 8/6/10 7:22 AM, Eric Noulard wrote:
>> 2010/8/6 Chris Wolf :
>>>
>>> e.g for : install(TARGETS usb LIBRARY DESTINATION lib)
>>>
>>> (where project name is "libusb")
>>>
>>
On 8/6/10 9:46 AM, Bill Hoffman wrote:
> There is one in the Tutorial:
>
> http://www.cmake.org/cmake/help/cmake_tutorial.html
>
> -Bill
I did look at that when I first started, but this tutorial
does not install the library (just the executable and headers).
Right now, I'm focused on a proje
On 8/6/10 7:22 AM, Eric Noulard wrote:
> 2010/8/6 Chris Wolf :
>>
>> e.g for : install(TARGETS usb LIBRARY DESTINATION lib)
>>
>> (where project name is "libusb")
>>
>> The CPack-generated TGZ archive will contain:
>> libusb-0.1.1-Darwin/li
On 8/5/10 6:22 PM, Eric Noulard wrote:
> 2010/8/6 Chris Wolf :
>>
>> Unfortunately, at first, I din't see how your example is different from
>> the parts of my CMakeList.txt I sent in my last post.
>>
>> Then I noticed that your "install(TAR
On 8/5/10 5:15 PM, Olaf van der Spek wrote:
> On Thu, Aug 5, 2010 at 11:06 PM, Chris Wolf wrote:
>> I'm looking all over for an end-to-end basic example of using CPack
>> to create a package with a single shared library target. It can
>> even
y basic) example would be
helpful.
Thanks,
Chris Wolf
P.S. Here is my current CMakeList.txt:
cmake_minimum_required(VERSION 2.8)
project(libusb)
set(NAME libusb)
include(CheckIncludeFiles)
include(CPack)
set(CPACK_PACKAGE_EXECUTABLES "libusb.dylib" "libusb-1.0.8&q
.app/Contents/share/cmake-2.8/Modules"
Also, I think the man pages still need to be copied, or symlinked,
or the MANPATH updated.
Thanks,
Chris Wolf
On 8/5/10 3:18 PM, Ryan Pavlik wrote:
> How are you running cmake? I've used the installer from the web site on my
> mac, and it wor
quot;postflight" script should have also symlinked, or copied,
the "doc", "man" and "share" directory hierarchies content also.
I can do this manually myself, but I just wanted to point out the
issue with the MacOS installer package for cmake-2.8.2.
Thanks,
C
). Does this mean that currently all DartClients on Windows
compile as "Release" or is there a possibility to override this somehow?
Thanks,
Ivo
--
--
Dr. Ivo Wolf, Dipl.-Phys. Phone: (+49) 6221/42-2327
74 matches
Mail list logo
