On Thu, Jan 15, 2009 at 11:19 AM, Alexander Neundorf <
a.neundorf-w...@gmx.net> wrote:
> On Thursday 15 January 2009, Robert Dailey wrote:
> > On Thu, Jan 15, 2009 at 6:27 AM, Miguel A. Figueroa-Villanueva <
> >
> > migu...@ieee.org> wrote:
> > > Well, I don't know about libfind_process, but none
On Thursday 15 January 2009, Robert Dailey wrote:
> On Thu, Jan 15, 2009 at 6:27 AM, Miguel A. Figueroa-Villanueva <
>
> migu...@ieee.org> wrote:
> > Well, I don't know about libfind_process, but none of the modules
> > shipped with CMake use it. Again your primary source of information to
> > prop
On Thu, Jan 15, 2009 at 6:27 AM, Miguel A. Figueroa-Villanueva <
migu...@ieee.org> wrote:
> Well, I don't know about libfind_process, but none of the modules
> shipped with CMake use it. Again your primary source of information to
> properly write a find module should be the Modules/readme.txt
> (
On Thu, Jan 15, 2009 at 12:15 AM, Philip Lowman wrote:
> On Wed, Jan 14, 2009 at 10:54 PM, Robert Dailey wrote:
>
> It's not the only one. There are many modules that lack _LIBRARIES.
> Somebody needs to fix them all but there is some confusion over how
> _LIBRARIES works that needs explaining (s
On Wed, Jan 14, 2009 at 11:51 PM, Robert Dailey wrote:
> On Wed, Jan 14, 2009 at 4:20 PM, Miguel A. Figueroa-Villanueva wrote:
>> On Wed, Jan 14, 2009 at 5:54 PM, Andreas Pakulat wrote:
>> > On 14.01.09 15:45:53, Robert Dailey wrote:
>> >> On Wed, Jan 14, 2009 at 1:20 PM, Andreas Pakulat wrote:
>>
On Wed, Jan 14, 2009 at 10:54 PM, Robert Dailey wrote:
> On Wed, Jan 14, 2009 at 9:51 PM, Robert Dailey wrote:
>
>>
>>
>> On Wed, Jan 14, 2009 at 4:20 PM, Miguel A. Figueroa-Villanueva <
>> migu...@ieee.org> wrote:
>>
>>> On Wed, Jan 14, 2009 at 5:54 PM, Andreas Pakulat wrote:
>>> > On 14.01.09
On Wed, Jan 14, 2009 at 9:51 PM, Robert Dailey wrote:
>
>
> On Wed, Jan 14, 2009 at 4:20 PM, Miguel A. Figueroa-Villanueva <
> migu...@ieee.org> wrote:
>
>> On Wed, Jan 14, 2009 at 5:54 PM, Andreas Pakulat wrote:
>> > On 14.01.09 15:45:53, Robert Dailey wrote:
>> >> On Wed, Jan 14, 2009 at 1:20 P
On Wed, Jan 14, 2009 at 4:20 PM, Miguel A. Figueroa-Villanueva <
migu...@ieee.org> wrote:
> On Wed, Jan 14, 2009 at 5:54 PM, Andreas Pakulat wrote:
> > On 14.01.09 15:45:53, Robert Dailey wrote:
> >> On Wed, Jan 14, 2009 at 1:20 PM, Andreas Pakulat wrote:
> >>
> >> > If you look at the cmake docs,
On Wed, Jan 14, 2009 at 5:54 PM, Andreas Pakulat wrote:
> On 14.01.09 15:45:53, Robert Dailey wrote:
>> On Wed, Jan 14, 2009 at 1:20 PM, Andreas Pakulat wrote:
>>
>> > If you look at the cmake docs, then you'll find out that nothing in there
>> > states that wildcards are allowed. Hence I'd assume
On 14.01.09 15:45:53, Robert Dailey wrote:
> On Wed, Jan 14, 2009 at 1:20 PM, Andreas Pakulat wrote:
>
> > If you look at the cmake docs, then you'll find out that nothing in there
> > states that wildcards are allowed. Hence I'd assume that wildcards are not
> > supported.
> >
> > Also you only
On Wed, Jan 14, 2009 at 1:20 PM, Andreas Pakulat wrote:
> If you look at the cmake docs, then you'll find out that nothing in there
> states that wildcards are allowed. Hence I'd assume that wildcards are not
> supported.
>
> Also you only need to set one of the two for find_path to use the
> dir
On 14.01.09 12:33:35, Robert Dailey wrote:
> On Wed, Jan 14, 2009 at 6:22 AM, Andreas Pakulat wrote:
>
> > On 13.01.09 19:06:13, Robert Dailey wrote:
> > > Trust me, I've read this already. It makes no sense to me. How am I
> > supposed
> > > to know that any of the variables it is checking have
On Wed, Jan 14, 2009 at 6:22 AM, Andreas Pakulat wrote:
> On 13.01.09 19:06:13, Robert Dailey wrote:
> > Trust me, I've read this already. It makes no sense to me. How am I
> supposed
> > to know that any of the variables it is checking have been set?
>
> Not sure what you mean wit that. You can
On 13.01.09 19:06:13, Robert Dailey wrote:
> Trust me, I've read this already. It makes no sense to me. How am I supposed
> to know that any of the variables it is checking have been set?
Not sure what you mean wit that. You can check for any cmake variable
wether its set via if()
> And if so, wh
Just making sure it was read. Here is my take line by line from
FindZLIB.cmake
# - Find zlib
# Find the native ZLIB includes and library
#
# ZLIB_INCLUDE_DIR - where to find zlib.h, etc.
# ZLIB_LIBRARIES - List of libraries when using zlib.
# ZLIB_FOUND - True if zlib found.
# Next
Trust me, I've read this already. It makes no sense to me. How am I supposed
to know that any of the variables it is checking have been set? And if so,
where were they set? Could someone give me a summary of what find_path is
searching in in this specific case?
On Tue, Jan 13, 2009 at 4:20 PM, Mic
From the Help page:
All CMake commands
• find_path: Find the directory containing a file.
find_path( name1 [path1 path2 ...])
This is the short-hand signature for the command that is sufficient in
many cases. It is the same as find_path( name1 [PATHS path1
path2 ...])
find_path(
n
Hi,
I'm currently looking at FindZLIB.cmake trying to understand how it works
and I just can't seem to make sense of it. I have a few questions:
1. How does find_path() know where to look? Where is it looking? Where is
it told where to look?
2. Question #1 with find_library() as well.
I
18 matches
Mail list logo
