At this point of the discussion, I think that we need someone else to
join. We both have made strong points for our viewpoints, and neither of
us has a perfect solution.
On Sunday 05 December 2010 12:48:49 Michael Hertling wrote:
On 12/01/2010 05:57 PM, Johannes Zarl wrote:
On 12/01/2010 at
On Sunday 05 Dec 2010 6:16:35 pm Michael Hertling wrote:
On 11/30/2010 05:53 AM, Kishore wrote:
On Tuesday 23 Nov 2010 5:27:56 pm Johannes Zarl wrote:
Another somehow related topic seems to be import/export of targets. Should
a LibraryConfig.cmake or FindLibrary.cmake file create imported
On 12/01/2010 05:57 PM, Johannes Zarl wrote:
On 12/01/2010 at 16:06, Michael Hertling mhertling at online.de wrote:
FIND_PACKAGE(XXX COMPONENTS YYY)
...
ADD_SUBDIRECTORY(subdir)
...
TARGET_LINK_LIBRARIES(AAA ${XXX_LIBRARIES})
TARGET_LINK_LIBRARIES(BBB ${XXX_LIBRARIES} ${XXX_YYY_LIBRARIES})
On 11/30/2010 05:53 AM, Kishore wrote:
On Tuesday 23 Nov 2010 5:27:56 pm Johannes Zarl wrote:
Another somehow related topic seems to be import/export of targets. Should
a LibraryConfig.cmake or FindLibrary.cmake file create imported targets
for the library?
Thanks for this thread. It has
On Wednesday 01 December 2010 17:57:45 Johannes Zarl wrote:
Back to my proposed FPCHSA: My initial goal was to provide an interface
which does as much work as possible for you, maybe at the price of
restricted variable naming. So let's come up with a better interface:
I do want to restrict
On 11/30/2010 01:32 PM, Johannes Zarl wrote:
- Do multiple consecutive FIND_PACKAGE(XXX ...) invocations act in an
accumulative manner on the invocation-specific variables?
Generally speaking, I would say: yes. At least this is the way of the
least surprise for the user, as in sufficiently
On 12/01/2010 at 16:06, Michael Hertling mhertl...@online.de wrote:
FIND_PACKAGE(XXX COMPONENTS YYY)
...
ADD_SUBDIRECTORY(subdir)
...
TARGET_LINK_LIBRARIES(AAA ${XXX_LIBRARIES})
TARGET_LINK_LIBRARIES(BBB ${XXX_LIBRARIES} ${XXX_YYY_LIBRARIES})
In subdir/CMakeLists.txt:
FIND_PACKAGE(XXX
On 11/29/2010 02:28 PM, Johannes Zarl wrote:
Sorry for the late response, but your mail was simply to long for a
swift response...
No problem, this topic is not exactly trivial.
On 11/26/2010 at 05:47, Michael Hertling mhertl...@online.de wrote:
On 11/24/2010 04:51 PM, Johannes Zarl wrote:
On 11/30/2010 at 11:39, Michael Hertling mhertl...@online.de wrote:
Does this mean that XXX_LIBRARIES etc. should normally incorporate the
settings for the components as well? [...]
Yes, of course, if FIND_PACKAGE(XXX ...) returns successfully one would
expect XXX_LIBRARIES to hold all
Sorry for the late response, but your mail was simply to long for a
swift response...
On 11/26/2010 at 05:47, Michael Hertling mhertl...@online.de wrote:
On 11/24/2010 04:51 PM, Johannes Zarl wrote:
About the components question again: I played around a bit, and I think I
now more or less
On 11/29/2010 at 14:28, Johannes Zarl johannes.z...@jku.at wrote:
On 11/26/2010 at 05:47, Michael Hertling mhertl...@online.de wrote:
See [1] for a former discussion of
several aspects regarding multi-component packages.
[...]
[1] http://www.mail-archive.com/cmake@cmake.org/msg28431.html
On Tuesday 23 Nov 2010 5:27:56 pm Johannes Zarl wrote:
Another somehow related topic seems to be import/export of targets. Should
a LibraryConfig.cmake or FindLibrary.cmake file create imported targets
for the library?
Thanks for this thread. It has helped. However, i am still not clear about
On 25-11-2010 at 17:34, in message
201011251734.55788.johannes.z...@jku.at,
Johannes Zarl johannes.z...@jku.at wrote:
I took the liberty and compiled such a compatibility matrix here:
http://www.cmake.org/Wiki/CMake_Version_Compatibility_Matrix
It's a draft and does not (yet) contain
2010/11/25 Johannes Zarl johannes.z...@jku.at:
On Wednesday 24 November 2010 19:03:21 David Cole wrote:
On Wed, Nov 24, 2010 at 12:58 PM, Tyler Roscoe ty...@cryptio.net wrote:
On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer
On Friday 26 November 2010 10:49:01 Eric Noulard wrote:
From the information in http://www.cmake.org/Wiki/CMake_Released_Versions
and using some shell-scripts to create the diffs between all
neighbor-versions, it's not too much work to create a compatibility
matrix for the documented
On 24-11-2010 at 17:34, in message
ddc068a445e2cc6dcf015e9b84217da0.squir...@webmail.sf-mail.de, Rolf
Eike
Beer e...@sf-mail.de wrote:
On Wed, Nov 24, 2010 at 6:57 AM, Rolf Eike Beer e...@sf-mail.de
wrote:
In KDE we have a macro MACRO_WRITE_BASIC_CMAKE_VERSION_FILE()
which
helps
with
2010/11/25 Marcel Loose lo...@astron.nl:
Everyone looks into his local CMake documentation and uses what he
finds
in there. And then it breaks on older versions. You currently have
no
chance to know what works but to install all older versions and do a
binary search in the documentation.
On Wednesday 24 November 2010 19:03:21 David Cole wrote:
On Wed, Nov 24, 2010 at 12:58 PM, Tyler Roscoe ty...@cryptio.net wrote:
On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer e...@sf-mail.de wrote:
So I think it is _really_
On Thursday 25 November 2010, Johannes Zarl wrote:
On Wednesday 24 November 2010 19:03:21 David Cole wrote:
On Wed, Nov 24, 2010 at 12:58 PM, Tyler Roscoe ty...@cryptio.net wrote:
On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer
On 11/24/2010 04:51 PM, Johannes Zarl wrote:
Hi,
On 11/23/2010 at 21:25, Alexander Neundorf a.neundorf-w...@gmx.net wrote:
CMAKE_MODULE_PATH is only for finding Find-modules, not for finding the
actual packages or Config-files.
For that you can set CMAKE_PREFIX_PATH. CMake uses each
In KDE we have a macro MACRO_WRITE_BASIC_CMAKE_VERSION_FILE() which helps
with
creating a basic version-info file which should be installed along with
the
Config-file.
It consists of MacroWriteBasicCMakeVersionFile.cmake and
BasicFindPackageVersion.cmake.in which you can find in
On Wed, Nov 24, 2010 at 6:57 AM, Rolf Eike Beer e...@sf-mail.de wrote:
In KDE we have a macro MACRO_WRITE_BASIC_CMAKE_VERSION_FILE() which helps
with
creating a basic version-info file which should be installed along with
the
Config-file.
It consists of MacroWriteBasicCMakeVersionFile.cmake
On Wed, Nov 24, 2010 at 6:57 AM, Rolf Eike Beer e...@sf-mail.de wrote:
In KDE we have a macro MACRO_WRITE_BASIC_CMAKE_VERSION_FILE() which
helps
with
creating a basic version-info file which should be installed along with
the
Config-file.
It consists of
On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer e...@sf-mail.de wrote:
On Wed, Nov 24, 2010 at 6:57 AM, Rolf Eike Beer e...@sf-mail.de wrote:
In KDE we have a macro MACRO_WRITE_BASIC_CMAKE_VERSION_FILE() which
helps
with
creating a basic version-info file which should be installed along with
On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer e...@sf-mail.de wrote:
So I think it is _really_ necessary to go through all the CMake
documentation items and add a line about when which feature was added.
Adding that information
On Wed, Nov 24, 2010 at 12:58 PM, Tyler Roscoe ty...@cryptio.net wrote:
On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer e...@sf-mail.de wrote:
So I think it is _really_ necessary to go through all the CMake
documentation items and
2010/11/24 David Cole david.c...@kitware.com:
On Wed, Nov 24, 2010 at 12:58 PM, Tyler Roscoe ty...@cryptio.net wrote:
On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer e...@sf-mail.de wrote:
So I think it is _really_ necessary to go
Sorry for hijacking this thread, but I'm wondering about this for some
time, too. (And the information in the doc/wiki is somewhat dated and/or
ambiguous [1,2,3,4]). I will just go on and write my thoughts and what I
(think I) know, in the hope that somebody corrects those things I got
wrong.
On Mon, Nov 22, 2010 at 10:37 PM, Michael Hertling mhertl...@online.de wrote:
[snip]
This seems like a common situation, so I'm wondering what the common
solution is.
'hope that helps.
Thanks, yes that helps a lot. I figured there must be some method like this.
@Johannes Zarl: hijack away,
So with a library, the correct thing to do is to install your
FindLibrary.cmake into ${CMAKE_ROOT}/Modules and then dependent
projects would just do find_package(Library REQUIRED) correct?
I guess I'm thinking about how, in the situation where they don't have
the library installed, they would
30 matches
Mail list logo
