-develop...@cmake.org) or
submit a bug.
--
Best Regards,
Alexander
On Sat, 5 Oct 2019 at 10:33, Craig Scott wrote:
>
>
> On Sat, Oct 5, 2019 at 12:59 AM Alexander
> wrote:
>
>> Dear Cristian,
>>
>> It would better for me not modifying CMakeFiles.txt, because as
? What is the
logic behind this behavior? Why not simply allow /DEF in
CMAKE_SHARED_LINKER_FLAGS and not cut it?
--
Best Regards,
Alexander
On Fri, 4 Oct 2019 at 16:54, Cristian Adam wrote:
> Hi,
>
> You should simply add the my_defs.def file as a source files to
> add_library/ad
is"
so that they are not modified.
Any workaround is highly appreciated (better command-line, because we build
3rd party software and it would not really fine to change CMakeLists.txt)
--
Best Regards,
Alexander Samoilov
Build & Integration Engineer
Compart AG, 71034 Böblingen Germany
--
On Mittwoch, 11. September 2019 21:22:04 CEST Kyle Edwards via CMake wrote:
> 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
On 2019 M03 28, Thu 18:22:03 CET Scott Bloom wrote:
> Just a note, for google later on… 😊
>
> The default appears to have the variable unset, so it doesn’t show up in the
> list of variables in ccmake or the cmake-gui.
> I also added it to my system before any INSTALL command was called. I don’
On 2019 M02 12, Tue 08:02:43 CET Starka Tomáš wrote:
> tldr;
> It would be wonderful to have function or signature for
> target_link_libraries tha would link only to a targets. Did I overlook
> something?
>
> like target_link_libraries(name [PUBLIC...] TARGETS myFavouriteLib ...
> QUIET/VERBOSE)
>
On 2019 M01 13, Sun 09:43:03 CET Lectem wrote:
> Hi,
>
> Is there a way to list all the packages (both config files and find-modules)
> that find_package could find ? Could we even imagine this would also permit
> to list the variables and targets created in it ? I think that would be a
> very hel
On 2019 M01 5, Sat 08:06:31 CET Federico Milano wrote:
> Hi. When packaging my application, I'm using install (FILES...) to copy
> some third party executables to my binary folder.
>
> 1. I do not know if I'm doing it right or if I should use install
> (PROGRAMS...)
> 2. Some of the binaries have
On 2018 M11 5, Mon 13:20:32 CET Robert Maynard wrote:
> Yes, you can do that. I don't know if there is an easier way than the
> following:
you could have a look at the following variables:
CMAKE_STATIC_LIBRARY_PREFIX
CMAKE_STATIC_LIBRARY_SUFFIX
CMAKE_SHARED_LIBRARY_PREFIX
CMAKE_SHARED_LIBRARY_SUF
On 2018 M10 28, Sun 18:46:24 CET you wrote:
> El 28/10/18 a las 18:32, Alexander Neundorf escribió:
> > well, then you do have some RPATH/RUNPATH somewhere ;-). As you say
> > probably in the libraries.
> > ld.so.conf could also contains additional search directories, but I
On 2018 M10 28, Sun 14:20:40 CET you wrote:
> El 28/10/18 a las 13:59, Alexander Neundorf escribió:
> > On 2018 M10 28, Sun 10:19:58 CET Gonzalo Garramuño wrote:
> > ...
> >
> >> 3) Why does running 'readelf -d myexecutable | grep RPATH' returns
> >
On 2018 M10 28, Sun 10:19:58 CET Gonzalo Garramuño wrote:
...
> 3) Why does running 'readelf -d myexecutable | grep RPATH' returns nothing
only grep for "PATH", then you also get the newer RUNPATH entry.
Alex
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake F
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.
> > How do you handle this ?
>
> I just found out I don't.
> Any idea on that one ?
here are some suggestions:
h
Hei hei,
for a standalone build without system libraries I was experimenting
with the ExternalProject module today. My goal is to have some top
level build project which includes several CMake projects and some
external projects without relying on dev libraries installed on the
system (reason are
On 2018 M08 23, Thu 12:50:14 CEST David Jobet wrote:
> Hello,
>
> I'm trying to port an existing project from premake to cmake.
> I'm trying to avoid modifying the source files while doing so.
>
> Right now, we have several libraries (read in different directories) using
> proto files with import
On 2018 M08 6, Mon 21:54:33 CEST Hendrik Sattler wrote:
> Am 6. August 2018 20:27:23 MESZ schrieb Philip Van Hoof
:
> >Hello everyone,
> >
> >I noticed that it sometimes happens that I find a package for a shared
> >object file(s) (or DLLs, on platforms like Windows) that have a build
> >set up us
On 2018 M08 2, Thu 10:01:39 CEST Randy Heiland wrote:
> Hi,
>
> I'd like to figure out how to modify the simple "hello" demo (
> https://cmake.org/examples/) so that the Hello project is a library with an
> accompanying FindHello.cmake and then the Demo project uses that
> information and "find_pa
On 2018 M07 18, Wed 09:49:47 CEST Brian S wrote:
> I currently use cmake/ctest to build and test my software. The software is
> C++/CUDA. During the build step I don't need a GPU but in the test step I
> do. I would like to build the code with cmake on a cluster with many CPUs
> and then run the te
On 2018 M07 7, Sat 19:09:18 CEST Martin Weber wrote:
> Hi all,
>
> FYI, according to this [1], those generators do no longer work with the new
> core build introduced in CDT 9.5.
>
> Martin
>
> [1] http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg33066.html
do you know whether the new build syst
Hi Isaiah,
that's correct and basically the reason why I need to compile two different
modules for python2 and python3. In addition, I assume that the python
minor version does not change; with that, I get some help from the package
manager.
Cheers,
Alexander Bürger
MET Norway
--
Power
Hello Juan,
but there are also two boost-python versions required, one for python2 and
one for python3. I think it is not a good idea to reimplement the FindBoost
logic.
Cheers,
Alexander Bürger
MET Norway
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
Hi,
thanks, Petr, for the hint. I was not aware of the possibility to specify a
binary directory, and I will investigate how that works.
Cheers,
Alexander Bürger
MET Norway
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki
COMPONENTS python # or python3)
with different python versions is to use one CMakeLists.txt per python
version, each in a subdirectory, and with almost equal contents. I would
appreciate suggestions for a better approach, with less duplication.
Best regards,
Alexander Bürger
MET Norway
hello, world!sorry for my english:I have several libraries that come to me in archives compiled with their header files. for unpacking and configuring the primary method I use externalproject_add(). next, I need to install them and create configuration scripts for further importing into several pro
Hi,
I stumbled upon a problem with protobuf files, I attached a testcase.
There is a MyBase.proto, which is "imported" by Complex.proto.
If MyBase.proto is modified, protoc is run again in MyBase.proto, but not on
Complex.proto, although it should.
You can have a look at the attached example.
Th
On 2018 M04 5, Thu 15:15:21 CEST Juan E. Sanchez wrote:
> The example I just sent was for building in centos 6, because 5 is gone.
not really gone, it's still in vault.centos.org :-)
https://hub.docker.com/r/aneundorf/centos5-build-base/~/dockerfile/
Alex
--
Powered by www.kitware.com
Please
On 2018 M04 5, Thu 12:50:04 CEST Ben Sferrazza wrote:
>
> Were you able to actually build the newer versions of Cmake that require
> c++11 on Centos 5?
I didn't try that.
Alex
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/
On 2018 M04 5, Thu 21:24:40 CEST Alexander Neundorf wrote:
> On 2018 M04 5, Thu 16:15:17 CEST suzuki toshiya wrote:
> > Dear Eric,
> >
> > # if anybody think "how C++11 environment should be prepared
> > # on legacy GNU/Linux" is off-topic and should be discu
On 2018 M04 5, Thu 16:15:17 CEST suzuki toshiya wrote:
> Dear Eric,
>
> # if anybody think "how C++11 environment should be prepared
> # on legacy GNU/Linux" is off-topic and should be discussed
> # in off-list, please let me know. I will do so.
>
> Eric Wing wrote:
> > Thanks for the responses.
On 2018 M04 3, Tue 16:01:58 CEST jeandet wrote:
> Hi all,
>
> Reading the documentation I can see:
> https://cmake.org/cmake/help/v3.11/manual/cmake.1.html?highlight=find%2
> 0package#find-package-tool-mode id="-x-evo-selection-start-marker">
> "
> Note
>
> This mode is not well-supported due to
On 2018 M03 20, Tue 21:14:30 CET Mateusz Loskot wrote:
...
> Why I can not write:
>
> target_use(app Boost::system Boost::filesystem)
>
> or
>
> target_use_targets(app Boost::system Boost::filesystem)
>
> and, actually read and understand what I'm doing?
>
> (If you're now typing "why don't yo
shown. So, is there any way to disable it?
So far I've only found CPACK_MONOLITHIC_INSTALL, but it causes
all the components to install.
Thanks,
Alexander
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware
't think it's a good solution for various reasons.
Thanks,
Alexander
--
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 2018 M01 22, Mon 15:16:50 CET Sik wrote:
> Hello CMake users and devs,
>
> In openmeeg we are reviewing our MKL package finder to make it more
> maintainable for ourselves and others who had adopted our solution.
> Therefore I'm writing you requesting comments and feedback so that is
> useful f
On 2018 M01 4, Thu 10:06:26 CET Franck Houssen wrote:
...
> ...
> target_include_directories(main PUBLIC ${PETSc_INCLUDE_DIRS})
> foreach(lib ${PETSc_LDFLAGS})
> target_link_libraries(main PUBLIC ${lib})
> message("target_link_libraries - lib is ${lib}")
> endforeach(lib)
>
> foreach(dir ${PET
On 2018 M01 4, Thu 05:09:54 CET Dave Milter wrote:
> Hello,
>
> If there is some libfoo that I want to use in my project,
> and this libfoo has it's own CMakeLists.txt I have 3 options to deal
> with such external dependency:
>
> a) Treat it like every other external dependency and write cmake co
On 2018 M01 3, Wed 10:08:09 CET Franck Houssen wrote:
> Hello,
>
> How to ask cmake to add a library path (coming from pc file) to rpath ?
>
> I checked this https://cmake.org/Wiki/CMake_RPATH_handling, but still not
> working. Can somebody help ?
> >> more main.cpp
>
> #include
>
> int main(i
On 2017 M09 21, Thu 07:18:46 CEST David Cole via CMake wrote:
> By manually deleting (or touching) the stamp file associated with the
> earliest step you need to re-run.
>
> ExternalProject is not for auto-detecting changes to stuff and
> minimally re-running build steps. It's for static stuff tha
On 2017 M10 1, Sun 12:38:43 CEST David Cole via CMake wrote:
> No, I was already promptly corrected by Brad, too. I was not
> accounting for the fact that the other find_* calls used inside of
> find modules also use CMAKE_PREFIX_PATH. I was thinking of its use to
> find a project's config file fro
On 2017 M08 10, Thu 17:15:00 CEST Robert Maynard wrote:
> > Which leads to a question I have for the Kitware types here. What
>
> should I suggest to my Linux enterprise distribution users? Can they
> simply download and use the latest Linux binary version of CMake that
> is distributed by Kitwar
On 2017 M09 13, Wed 09:50:48 CEST Patrick Welche wrote:
> I think I am confused by the following:
>
> 1) CMAKE_PREFIX_PATH;
>
> Problematic (scribus) CMakeLists.txt:
>
>set(CMAKE_PREFIX_PATH "${QT_PREFIX}/lib/cmake")
This looks wrong to me.
In general CMAKE_PREFIX_PATH should contain only t
On 2017 M08 29, Tue 11:33:15 CEST David Cole via cmake-developers wrote:
> That's correct:
>
> find modules do what they want, and most do not pay attention to
> CMAKE_PREFIX_PATH.
are you sure ?
As long as NO_DEFAULT_PATH is not used in the find_*() calls, CMAKE_PREFIX_PATH
is used automaticall
On 2017 M08 24, Thu 13:36:45 CEST Robert Dailey wrote:
> So I have a "super build" CMake script that runs a series of
> ExternalProject_Add() functions to execute builds of various third
> party libraries and install them to a path relative to the parent
> project's CMAKE_BINARY_DIR.
>
> Once the
On 2017 M05 27, Sat 15:49:35 CEST biologi spm wrote:
> Hi CMake developers,
>
> When both Mingw64 GCC and MSVC is available in PATH and run cmake
> -GNinja, cmake always choose GCC. I have to manually remove GCC from
> PATH or type -DCMAKE_IGNORE_PATH= which is very long.
you can set the CC and C
Hi John,
On 2016 M01 19, Tue 07:55:27 CET Biddiscombe, John A. wrote:
> Alex
>
> Thank you for this information. I shall test this out right away.
so, did it work out ?
Alex
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CM
On 2017 M02 3, Fri 20:32:58 CET you wrote:
> FWIW, we've moved to CentOS 6 for the binaries we package and distribute
> for ParaView. It's about the oldest widely deployed Linux distro that's
> still actively supported (EL5 is EOL'd and most deployments have long since
> moved to 6 or 7).
Yes,
On 2017 M02 2, Thu 20:07:29 CET you wrote:
> Hi Gonzalo,
>
> Using the dockcross/manylinux-x64 docker image should allow to build you
> project out-of-the-box.
> It is based on Centos5, include recent gcc, CMake, Git, etc ...
>
> See https://github.com/dockcross/dockcross
>
> In a nutshell,
>
>
Hi all,
we have the following setup: Visual Studio 2013 Professional is installed,
but for compatibility reasons we need to use the Visual Studio 2010
(vc100) compilers. To that end we have Visual Studio 2010 Express
installed (to complicate things, we also need the Windows SDK 7.1 to get
access t
On 2017 M01 26, Thu 18:23:05 CET Gonzalo Garramuño wrote:
> I currently own an Ubuntu Xenial 14.04.1 LTS box in which I do all my
> work.I distribute a binary image viewer. However, recently one of
> my users tried to run the viewer on a CentOS 7 distro and found out that
> that distro libc a
On 2016 M11 29, Tue 14:42:49 CET Robert Bielik wrote:
> Hmm.. using v3.7 the answer is no, i.e. a function declared in a subfolder
> will be available in parent scope. Seems a bit odd, doesn't it ?
this has been discussed here just recently...
Functions and macros are global.
Once they are define
On Wednesday 09 November 2016 09:22:24 Nils Gladitz wrote:
...
> You said you are not forcing your users to upgrade by setting a policy
> to OLD.
> Which implied that not setting the policy to OLD would force your users
> to upgrade ... which it doesn't.
>
> >> In fact all that setting it to OLD d
On Wednesday 09 November 2016 00:47:39 Albrecht Schlosser wrote:
> On 08.11.2016 23:01 Nils Gladitz wrote:
> > On 08.11.2016 20:26, Albrecht Schlosser wrote:
> >> I'm a developer of a public GUI library (FLTK). In this position you
> >> don't know anything about the availability of CMake versions o
ion ‘--param
l1-cache-line-size=64’
gcc: error: unrecognized command line option ‘--param
l2-cache-size=512’
If I only specify one of the flags (with no single/double quotes) gcc accepts
the flag.
Thanks,
Alex
From: CHEVRIER, Marc
Sent: Friday, 12
On Tuesday 12 July 2016 09:00:43 portolan wrote:
> Hello,
>
> I am new to Cmake and I have a pretty strange behaviour: I set my c+++
> project to work with a single CMakefile.txt, and now I am trying to have
> a more proper version with a .txt for each subdirectory
>
> Pretty normal stuff, my sou
On 06/18/2016 01:15 PM, Nils Gladitz wrote:
On 18.06.2016 13:03, Alexander Shukaev wrote:
if(POLICY CMP0011)
cmake_policy(SET CMP0011 NEW)
endif()
if(POLICY CMP0063)
cmake_policy(SET CMP0063 NEW)
endif()
CMakeLists.txt:
include(xxx)
cmake_minimum_required(VERSION 3.1.0)
and it still
On 06/18/2016 12:18 PM, Nils Gladitz wrote:
On 18.06.2016 11:38, Alexander Shukaev wrote:
I did try both variants, after and before
cmake_minimum_required(VERSION)
but the result is the same. The scope is for sure parent to targets.
I don't know what else it could be but this works
On 06/18/2016 11:02 AM, Nils Gladitz wrote:
On 18.06.2016 09:34, Alexander Shukaev wrote:
Hello,
CMake 3.5.2 here. Why explicitly setting the CMP0063 policy to NEW
does not suppress the warning and actually use that new policy? That is
if(POLICY CMP0063)
cmake_policy(SET CMP0063 NEW
NLINES_HIDDEN
For compatibility CMake is not honoring them for this target.
Is this a bug? Thanks in advance.
Regards,
Alexander
--
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
On Monday, April 18, 2016 16:57:52 Nils Rathmann wrote:
> Hi,
> when I setup with the Eclipse CDT4 generator, as described here:
> https://cmake.org/Wiki/Eclipse_CDT4_Generator4
>
> my [Targets] folder contains virtual folders for CMakeRules, Header
> Files, Object Files, Resources and Source File
27;t support OPTIONAL_COMPONENTS which seems only to work
if FIND_PACKAGE_HANDLE_STANDARD_ARGS is called with HANDLE_COMPONENTS passed.
This is not the case and does not work. I guess due to different naming scheme
used for components. AFAICS they have to be e.g. Qt4_QtCore_FOUND, but not
QT_QTCORE_FOU
ere?
Best regards,
Alexander
--
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:
CMake Support: http:/
On Sunday, January 17, 2016 14:01:59 Alexander Neundorf wrote:
> On Sunday, January 17, 2016 13:45:34 Dimitri Kaparis wrote:
> > On Sat, Jan 9, 2016 at 9:16 PM, Alexander Neundorf
> > >
> > wrote:
> > > On Saturday, January 09, 2016 12:27:48 Dimitri
On Thursday, February 11, 2016 13:11:29 Ron wrote:
> Hi,
>
> I am working on a project that requires libevent and libevhtp.
> The latter is cmake managed, my project and libevent are autoconf managed.
>
> (Note that libevhtp depends on libevent, both depend on openssl, which I
> rely
> on the sys
On Wednesday, February 03, 2016 13:08:42 Andrew Bell wrote:
> If my package is installed to a non-standard location, my
> Config.cmake file is currently also installed to the non-standard
> location and can't be found by dependent projects.
>
> I see that there's export(PACKAGE ), but this creates
On Sunday, January 17, 2016 13:45:34 Dimitri Kaparis wrote:
> On Sat, Jan 9, 2016 at 9:16 PM, Alexander Neundorf
> wrote:
> > On Saturday, January 09, 2016 12:27:48 Dimitri Kaparis wrote:
> > > Greetings,
> > >
> > > I'm using the "Code
On Thursday, January 14, 2016 21:51:23 Biddiscombe, John A. wrote:
> Apologies for posting a cdash question question to the cmake list…
>
> CDash plots the run-time of tests, which is very useful indeed, but it would
> be even more useful if one could output a performance related ‘time’ from a
> t
On Saturday, January 09, 2016 12:27:48 Dimitri Kaparis wrote:
> Greetings,
>
> I'm using the "CodeBlocks - Unix Makefiles" generator under linux to create
> a build tree for my project consisting of multiple executables and
> libraries.
> From the command line, I could use make -jN switch from the
On Saturday, November 14, 2015 12:19:11 Nicholas Braden wrote:
> Instead of using FOO_INCLUDE_DIR, I believe you should use
> target_include_directories() with the INTERFACE or PUBLIC options -
> this will export the include directories properly and they will be
> used when someone target_link_libr
On Monday, December 07, 2015 15:39:40 Attila Krasznahorkay wrote:
> Dear All,
>
> I'm still debugging the performance problems of our build. But now I
bumped
> into another surprising thing.
>
> Our "highest level" packages can depend on a *lot* of low level
packages.
> The one I'm testing now
On Thursday, December 03, 2015 09:27:29 Ruslan Baratov via CMake
wrote:
> On 03-Dec-15 04:34, Alexander Neundorf wrote:
> > On Wednesday, December 02, 2015 12:27:42 Ruslan Baratov wrote:
> > If RPATH was _designed_ to be patchable, tools could just do it,
> > instead o
On Wednesday, December 02, 2015 12:27:42 Ruslan Baratov wrote:
> On 02-Dec-15 05:13, Alexander Neundorf wrote:
...
> > well, the RPATH entry was not designed to be patched,
>
> RPATH designed to be patched. And since it's a third time I'm making
> this statement ple
On Tuesday, December 01, 2015 07:17:35 Ruslan Baratov wrote:
> On 01-Dec-15 03:51, Alexander Neundorf wrote:
> > On Monday, November 30, 2015 16:13:03 Ruslan Baratov via CMake
wrote:
> > > On 30-Nov-15 09:10, Dmitry Marakasov wrote:
> > > > Hi!
> >
> > .
On Monday, November 30, 2015 16:13:03 Ruslan Baratov via CMake
wrote:
> On 30-Nov-15 09:10, Dmitry Marakasov wrote:
> > Hi!
> >
...
> > The best solution would be for cmake to fix path in executable file
> > right after installation, something similar to what cmake does with
> > rpaths.
>
> I do
reluctant to grab another
> dependency that all my consumers would be advised to install.
CMake is a
> fairly full blown suite and I was hoping to find something that could
> provide similar results.
>
> @Matt: Seems nice. Python is not much a dependency, but VTK is
less evident
On Monday, November 09, 2015 23:21:58 Nagy-Egri Máté Ferenc via
CMake wrote:
> Hi!
>
> Can anyone tell me if CMake (or CTest) can be customized in a way to
produce
> decent benchmark output? An .xlsx perhaps, or something GnuPlot
friendly? I
> have not found any examples of CTest being (ab)used
Hi,
On Sunday, September 27, 2015 13:29:15 Talin wrote:
> I've been using CMake and Eclipse for a bunch of different projects over
> the last several years. Although many aspects of both CMake and Eclipse
> have improved over the years, using them together still has a lot of
> problems.
>
> From
On Wednesday, September 02, 2015 22:12:39 Nico Schlömer wrote:
> Indeed,
> ```
> get_target_property(out ${netCDF_LIBRARIES} LOCATION)
> message(${out})
> ```
> gives
> ```
> /usr/lib/x86_64-linux-gnu/libnetcdf.so.7.3.0
> ```
> This value appears to be set in the CMake export file
> ```
> /usr/lib/
On Wednesday, September 02, 2015 20:28:35 Nico Schlömer wrote:
> Curiously,
> ```
> message(${ZLIB_LIBRARIES})
> message(${netCDF_LIBRARIES})
> ```
> yields
> ```
> /usr/lib/x86_64-linux-gnu/libz.so
> netcdf
> ```
> Hm, I would have expected it the other way around. :)
maybe "netcdf" is the name
On Wednesday, September 02, 2015 08:22:08 Nico Schlömer wrote:
> > it uses -l if the full path is not know or if the full path is one of the
> > system
> library dirs
>
> Hm, that sound a little weird. Using `-l` appears to delegate the library
> finding to the linker although CMake has already do
On Friday, August 28, 2015 08:23:47 Nico Schlömer wrote:
> Hi everyone,
>
> I'm curious about when CMake decides to link a library by its absolute path
> and when it links using the `-l*` syntax. I came across this for the very
> simple test problem
> ```
> cmake_minimum_required(VERSION 3.0)
>
>
On Monday, August 17, 2015 09:15:18 Michael Jackson wrote:
> I thought there used to be a DocBook version of the documentation? At one
> point I had an XML parser that used that as input to process the
> documentation in the same way.
the way the documentation is generated has changed with version
On Wednesday, July 29, 2015 07:49:07 Nagy-Egri Máté Ferenc via cmake-
developers wrote:
...
> I believe CMake is an invaluable tool, but it could do far better. 0/10
> CMake users I’ve met say they are “happy” CMake users. The learning curve
> is steep, and the skills gained are not reusable. CMake
On Tuesday, July 07, 2015 14:36:25 Steve Borho wrote:
> Hello, I am the technical lead for x265 (HEVC encoder) and we have used
> cmake successfully since the beginning of the project. There are a few
> rough edges that we've had to work around (uninstall rules, yasm support
> in MSVC, etc) but in
On Thursday, July 02, 2015 04:13:40 Stuermer, Michael SP/HZA-ZSEP wrote:
> Have a look at cmake_minimum_required() and cmake_policy(). I think with
> these both it should be possible to verify you are using a cmake version
> that provides all features which are required by your project.
no, what
On Friday, July 03, 2015 09:33:42 Glenn Coombs wrote:
> I don't think policies are sufficient. I just tried using the new
> target_sources command that was introduced in CMake 3.1.0 in a
> CMakeLists.txt file that specified cmake_minimum_required(VERSION 3.0) and
> it didn't warn that the CMakeLis
On Monday, June 22, 2015 18:02:01 Cedric Doucet wrote:
> Hello,
>
> I am testing the possibility of generating Eclipse projects with CMake.
> I use the following command line:
> cmake -G"Eclipse CDT4 - Unix Makefiles" -D CMAKE_BUILD_TYPE=Debug ../src
> It works fine.
>
> However, I would like to
On Saturday, June 13, 2015 23:26:59 tors...@robitzki.de wrote:
> Hi Alex,
>
> Am 13.06.2015 um 22:18 schrieb Alexander Neundorf :
> > On Friday, May 29, 2015 11:14:06 tors...@robitzki.de wrote:
> …
>
> >> I saw that there is a file Platform/Generic-SDCC-C.cmake, whi
On Saturday, June 13, 2015 23:17:37 René J.V. Bertin wrote:
> On Saturday June 13 2015 22:26:12 Alexander Neundorf wrote:
> > did you try check_symbol_exists() and the other similar functions ?
>
> Yes, but none that I could find give any information beyond whether the
> symbol
On Thursday, June 11, 2015 19:18:55 Klaim - Joël Lamotte wrote:
> On 11 June 2015 at 15:22, Johannes Zarl-Zierl
>
> wrote:
> > Hi,
> >
> > > I tried several times now to find documentation about how to define
> > > and use target names which seem to have namespaces, like Qt ones.
> > >
> > > Fo
On Wednesday, June 10, 2015 01:32:21 René J. V. Bertin wrote:
> Ok, let me rephrase the question to see what other kind of constructive
> answers that'll lead to:
>
> how does one check which header file provides the prototype for a function
> from the system libraries? Function in question: reall
On Sunday, June 07, 2015 17:39:39 Peng Yu wrote:
> Hi, I following the following steps to compile gtest.
>
> https://code.google.com/p/tonatiuh/wiki/GoogleTest
>
> But the following output shows that it uses the default compiler on
> Mac OS X. I want to use some other compiler. Does anybody know
On Friday, May 29, 2015 11:14:06 tors...@robitzki.de wrote:
> Hello,
> I was looking for some resources on how to configure cmake to use the small
> device c compiler (sdcc). I tried a little bit and found that cmake assumed
> that the object file extension would be .obj. But sdcc uses .rel for obj
On Friday, April 24, 2015 12:33:50 Alan W. Irwin wrote:
> The Fedora packager of PLplot is having trouble splitting installed
> results into separate binary packages because of the way that PLplot
> currently exports its targets. What steps do we have to do to make
> life easier for him?
>
> Here
On Tuesday, April 07, 2015 15:24:18 Daniel Dilts wrote:
> Looking at the way these things work, it seems to me that the ideal
> solution to my situation, if it is possible, is to do a
> add_custom_command() for each source file, and then do a
> add_custom_target() that has all of the custom command
On Tuesday, April 07, 2015 13:22:30 you wrote:
> > > > I have a custom executable that does some codegen to produce an
> > > >
> >> > > enumeration and a couple of tables. I need this to be run against
> >>
> >> each
> >>
> >> > > source file before actual compilation. It needs include directo
On Monday, April 06, 2015 21:19:57 Klaim - Joël Lamotte wrote:
> On Mon, Apr 6, 2015 at 8:47 PM, Daniel Dilts wrote:
> > I have a custom executable that does some codegen to produce an
> > enumeration and a couple of tables. I need this to be run against each
> > source file before actual compila
Thanks, that really clears things up for me!
--Alex
On 04.04.15 14:39, Mark Abraham wrote:
On 03/04/2015 8:24 pm, "Alexander Droste" <
alexander.ra.dro...@googlemail.com> wrote:
Hello everyone,
based on the documentation here:
http://www.cmake.org/cmake/help/v3.0/module/F
calling: message(STATUS "MPI_C_COMPILE_FLAGS = ${MPI_C_COMPILE_FLAGS}")
gives me: MPI_C_COMPILE_FLAGS =
So there are no flags contained.
Is it in general preferable to use this:
target_compile_options..
instead of:
set(CMAKE_COMPILE_FLAGS ${CMA..
?
On 04.04.15 00:28, Daniel Schepler wrote:
I m
Do you mean just using:
target_compile_options(core.x PUBLIC ${MPI_C_COMPILE_FLAGS})
but not:
include_directories(SYSTEM ${MPI_C_INCLUDE_PATH})
link_directories(${MPI_C_LINK_FLAGS})
set(CMAKE_COMPILE_FLAGS ${CMAKE_COMPILE_FLAGS} ${MPI_C_COMPILE_FLAGS})
target_link_libraries(core.x ${MPI_C_LIBRARI
-kt
-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Alexander Droste
Sent: Friday, April 03, 2015 12:24 PM
To: cmake@cmake.org
Subject: [CMake] how to use the FindMPI module correctly?
Hello everyone,
based on the documentation here:
http://www.cmake.org/cmake/help/v3.0/m
1 - 100 of 2609 matches
Mail list logo
