Eric Noulard wrote:
I all,
I don't want to waste too much of our time on this
since I don't think it is a "must really have feature"
but I want to comment a little more.
So, the project I was concerned about is a CMake project, but does some
funny stuff with install script I think. Anyway I
I all,
I don't want to waste too much of our time on this
since I don't think it is a "must really have feature"
but I want to comment a little more.
2008/5/13 Bill Hoffman <[EMAIL PROTECTED]>:
> Alexander Neundorf wrote:
> We have projects that use it for non-cmake parts of the build. I don't
On Tuesday 13 May 2008, you wrote:
...
> We have projects that use it for non-cmake parts of the build. I don't
> want to break those projects. In fact, the project that funded CPack is
> the one I am most concerned about breaking.
There are these project-backwards-compatibility files. Could the
On Tuesday 13 May 2008, Bill Hoffman wrote:
> Alexander Neundorf wrote:
> > On Tuesday 13 May 2008, Bill Hoffman wrote:
> >> Eric Noulard wrote:
> >
> > ...
> >
> >>> Using absolute path install on unix is not a good idea either but
> >>> you sometimes have to use it to put you file in /etc/ .
> >>
Alexander Neundorf wrote:
On Tuesday 13 May 2008, Bill Hoffman wrote:
Eric Noulard wrote:
...
Using absolute path install on unix is not a good idea either but
you sometimes have to use it to put you file in /etc/ .
Be sure I'm not willing to break some backward compatibilty but
to avoid stra
On Tuesday 13 May 2008, Bill Hoffman wrote:
> Eric Noulard wrote:
...
> > Using absolute path install on unix is not a good idea either but
> > you sometimes have to use it to put you file in /etc/ .
> >
> > Be sure I'm not willing to break some backward compatibilty but
> > to avoid strange behavi
2008/5/13, Bill Hoffman <[EMAIL PROTECTED]>:
> >
> There is one more issue. CPack is supposed to work with any build system
> not just CMake. It might just be a set of hand crafted makefiles, and it
> may or may not support DESTDIR. I suppose this could be taken care of by
> only making DESTD
Eric Noulard wrote:
2008/5/13, David Cole <[EMAIL PROTECTED]>:
On Windows, where you have DESTDIR=C:/MyDir and an "absolute" install path
of "C:/Program Files/Whatever"
"C:/MyDir/C:/Program Files/Whatever" is probably going to make somebody a
bit grumpy...
Ok right, I see, DESTDIR and ABS
2008/5/13, David Cole <[EMAIL PROTECTED]>:
> On Windows, where you have DESTDIR=C:/MyDir and an "absolute" install path
> of "C:/Program Files/Whatever"
>
> "C:/MyDir/C:/Program Files/Whatever" is probably going to make somebody a
> bit grumpy...
Ok right, I see, DESTDIR and ABSOLUTE path shou
On Windows, where you have DESTDIR=C:/MyDir and an "absolute" install path
of "C:/Program Files/Whatever"
"C:/MyDir/C:/Program Files/Whatever" is probably going to make somebody a
bit grumpy...
Big picture perspective needed. Do not hastily change default behaviors.
On Tue, May 13, 2008 at
2008/5/13, Bill Hoffman <[EMAIL PROTECTED]>:
> Eric Noulard wrote:
>
> >
> Because for some projects DESTDIR may not work, and the default has been
> set. To change it would break existing projects.
Sorry about being pushy but in which kind of "project"
DESTDIR may not work?
More preciselty wh
Eric Noulard wrote:
Hi All,
I did examine a problem with CPack RPM generator which had
been reported by a user:
http://public.kitware.com/Bug/view.php?id=7000
The issue concerned file/target installed with absolute path name
which leads to the following error:
CMake Error at cmake_install.cmak
Hi All,
I did examine a problem with CPack RPM generator which had
been reported by a user:
http://public.kitware.com/Bug/view.php?id=7000
The issue concerned file/target installed with absolute path name
which leads to the following error:
CMake Error at cmake_install.cmake:40 (FILE):
file ca
13 matches
Mail list logo
