Re: [CMake] Weirdness with shared library, RPATH policy on MacOS

On 8/13/10 1:12 PM, Martin Costabel wrote: > Chris Wolf wrote: > [] >> Have you actually built shared libraries on MacOS with CMake? If so, >> maybe an example >> of yours would be more helpful. > > The following settings work for me

Re: [CMake] Weirdness with shared library, RPATH policy on MacOS

On 8/15/10 12:43 PM, Michael Wild wrote: > > On 15. Aug, 2010, at 13:22 , Chris Wolf wrote: > >> >> >> >>>> >>>> No, the two mechanisms are fundamentally different. >>>> >>>> On Linux the RPATH is a search pat

Re: [CMake] Weirdness with shared library, RPATH policy on MacOS

On 8/14/10 4:01 PM, Michael Wild wrote: > > On 14. Aug, 2010, at 18:26 , Chris Wolf wrote: > >> >> >> On 8/14/10 10:31 AM, Michael Wild wrote: >>> >>> On 14. Aug, 2010, at 15:13 , Chris Wolf wrote: >>> >>>> >>>> &g

Re: [CMake] Weirdness with shared library, RPATH policy on MacOS

On 8/14/10 10:31 AM, Michael Wild wrote: > > On 14. Aug, 2010, at 15:13 , Chris Wolf wrote: > >> >> >> On 8/14/10 3:35 AM, Michael Wild wrote: >>> >>> On 13. Aug, 2010, at 20:58 , Michael Wild wrote: >>> [...] >>>> >>&g

Re: [CMake] Weirdness with shared library, RPATH policy on MacOS

On 8/14/10 3:35 AM, Michael Wild wrote: > > On 13. Aug, 2010, at 20:58 , Michael Wild wrote: > [...] >> >> Sure, http://repo.or.cz/w/freefoam.git/shortlog/refs/heads/pu, but it's >> pretty complex... >> >> Michael > > Attached is a tiny project which works for me on both Linux and Mac. > > Mi

Re: [CMake] Weirdness with shared library, RPATH policy on MacOS

On 8/13/10 11:21 AM, Michael Wild wrote: > > On 13. Aug, 2010, at 16:32 , Chris Wolf wrote: > >> >> >> On 8/13/10 10:23 AM, Chris Wolf wrote: >>> >>> >>> On 8/13/10 9:29 AM, Michael Wild wrote: >>>> >>>> On 13. Aug,

Re: [CMake] Weirdness with shared library, RPATH policy on MacOS

On 8/13/10 10:23 AM, Chris Wolf wrote: > > > On 8/13/10 9:29 AM, Michael Wild wrote: >> >> On 13. Aug, 2010, at 15:25 , Chris Wolf wrote: >> >>> >>> I have confirmed that the RPATH handling, as documented here: >>> >>> http://www.c

Re: [CMake] Weirdness with shared library, RPATH policy on MacOS

On 8/13/10 9:29 AM, Michael Wild wrote: > > On 13. Aug, 2010, at 15:25 , Chris Wolf wrote: > >> >> I have confirmed that the RPATH handling, as documented here: >> >> http://www.cmake.org/Wiki/CMake_RPATH_handling >> >> Is only accurate for the Li

Re: [CMake] Weirdness with shared library, RPATH policy on MacOS

I have confirmed that the RPATH handling, as documented here: http://www.cmake.org/Wiki/CMake_RPATH_handling Is only accurate for the Linux case and *NOT* for MacOS. Here is the summary of my findings: "Default RPATH": http://www.cmake.org/Wiki/CMake_RPATH_handling#Default_RPATH_settings li

Re: [CMake] Weirdness with shared library, RPATH policy on MacOS

On 8/13/10 3:47 AM, Michael Wild wrote: > > On 12. Aug, 2010, at 22:37 , Chris Wolf wrote: > >> I have a project which creates a shared library and a utility which uses this >> shared library. I would like to be able to run the utility within the build >> tree and

[CMake] Weirdness with shared library, RPATH policy on MacOS

I have a project which creates a shared library and a utility which uses this shared library. I would like to be able to run the utility within the build tree and also from the final install directory. I can do this, it works, but the path hard-coded path in the executable is always the build tre

Re: [CMake] Framework + Unix tools help

On 8/12/10 10:20 AM, Carlos Gonçalves wrote: > Hi, > > I have already looked everywhere possible (so to speak) on how to create a > Framework + Unix tools as described in [1] but found no examples. So far I > was able to create a Framework only [2]. > > I'm trying to add Mac OS X support to G

Re: [CMake] Obtaining info about the compiler command arguments

On 8/12/10 1:30 PM, Óscar Fuentes wrote: > Michael Wild writes: > How to know the compiler arguments set by include_directories, add_definitions, etc? CMAKE__FLAGS (with and whitout the uppercase build_type suffix) doesn't contain anything that was set by the cmake comm

Re: [CMake] OS X architecture changes interfere with CheckTypeSize()?

