On Dec 2, 2010, at 04:35 , Michael Wild wrote:
> On 12/02/2010 10:18 AM, Marcel Loose wrote:
> On 30-11-2010 at 18:48, in message
>> <20101130174852.gc10...@cryptio.net>, Tyler
>> Roscoe wrote:
>>> On Thu, Nov 25, 2010 at 02:01:31PM +0100, Marcel Loose wrote:
>>> On 24-11-2010 at 17:45,
On 12/02/2010 10:18 AM, Marcel Loose wrote:
On 30-11-2010 at 18:48, in message
> <20101130174852.gc10...@cryptio.net>, Tyler
> Roscoe wrote:
>> On Thu, Nov 25, 2010 at 02:01:31PM +0100, Marcel Loose wrote:
>> On 24-11-2010 at 17:45, in message
>>> <20101124164507.gg23...@cryptio.net>, Ty
>>> On 30-11-2010 at 21:36, in message
<759ee5dc-038d-4c17-91da-98121049a...@mac.com>, S Roderick
wrote:
> On Nov 30, 2010, at 13:40 , David Cole wrote:
>
>> It probably works "accidentally" if you do the set before the
project
> command.
>
> That is what we do, and it definitely works for us.
>>> On 30-11-2010 at 18:48, in message
<20101130174852.gc10...@cryptio.net>, Tyler
Roscoe wrote:
> On Thu, Nov 25, 2010 at 02:01:31PM +0100, Marcel Loose wrote:
>> >>> On 24-11-2010 at 17:45, in message
>> <20101124164507.gg23...@cryptio.net>, Tyler
>> Roscoe wrote:
>> > On Wed, Nov 24, 2010 at
On Nov 30, 2010, at 13:40 , David Cole wrote:
> It probably works "accidentally" if you do the set before the project command.
That is what we do, and it definitely works for us. Set it _before_ the
PROJECT() statement.
>
> Unfortunately, the project command has significant side effects.
> Set
On Nov 30, 2010, at 16:03 , David Cole wrote:
> If we want this unintentional behavior to continue working as is into
> the future, we should add a test for this behavior and make the test
> fail if the value of CMAKE_INSTALL_PREFIX is not as expected at the
> bottom of CMakeLists...
I think it i
If we want this unintentional behavior to continue working as is into
the future, we should add a test for this behavior and make the test
fail if the value of CMAKE_INSTALL_PREFIX is not as expected at the
bottom of CMakeLists...
Anybody want to add some code to the test suite to validate this
pa
It probably works "accidentally" if you do the set before the project command.
Unfortunately, the project command has significant side effects.
Setting a default (cached) value for CMAKE_INSTALL_PREFIX might be one
of those...
On Tuesday, November 30, 2010, Tyler Roscoe wrote:
> On Thu, Nov 25,
On Thu, Nov 25, 2010 at 02:01:31PM +0100, Marcel Loose wrote:
> >>> On 24-11-2010 at 17:45, in message
> <20101124164507.gg23...@cryptio.net>, Tyler
> Roscoe wrote:
> > On Wed, Nov 24, 2010 at 12:11:56PM +0100, Micha Renner wrote:
> >>
> >> > SET(CMAKE_INSTALL_PREFIX "/foo/bar" CACHE PATH "Foo
> And *NEVER EVER* set CMAKE_INSTALL_PREFIX in your CMakeLists.txt file.
> That is a user-setting and you will make people angry at you if you
> override their choice in your code.
There is actually one single use-case where it might be useful to change this
variable once:
Say you have a library
>>> On 24-11-2010 at 17:45, in message
<20101124164507.gg23...@cryptio.net>, Tyler
Roscoe wrote:
> On Wed, Nov 24, 2010 at 12:11:56PM +0100, Micha Renner wrote:
>>
>> > SET(CMAKE_INSTALL_PREFIX "/foo/bar" CACHE PATH "Foo install
prefix")
>> >
>> > So, without the test to
CMAKE_INSTALL_PREFIX_
On Wed, Nov 24, 2010 at 12:11:56PM +0100, Micha Renner wrote:
>
> > SET(CMAKE_INSTALL_PREFIX "/foo/bar" CACHE PATH "Foo install prefix")
> >
> > So, without the test to CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT,
> > and without the FORCE option.
>
> No, as I mentioned, there was an article of
> SET(CMAKE_INSTALL_PREFIX "/foo/bar" CACHE PATH "Foo install prefix")
>
> So, without the test to CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT,
> and without the FORCE option.
>
> Reason: if someone unsets CMAKE_INSTALL_PREFIX on the command-line with
> -U, CMAKE_INSTALL_PREFIX will default to
>>> On 23-11-2010 at 15:37, in message
<1290523061.2001.8.ca...@gildemeister-2>,
Micha Renner wrote:
> Am Dienstag, den 23.11.2010, 15:01 +0100 schrieb Michael Wild:
>> On 11/23/2010 02:33 PM, Micha Renner wrote:
>> > Am Dienstag, den 23.11.2010, 14:01 +0100 schrieb
tomas...@sbc.su.se:
>> >> Dear
On Tuesday 23 November 2010, tomas...@sbc.su.se wrote:
> Dear Cmake users,
>
> 1) I am trying to set CMAKE_INSTALL_PREFIX in the CMakeLists file with
> SET(CMAKE_INSTALL_PREFIX, "my/path")
> but the variable remain unset; everything works fine if the variable is
> set on the command line when invok
Am Dienstag, den 23.11.2010, 15:01 +0100 schrieb Michael Wild:
> On 11/23/2010 02:33 PM, Micha Renner wrote:
> > Am Dienstag, den 23.11.2010, 14:01 +0100 schrieb tomas...@sbc.su.se:
> >> Dear Cmake users,
> >>
> >> 1) I am trying to set CMAKE_INSTALL_PREFIX in the CMakeLists file with
> >> SET(CMAK
On 11/23/2010 02:33 PM, Micha Renner wrote:
> Am Dienstag, den 23.11.2010, 14:01 +0100 schrieb tomas...@sbc.su.se:
>> Dear Cmake users,
>>
>> 1) I am trying to set CMAKE_INSTALL_PREFIX in the CMakeLists file with
>> SET(CMAKE_INSTALL_PREFIX, "my/path")
> ^
>
Am Dienstag, den 23.11.2010, 14:01 +0100 schrieb tomas...@sbc.su.se:
> Dear Cmake users,
>
> 1) I am trying to set CMAKE_INSTALL_PREFIX in the CMakeLists file with
> SET(CMAKE_INSTALL_PREFIX, "my/path")
^
No comma!
greetings
Micha
__
Dear Cmake users,
1) I am trying to set CMAKE_INSTALL_PREFIX in the CMakeLists file with
SET(CMAKE_INSTALL_PREFIX, "my/path")
but the variable remain unset; everything works fine if the variable is
set on the command line when invoking cmake
(-DCMAKE_INSTALL_PREFIX=my/path).
2) I am also looking
19 matches
Mail list logo
