On Monday 21 January 2013, Andrea Scarpino wrote:
> On Monday 21 January 2013 20:09:57 Alexander Neundorf wrote:
> > what about /include/ ?
> > This typically does not exist, but this will also make the Config.cmake
> > files fail.
> > The Config.cmake files typically reference the include/ subdir,
On Sunday 18 November 2012, Andrea Scarpino wrote:
> On Saturday 17 November 2012 20:24:42 you wrote:
> > Hi,
> >
> > maybe I am missing something, but here we go:
> >
> > on 64bit ArchLinux installations, /lib64/ is a symlink to /usr/lib/.
> > /bin/ and /usr/bin/ are normal directories, no symli
On Thursday 13 December 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Thursday 06 December 2012, Stephen Kelly wrote:
> >> Alexander Neundorf wrote:
> >> > On Thursday 06 December 2012, Stephen Kelly wrote:
> >> > ...
> >> >
> >> >> I don't fully follow (too much 'the example' etc
Alexander Neundorf wrote:
> On Thursday 06 December 2012, Stephen Kelly wrote:
>> Alexander Neundorf wrote:
>> > On Thursday 06 December 2012, Stephen Kelly wrote:
>> > ...
>> >
>> >> I don't fully follow (too much 'the example' etc :)), but I guess it's
>> >> not too important. I think the two c
On Thursday 06 December 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Thursday 06 December 2012, Stephen Kelly wrote:
> > ...
> >
> >> I don't fully follow (too much 'the example' etc :)), but I guess it's
> >> not too important. I think the two cases we're talking about are clear
Alexander Neundorf wrote:
> On Thursday 06 December 2012, Stephen Kelly wrote:
> ...
>> I don't fully follow (too much 'the example' etc :)), but I guess it's
>> not too important. I think the two cases we're talking about are clear
>>
>> * Installing to a location where one or more locations bel
On Thursday 06 December 2012, Stephen Kelly wrote:
...
> I don't fully follow (too much 'the example' etc :)), but I guess it's not
> too important. I think the two cases we're talking about are clear
>
> * Installing to a location where one or more locations below
> ${CMAKE_INSTALL_PREFIX} are sy
Alexander Neundorf wrote:
>> I also think it's a very bad idea to install into a prefix where one of
>> the directories below it is a symlink to somewhere else. I think that
>> also deserves a warning.
>
> See below, you can get the same problem if you install into a prefix where
> there is no sy
On Thursday 06 December 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Thursday 06 December 2012, Stephen Kelly wrote:
> >> Alexander Neundorf wrote:
> >> > On Thursday 06 December 2012, Stephen Kelly wrote:
> >> >> Alexander Neundorf wrote:
> >> >> > Let's assume /opt/foo/lib/ is a
Alexander Neundorf wrote:
> On Thursday 06 December 2012, Stephen Kelly wrote:
>> Alexander Neundorf wrote:
>> > On Thursday 06 December 2012, Stephen Kelly wrote:
>> >> Alexander Neundorf wrote:
>> >> > Let's assume /opt/foo/lib/ is a symlink to /usr/local/lib/.
>> >> > The package has been insta
On Thursday 06 December 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Thursday 06 December 2012, Stephen Kelly wrote:
> >> Alexander Neundorf wrote:
> >> > Let's assume /opt/foo/lib/ is a symlink to /usr/local/lib/.
> >> > The package has been installed to /opt/foo/ and is found via
Alexander Neundorf wrote:
> On Thursday 06 December 2012, Stephen Kelly wrote:
>> Alexander Neundorf wrote:
>> > Let's assume /opt/foo/lib/ is a symlink to /usr/local/lib/.
>> > The package has been installed to /opt/foo/ and is found via
>> > CMAKE_PREFIX_PATH in /opt/foo/lib/cmake/Foo/FooConfig.
On Thursday 06 December 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > Let's assume /opt/foo/lib/ is a symlink to /usr/local/lib/.
> > The package has been installed to /opt/foo/ and is found via
> > CMAKE_PREFIX_PATH in /opt/foo/lib/cmake/Foo/FooConfig.cmake.
> > Now when going up to t
Alexander Neundorf wrote:
> Let's assume /opt/foo/lib/ is a symlink to /usr/local/lib/.
> The package has been installed to /opt/foo/ and is found via
> CMAKE_PREFIX_PATH in /opt/foo/lib/cmake/Foo/FooConfig.cmake.
> Now when going up to the prefix, we will come across /opt/foo/lib/, which
> is a sy
On Tuesday 04 December 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > All install variables which are at cmake time somewhere below
> > CMAKE_INSTALL_PREFIX are treated as relative to CMAKE_INSTALL_PREFIX.
> > This is what the @PAKCAGE_INIT@ macro together with the @PACKAGE_FOO_DIR@
> >
Alexander Neundorf wrote:
> All install variables which are at cmake time somewhere below
> CMAKE_INSTALL_PREFIX are treated as relative to CMAKE_INSTALL_PREFIX.
> This is what the @PAKCAGE_INIT@ macro together with the @PACKAGE_FOO_DIR@
> variables does.
Could your set_and_check macro be extende
On Thursday 29 November 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Saturday 17 November 2012, Alexander Neundorf wrote:
> >> Hi,
> >>
> >> maybe I am missing something, but here we go:
> >>
> >> on 64bit ArchLinux installations, /lib64/ is a symlink to /usr/lib/.
> >> /bin/ and
Alexander Neundorf wrote:
> On Saturday 17 November 2012, Alexander Neundorf wrote:
>> Hi,
>>
>> maybe I am missing something, but here we go:
>>
>> on 64bit ArchLinux installations, /lib64/ is a symlink to /usr/lib/.
>> /bin/ and /usr/bin/ are normal directories, no symlinks.
>>
>> Now if a Co
On Saturday 17 November 2012, Alexander Neundorf wrote:
> Hi,
>
> maybe I am missing something, but here we go:
>
> on 64bit ArchLinux installations, /lib64/ is a symlink to /usr/lib/.
> /bin/ and /usr/bin/ are normal directories, no symlinks.
>
> Now if a Config.cmake files is installed into /u
Alexander Neundorf wrote:
> On Saturday 17 November 2012, Alexander Neundorf wrote:
>> Hi,
>>
>> maybe I am missing something, but here we go:
>>
>> on 64bit ArchLinux installations, /lib64/ is a symlink to /usr/lib/.
>> /bin/ and /usr/bin/ are normal directories, no symlinks.
>>
>> Now if a Co
On Saturday 17 November 2012 20:24:42 you wrote:
> Hi,
>
> maybe I am missing something, but here we go:
>
> on 64bit ArchLinux installations, /lib64/ is a symlink to /usr/lib/.
> /bin/ and /usr/bin/ are normal directories, no symlinks.
Hi Alexander,
that's true, anyway we'll symlink /bin to /us
On Saturday 17 November 2012, Alexander Neundorf wrote:
> Hi,
>
> maybe I am missing something, but here we go:
>
> on 64bit ArchLinux installations, /lib64/ is a symlink to /usr/lib/.
> /bin/ and /usr/bin/ are normal directories, no symlinks.
>
> Now if a Config.cmake files is installed into /u
Hi,
maybe I am missing something, but here we go:
on 64bit ArchLinux installations, /lib64/ is a symlink to /usr/lib/.
/bin/ and /usr/bin/ are normal directories, no symlinks.
Now if a Config.cmake files is installed into /usr/lib/foo/, and references
other files of its installations using rela
23 matches
Mail list logo