On 8/11/10 4:29 PM, Michael Wild wrote: > > On 11. Aug, 2010, at 22:16 , Michael Jackson wrote: > >> >> >> On Aug 11, 2010, at 3:52 PM, Michael Wild wrote: >> >>> >>> On 11. Aug, 2010, at 21:44 , Erik Lindahl wrote: >>> Hi, Sound technical answers from both David & Clinton - I se

Re: [CMake] Support for multiple components in cpack

On 8/11/10 5:39 PM, Eric Noulard wrote: > 2010/8/11 Thawan Kooburat : >> Hi Eric, >> >> I read though this thread and also two bug reports related to this issue. >> >> It seems like it will take a while because of CPack design issue. Do >> you think there will be any workaround or small hack to m

Re: [CMake] Support for multiple components in cpack

On 8/9/10 2:22 PM, Eric Noulard wrote: > 2010/8/9 Chris Wolf : >> >> >> On 8/9/10 12:11 PM, Kishore wrote: >>> On Friday 06 Aug 2010 4:18:36 am Eric Noulard wrote: >>>> 2010/8/4 Kishore : >>>>> On Monday 02 Aug 2010 4:59:47 pm Eric Noul

Re: [CMake] Support for multiple components in cpack

On 8/9/10 12:11 PM, Kishore wrote: > On Friday 06 Aug 2010 4:18:36 am Eric Noulard wrote: >> 2010/8/4 Kishore : >>> On Monday 02 Aug 2010 4:59:47 pm Eric Noulard wrote: Hi All, I did add a patch for the "multiple file problem" http://public.kitware.com/Bug/view.php?id=10736 >>

Re: [CMake] still having a problem with PackageMaker, and now DEB

On 8/7/10 12:13 PM, David Cole wrote: > On Sat, Aug 7, 2010 at 11:55 AM, Chris Wolf wrote: > >> >> >> On 8/7/10 11:22 AM, David Cole wrote: >>> On Sat, Aug 7, 2010 at 11:02 AM, Chris Wolf wrote: >>> >>>> >>>> >>>

Re: [CMake] still having a problem with PackageMaker, and now DEB

On 8/7/10 11:22 AM, David Cole wrote: > On Sat, Aug 7, 2010 at 11:02 AM, Chris Wolf wrote: > >> >> >> On 8/7/10 9:44 AM, David Cole wrote: >>> On Sat, Aug 7, 2010 at 9:26 AM, Chris Wolf wrote: >>> >>>> >>>> >>>> On

Re: [CMake] still having a problem with PackageMaker, and now DEB

On 8/7/10 9:44 AM, David Cole wrote: > On Sat, Aug 7, 2010 at 9:26 AM, Chris Wolf wrote: > >> >> >> On 8/7/10 7:14 AM, Eric Noulard wrote: >>> 2010/8/7 Chris Wolf : >>>> On 8/6/10 8:55 PM, Eric Noulard wrote: >>>>&

Re: [CMake] still having a problem with PackageMaker, and now DEB

On 8/7/10 9:50 AM, David Cole wrote: > On Sat, Aug 7, 2010 at 9:44 AM, David Cole wrote: > >> On Sat, Aug 7, 2010 at 9:26 AM, Chris Wolf wrote: >> >>> >>> >>> On 8/7/10 7:14 AM, Eric Noulard wrote: >>>> 2010/8/7 Chris Wolf : >>&

Re: [CMake] still having a problem with PackageMaker, and now DEB

On 8/7/10 9:44 AM, David Cole wrote: > On Sat, Aug 7, 2010 at 9:26 AM, Chris Wolf wrote: > >> >> >> On 8/7/10 7:14 AM, Eric Noulard wrote: >>> 2010/8/7 Chris Wolf : >>>> On 8/6/10 8:55 PM, Eric Noulard wrote: >>>>&

Re: [CMake] still having a problem with PackageMaker, and now DEB

On 8/7/10 7:14 AM, Eric Noulard wrote: > 2010/8/7 Chris Wolf : >> On 8/6/10 8:55 PM, Eric Noulard wrote: >>> >>> Did you try the command line? >>> >>> cpack -D CPACK_PACKAGING_INSTALL_PREFIX="/opt" -G DEB >

Re: [CMake] still having a problem with PackageMaker, and now DEB

On 8/6/10 8:55 PM, Eric Noulard wrote: > 2010/8/6 Chris Wolf : >> Earlier, I identified a problem with the "PackageMaker" (Apple) packager, >> and now, I see the same exact problem with the "DEB" (Debian) >> packager - it keeps prefixing

Re: [CMake] Error with cpack -G ZIP

On 8/6/10 8:43 PM, Eric Noulard wrote: > 2010/8/6 Chris Wolf : >> I am trying the ZIP package type and I get the same error on MacOS and Linux: >> >> CPack Error: archive_write_header:Filetype not supportedNo such file or >> directory -25 >> CPack Error: arc

