Hi Joachim,
Am Samstag, 20. Oktober 2018, 13:22:04 CEST schrieb Joachim Wuttke:
> If Config mode is the newer, preferred way to find a package, I would expect
> find_package to first try Config mode, and only fall back to Module mode if
> no config scripts can be found. However, according to the
Am Dienstag, 7. August 2018, 14:48:26 CEST schrieb Randy Heiland:
> Hmm, well if that's the case, how does one generate the HelloConfig.cmake
> file?
The official documentation is here:
https://cmake.org/cmake/help/latest/manual/cmake-packages.7.html
> Although, for my particular situation, my
Hi Ardi,
Am Mittwoch, 18. Juli 2018, 11:31:50 CEST schrieb ardi:
> For example, I'd like to type "somecommand /path/to/someproject" at
> the UNIX command line, and get this output:
> [...]
> Furthermore, if another command could show optional requisites, it
> would be really great:
gt; I've updated the merge request to incorporate this feedback.
>
> https://gitlab.kitware.com/cmake/cmake/merge_requests/2180
--
Johannes Zarl-Zierl
Information management
JOHANNES KEPLER UNIVERSITY LINZ
Altenberger Straße 69
4040 Linz, Austria
P +43 732 2468 3898
johannes.zarl-zi...@j
T_OPTION not being defined at all - like in a standalone build!
> >
> >
> >
> >
> >
> > One way would be to have an additional option or variable
> > BUILDING_MAINPROJECT which is set to ON or TRUE in the main project
> > and can be checked.
On Dienstag, 22. Mai 2018 11:13:18 CEST Brad King wrote:
> > not be much more work for the maintainer as pkg-config files.
>
> There is a proposal here:
>
> https://mwoehlke.github.io/cps/
This looks quite promising!
Do you know whether there's a shared interest on the pkg-config and
Hi Mateusz,
On Montag, 21. Mai 2018 19:39:16 CEST Mateusz Loskot wrote:
> The FindLZ4 discussion basically ended with suggestion from Brad that,
> instead of adding Find-module to CMake, I should approach LZ4 project
> and add Config-file to the library itself.
> Then I argued taht Config-files
On Dienstag, 17. April 2018 13:48:39 CEST David Demelier wrote:
> On Tue, 2018-04-17 at 12:25 +0200, Johannes Zarl-Zierl wrote:
> > Just replying to this topic of your message: you may want to
> > reconsider. The
> > cmake gui allows you to group options automatically b
Hi David,
On Dienstag, 17. April 2018 11:58:12 CEST David Demelier wrote:
> 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.
Just replying to this
Hello Carsten,
On Samstag, 25. November 2017 11:46:44 CET Carsten Fuchs wrote:
> Thanks for your reply, but how can I proceed from here?
>
> In order to be able to write in the parent script something that works
> in either case, that is,
>
> target_link_libraries(main_program )
Well, that's
On Mittwoch, 22. November 2017 11:32:22 CET Carsten Fuchs wrote:
> That is, follow-up question: near the "..." above, we have got a target
> "libjpeg", but how do I get the variables JPEG_INCLUDES, JPEG_LIBRARIES
> etc. that `find_package(JPEG)` normally provides so that the last line
> with the
Hi,
On Freitag, 25. August 2017 11:21:50 CEST Robert Dailey wrote:
> However, what I'm wondering is even though the import targets should
> contain all information about include directories, libraries, etc,
> should I still define the typical Foo_INCLUDE_DIRS, Foo_LIBRARIES
> variables?
This
On Dienstag, 21. März 2017 15:24:13 CET you wrote:
> > Did you try asking on the libsndfile mailing list?
> I did .but there was no response .
Ok then.
> I had written cmakelists.txt to compile and build .
> I was able to successfully built it in linux , but in windows I was not
> able to do it
Hi,
On Dienstag, 21. März 2017 10:57:42 CET aishwarya selvaraj wrote:
> I'm very new to all this , So Could anyone please guide me on what to do
> next .
Did you try asking on the libsndfile mailing list? They are more likely to know
about the issue you're dealing with.
Try here:
Hi,
On Tuesday 05 July 2016 23:46:16 J Decker wrote:
> https://cmake.org/cmake/help/v3.4/policy/CMP0065.html
> while I like the idea it suggests, I don't use the flags for -rdynamic so
> this is meaningless to me
I'm not sure I understood you correctly, but if the policy is meaningless to
you,
Hi Rob,
I've stopped working on it when 3.0 came out. Since the whole thing was very
much manual work (diff'ing documentation pages and checking whether some
change was only better documentation or a real change in cmake), it was too
much effort to continue long-term.
Johannes
On Saturday
> > I.e. it could be replaced with a string of the same length or a
> > shorter one, but not a longer one.
> >
> > CMake works around this by extending the build RPATH artificially with
> > ":" at the end I think, patchelf works around this by making the whole
> > executable one page bigger if
Hi,
For header files, that's quite a normal thing to do - you just need to add the
CMAKE_CURRENT_BINARY_DIR to your include directories.
For .cpp files, you can write your target so that it is referencing the source
file in the binary directory. I.e.:
configure_file(
Hi,
CXX_STANDARD is a target property, not a global one. You can either set
CXX_STANDARD for every target that needs it, or set it globally by changing
the default value.
You can do the latter by setting the variable CMAKE_CXX_STANDARD before
defining any target that depends on it:
Hi,
On Monday 07 September 2015 23:47:35 Aaron Gray wrote:
> cmake_minimum_required(VERSION 2.6)
Just as a side note: if you need to support cmake 2.6, that's fine. However,
if you are starting a new project and do not *need* to limit yourself to cmake
2.6, develop for a cmake version that as
On Monday 15 June 2015 22:43:41 you wrote:
Just a last question: I assume that most find module scripts distributed
with cmake are
not using this feature at the moment, right?
Sadly, no.
After reading your explaination I looked at documentation for FindBoost and
FindGTest
which are both
On Monday 15 June 2015 16:40:10 Klaim - Joël Lamotte wrote:
So far I didn't get what imported targets helps with, so I'm a bit lost on
the usefulness of namespaces
but I am sure that I am missing something.
Imported targets improve the handling of find_package stuff. In the old days,
the
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.
For example: add_executable( MyProject::some_target ... )
AFAIK target namespaces are intended for imported targets, not regular
targets:
A NAMESPACE
On Wednesday 10 June 2015 00:48:06 J Decker wrote:
CHECK_INCLUDE_FILE(stdint.h HAVE_STDINT_H)
is this supposed to create some sort of ADD_DEFINITION( -DHAVE_STDINT_H) ?
No.
if not what else do I have to do to make that work?
IF(HAVE_STDINT_H)
ADD_DEFINITION(HAVE_STDINT_H)
ENDIF()
If you
24 matches
Mail list logo
