The latest version of CMake, cmake-2.8.4-Linux-i386.tar.gz does not
looking in /lib64 paths. Could you let me know which version of CMake
you are referring to, that checks this path?
Thanks,
Sara
On May 21, 2011, at 3:47 PM, Eric Noulard wrote:
2011/5/20 Sara Rolfe :
Hello,
I am attemp
Hi Eric,
Thanks for your reply. I am using cmake-2.8.2 for Linux. I just
checked and it looks like that's not the most recent version. Do
you know if the most recent version, cmake-2.8.4 addresses this
problem?
Thanks,
Sara
On May 21, 2011, at 3:47 PM, Eric Noulard wrote:
2011/5/
2011/5/20 Sara Rolfe :
> Hello,
>
> I am attempting to modify my make file so the linker will check for
> /usr/lib64 instead of /usr/lib. I found a patch for this problem here:
>
> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=126c993d#patch1
This commit is not related with "finding" lib64 (
Hello,
I think my main problem is that I don't understand how to apply a
patch. This seems pretty basic, so I would think there would be
documentation...which I'm not finding.
Could someone point me to this information?
Thanks,
Sara
On May 19, 2011, at 3:46 PM, Sara Rolfe wrote:
Hello,
On Sat, May 21, 2011 at 1:39 PM, Eric Noulard wrote:
> Just tested and merged your patch proposal to next.
> db45b10 CPack make RPM work on AIX. fix #0012183 merge patch from Pasi
> Valminen
>
Splendid. Thanks.
Cheers,
Pasi
___
Powered by www.kitware.c
On Thursday 19 May 2011, Matthias Kretz wrote:
> Hi,
>
> On Tuesday 10 May 2011 21:47:41 Alexander Neundorf wrote:
> > Are you using cmake >= 2.8 ?
> > If so, there the switch CTEST_USE_LAUNCHERS. If this is set in your
> > ctest- script, the output parsing works better.
>
> After I set CTEST_USE
2011/5/11 Pasi Valminen :
>
> Thanks. :)
> AIX knows about RPMs since 5.1 at least (current version being 7.1), but the
> version is a bit old 3.x IIRC. I find RPMs more flexible in their rules than
> the AIX bff format. So, I prefer creating RPM packages if possible since
> there's native support
First of all, don't use "./lib" and "./share" as destinations in the
INSTALL() command. In the export files generated by INSTALL(EXPORT),
CMake computes the targets' IMPORTED_LOCATION property by ascending
from the export file's location to the CMAKE_INSTALL_PREFIX and sub-
sequently appending t