Re: [CMake] still having a problem with PackageMaker, and now DEB

be the case here) I'm no expert, so I could be missing things, but I think the behavior should be: CMAKE_INSTALL_PREFIX - controls "make install", does NOT effect "make package" CPACK_PACKAGING_INSTALL_PREFIX - controls "make package", has no effect on "make

Re: [CMake] still having a problem with PackageMaker, and now DEB

On 8/6/10 6:30 PM, David Cole wrote: > On Fri, Aug 6, 2010 at 5:49 PM, Chris Wolf wrote: > >> I'm still unclear what you're suggesting here (quote, below). If >> I run "make package", doesn't that make target invoke cpack with the >> cmak

Re: [CMake] still having a problem with PackageMaker, and now DEB

CPackOptions.cmake") > > > See CMake's "CMakeCPack.cmake" and "CMakeCPackOptions.cmake.in" files in the > top level directory for more CPack magic than you'll be able to absorb on a > Friday afternoon :-) > > > HTH, > David > > &

Re: [CMake] still having a problem with PackageMaker, and now DEB

's "CMakeCPack.cmake" and "CMakeCPackOptions.cmake.in" files in the > top level directory for more CPack magic than you'll be able to absorb on a > Friday afternoon :-) > > > HTH, > David > > > On Fri, Aug 6, 2010 at 4:45 PM, Chris Wolf wrot

[CMake] still having a problem with PackageMaker, and now DEB

Earlier, I identified a problem with the "PackageMaker" (Apple) packager, and now, I see the same exact problem with the "DEB" (Debian) packager - it keeps prefixing "./usr" to all the paths. Changing CPACK_PACKAGING_INSTALL_PREFIX doesn't do anything (even when it's at the top of the file) This

[CMake] Error with cpack -G ZIP

I am trying the ZIP package type and I get the same error on MacOS and Linux: CPack Error: archive_write_header:Filetype not supportedNo such file or directory -25 CPack Error: archive_write_data(): tried to write 16384 write 0 I searched around in case this was a known issue. The Wiki says: "

Re: [CMake] Small, complete CPack example? re: CPACK_INCLUDE_TOPLEVEL_DIRECTORY

On 8/6/10 12:57 PM, Chris Wolf wrote: > > > On 8/6/10 7:22 AM, Eric Noulard wrote: >> 2010/8/6 Chris Wolf : >>> >>> e.g for : install(TARGETS usb LIBRARY DESTINATION lib) >>> >>> (where project name is "libusb") >>> >>

Re: [CMake] Small, complete CPack example?

On 8/6/10 9:46 AM, Bill Hoffman wrote: > There is one in the Tutorial: > > http://www.cmake.org/cmake/help/cmake_tutorial.html > > -Bill I did look at that when I first started, but this tutorial does not install the library (just the executable and headers). Right now, I'm focused on a proje

Re: [CMake] Small, complete CPack example?

On 8/6/10 7:22 AM, Eric Noulard wrote: > 2010/8/6 Chris Wolf : >> >> e.g for : install(TARGETS usb LIBRARY DESTINATION lib) >> >> (where project name is "libusb") >> >> The CPack-generated TGZ archive will contain: >> libusb-0.1.1-Darwin/li

Re: [CMake] Small, complete CPack example?

On 8/5/10 6:22 PM, Eric Noulard wrote: > 2010/8/6 Chris Wolf : >> >> Unfortunately, at first, I din't see how your example is different from >> the parts of my CMakeList.txt I sent in my last post. >> >> Then I noticed that your "install(TAR

Re: [CMake] Small, complete CPack example?

On 8/5/10 5:15 PM, Olaf van der Spek wrote: > On Thu, Aug 5, 2010 at 11:06 PM, Chris Wolf wrote: >> I'm looking all over for an end-to-end basic example of using CPack >> to create a package with a single shared library target. It can >> even

[CMake] Small, complete CPack example?

y basic) example would be helpful. Thanks, Chris Wolf P.S. Here is my current CMakeList.txt: cmake_minimum_required(VERSION 2.8) project(libusb) set(NAME libusb) include(CheckIncludeFiles) include(CPack) set(CPACK_PACKAGE_EXECUTABLES "libusb.dylib" "libusb-1.0.8&q

Re: [CMake] Cannot find "modules" directory on MacOS

.app/Contents/share/cmake-2.8/Modules" Also, I think the man pages still need to be copied, or symlinked, or the MANPATH updated. Thanks, Chris Wolf On 8/5/10 3:18 PM, Ryan Pavlik wrote: > How are you running cmake? I've used the installer from the web site on my > mac, and it wor

[CMake] Cannot find "modules" directory on MacOS

quot;postflight" script should have also symlinked, or copied, the "doc", "man" and "share" directory hierarchies content also. I can do this manually myself, but I just wanted to point out the issue with the MacOS installer package for cmake-2.8.2. Thanks, C