Re: [CMake] CPack 101

2011-01-18 Thread Alexander Neundorf
On Thursday 23 December 2010, Mike McQuaid wrote: ... Until then, at least the mailing list has a reasonable response rate and, it seems, sufficient participation from knowledgeable folks willing to pitch in and answer. So... if you're confused about something, please ask here. We (I hope

Re: [CMake] CPack 101

2010-12-23 Thread Andreas Pakulat
On 22.12.10 23:24:35, Andreas Mohr wrote: - there's no cmake -E rename available (perhaps for reasons of build rule atomicity) Hmm my cmake -E help tells me different: ... rename oldname newname- rename a file or directory (on one volume) ... This is cmake version

Re: [CMake] CPack 101

2010-12-23 Thread Mike McQuaid
To start with, Charm might be a good example of how to use CPack, it's an internal tool we've written in Qt and use CPack to do all the packaging: https://github.com/KDAB/Charm Check particularly the CMakeLists.txt and Charm/CMakeLists.txt for all the CPack-relevant logic. On 22 December 2010

Re: [CMake] CPack 101

2010-12-23 Thread Mike McQuaid
On 22 December 2010 22:24, Andreas Mohr a...@lisas.de wrote: To put it simply, I was just not happy the entire time while trying to implement this and not finding any satisfying (well-crafted) solution, only ugly, very bad or semi-failing workarounds. That kind of work should be _fun_,

Re: [CMake] CPack 101

2010-12-23 Thread Michael Wild
On 12/22/2010 11:24 PM, Andreas Mohr wrote: On Wed, Dec 22, 2010 at 04:15:07PM -0500, cmake-requ...@cmake.org wrote: Date: Wed, 22 Dec 2010 09:57:11 -0800 From: KC Jones kc.jo...@skype.net Subject: [CMake] CPack 101 And I just don't seem to get it. I know this is very possible. I know

Re: [CMake] CPack 101

2010-12-23 Thread David Cole
On Wed, Dec 22, 2010 at 12:57 PM, KC Jones kc.jo...@skype.net wrote: Feeling really uneasy about putting this out there, but here goes... I have an app that I am building with cmake (2.8) on both Mac (10.6.40 and Linux (Ubuntu 10.04). The app depends on some libraries (Qt4.6 (no plugins) and

Re: [CMake] CPack 101

2010-12-23 Thread Mike McQuaid
On 23 December 2010 12:43, David Cole david.c...@kitware.com wrote: Neither do we: http://public.kitware.com/Bug/view.php?id=10067 As always, as developers we find ourselves constantly working to improve what we have: fixing bugs, implementing new features, answering questions on the mailing

Re: [CMake] CPack 101

2010-12-23 Thread Johan Björk
On Thu, Dec 23, 2010 at 1:43 PM, David Cole david.c...@kitware.com wrote: On Wed, Dec 22, 2010 at 12:57 PM, KC Jones kc.jo...@skype.net wrote: Feeling really uneasy about putting this out there, but here goes... I have an app that I am building with cmake (2.8) on both Mac (10.6.40 and

Re: [CMake] CPack 101

2010-12-23 Thread David Cole
On Thu, Dec 23, 2010 at 7:58 AM, Mike McQuaid m...@mikemcquaid.com wrote: On 23 December 2010 12:43, David Cole david.c...@kitware.com wrote: Neither do we: http://public.kitware.com/Bug/view.php?id=10067 As always, as developers we find ourselves constantly working to improve what we

Re: [CMake] CPack 101

2010-12-23 Thread David Cole
On Thu, Dec 23, 2010 at 8:23 AM, Johan Björk p...@spotify.com wrote: On Thu, Dec 23, 2010 at 1:43 PM, David Cole david.c...@kitware.comwrote: On Wed, Dec 22, 2010 at 12:57 PM, KC Jones kc.jo...@skype.net wrote: Feeling really uneasy about putting this out there, but here goes... I have

Re: [CMake] CPack 101

2010-12-23 Thread Mike McQuaid
On 23 December 2010 13:24, David Cole david.c...@kitware.com wrote: How do we make it very hard? What about KDE and Homebrew make this very easy? Specifics, please. Firstly, http://producingoss.com/ is a great read. Specifically though, Homebrew is pretty much the golden child of encouraging

Re: [CMake] CPack 101

2010-12-23 Thread Bill Hoffman
On 12/23/2010 8:44 AM, Mike McQuaid wrote: On 23 December 2010 13:24, David Coledavid.c...@kitware.com wrote: How do we make it very hard? What about KDE and Homebrew make this very easy? Specifics, please. I think for you guys general guidelines on what patches would/wouldn't be accepted

Re: [CMake] CPack 101

2010-12-23 Thread Raymond Wan
Hi Mike and all, On Thu, Dec 23, 2010 at 21:58, Mike McQuaid m...@mikemcquaid.com wrote: On 23 December 2010 12:43, David Cole david.c...@kitware.com wrote: I think the main problem is that you make it very hard for people to contribute. KDE and Homebrew (two other open-source projects I've

Re: [CMake] CPack 101

2010-12-23 Thread Bill Hoffman
On 12/23/2010 9:59 AM, Mike McQuaid wrote: A few questions: What platforms does it need to be tested on? At least one. The important thing is that it actually has a test, that will be run with make test on CMake after the code is merged into CMake. The dashboards will take care of testing

Re: [CMake] CPack 101

2010-12-23 Thread KC Jones
Thanks for your comments and questions. May we quote you on that? (cmake is elegant in the extreme ... great tool) Of course. Since all the code I work with is published on multiple OSes, cmake is a godsend. I'm actively working on replacing as much of our legacy build methods with cmake

Re: [CMake] CPack 101

2010-12-23 Thread David Cole
On Thu, Dec 23, 2010 at 3:59 PM, KC Jones kc.jo...@skype.net wrote: Thanks for your comments and questions. May we quote you on that? (cmake is elegant in the extreme ... great tool) Of course. Since all the code I work with is published on multiple OSes, cmake is a godsend. I'm actively

Re: [CMake] CPack 101

2010-12-23 Thread Mike McQuaid
On 23 December 2010 22:05, David Cole david.c...@kitware.com wrote: Much easier on the eyes, much nicer in every respect except there's one extra file in your source tree now. Small price to pay for readability and future maintainability... Agreed. I think what would be even nicer would be to

Re: [CMake] CPack 101

2010-12-22 Thread Andreas Mohr
On Wed, Dec 22, 2010 at 04:15:07PM -0500, cmake-requ...@cmake.org wrote: Date: Wed, 22 Dec 2010 09:57:11 -0800 From: KC Jones kc.jo...@skype.net Subject: [CMake] CPack 101 And I just don't seem to get it. I know this is very possible. I know this is my own problem, first and foremost. So