Am Freitag, den 08.05.2009, 20:10 +0200 schrieb Alexander Neundorf:
> On Thursday 07 May 2009, Micha Renner wrote:
> > If I use FIND_LIBRARY(_result name1), I have a strange effect, which I
> > do not understand.
> >
> > E.g FIND_LIBRARY(_result tiff) works as it should.
> >
> > FIND_LIBRARY(_resul
On Sun, May 10, 2009 at 5:08 PM, Alexander Neundorf wrote:
> The attached patch (against current cvs HEAD) changes the behaviour of set(
> CACHE) and option() slightly.
>
> Until now it behaves like this:
> if a variable FOO is set to a value, and then set FOO to a value in the
> CACHE,
> and FOO
On Sunday 19 April 2009, Eric Noulard wrote:
> 2009/4/19 Philip Lowman :
> > On Sun, Apr 19, 2009 at 1:56 PM, Eric Noulard
> >
> >> I think the "bug" is that you may define an option which overwrite an
> >> uncached var.
> >
> > This is exactly what I wanted to do though. In this case I don't car
2009/5/10 Tanguy Krotoff :
> btw you forgot to attach your unix example :p
I'm so used to the non-attached joined file :-)
--
Erk
file(GLOB filep "/home/eric/with*")
message("--${filep}--")
# switch next 2 lines comment to make it work.
file(TO_NATIVE_PATH "${filep}" file_native)
#set(file_nativ
On Sun, May 10, 2009 at 06:38:28PM +0200, Piotr Wyderski wrote:
> Yes, a lot of them: include directories specification,
> optimization flags (they also work as -D directives,
> e.g. they define __SSE2__ or not), language error
> handling mode (e.g. --Wno-pmf-conversion) etc.
> In fact I need the e
btw you forgot to attach your unix example :p
On Sun, May 10, 2009 at 7:19 PM, Eric Noulard wrote:
> 2009/5/10 Eric Noulard :
>> 2009/5/10 Tanguy Krotoff :
>>> Hello
>>>
>>> I'm pulling my hair out on what should be straightforward.
>>>
>>> file(TO_NATIVE_PATH ${file} file_native)
>>>
2009/5/10 Eric Noulard :
> 2009/5/10 Tanguy Krotoff :
>> Hello
>>
>> I'm pulling my hair out on what should be straightforward.
>>
>> file(TO_NATIVE_PATH ${file} file_native)
>> execute_process(
>> COMMAND type \"${file_native}\"
>> RESULT_VARIABLE result
2009/5/10 Tanguy Krotoff :
> Hello
>
> I'm pulling my hair out on what should be straightforward.
>
> file(TO_NATIVE_PATH ${file} file_native)
> execute_process(
> COMMAND type \"${file_native}\"
> RESULT_VARIABLE result
> OUTPUT_VARIABLE o
Tyler Roscoe wrote:
> Thinking about this more, is there anything handed off to the compiler
> that affects the preprocessor other than definitions (-D flags)?
Yes, a lot of them: include directories specification,
optimization flags (they also work as -D directives,
e.g. they define __SSE2__ or
On Sun, May 10, 2009 at 12:00:11PM +0200, Piotr Wyderski wrote:
> I've chceked those variables, but they provide not
> a very useful part of the command line, for example
> CMAKE_CXX_FLAGS_RELEASE gives me only
> -O3 -DNDEBUG.
>
> It is a very promising direction indeed, however
> after some hacki
On Sun, May 10, 2009 at 08:44:25AM -0700, Tron Thomas wrote:
> What is someone supposed to do after they create the patch?
Include it with the bug you open about this issue. Here is a bug with an
attached patch:
http://www.cmake.org/Bug/view.php?id=8967
tyler
Hello
I'm pulling my hair out on what should be straightforward.
file(TO_NATIVE_PATH ${file} file_native)
execute_process(
COMMAND type \"${file_native}\"
RESULT_VARIABLE result
OUTPUT_VARIABLE output
ERROR_VARIABLE e
Tyler Roscoe wrote:
On Sat, May 09, 2009 at 10:23:44PM -0700, Tron Thomas wrote:
What is involved in writing a patch?
This article looks like a pretty good summary if you have a Linux-like
environment available:
http://www.linuxforums.org/applications/using_diff_and_patch.html
tyler
2009/5/10 Eric Noulard :
> 2009/5/8 Eric Noulard :
>>> Ah, no problem. I was just thinking that there might be a bug. BTW,
>>> did you try the ECLIPSE_CDT4_GENERATE_SOURCE_PROJECT option?
>>
>> Yes it wokrs just fine.
>>
>>> It is no the nicest solution, but it works around the problem of the
>>> o
2009/5/8 Eric Noulard :
>> Ah, no problem. I was just thinking that there might be a bug. BTW,
>> did you try the ECLIPSE_CDT4_GENERATE_SOURCE_PROJECT option?
>
> Yes it wokrs just fine.
>
>> It is no the nicest solution, but it works around the problem of the
>> out-of-source builds with CVS sourc
2009/5/9 Alexander Neundorf :
> On Friday 08 May 2009, Eric Noulard wrote:
>> 2009/5/4 Miguel A. Figueroa-Villanueva :
> ...
>> > It is no the nicest solution, but it works around the problem of the
>> > out-of-source builds with CVS sources. It is described here:
>> >
>> > http://www.cmake.org/Wik
2009/5/10 Eric Noulard :
> 2009/5/9 Alexander Neundorf :
>> On Friday 08 May 2009, Eric Noulard wrote:
>>> Hi All CPack RPM users,
>>>
>>> Problems have been reported when using CPack RPM generator with
>>> rpm/rpmbuild version greater or equal than 4.6.0.
>>> (Fedora Core 10 or greater, Mandriva
On Sunday 10 May 2009, Eric Noulard wrote:
> 2009/5/9 Alexander Neundorf :
> > On Thursday 07 May 2009, Eric Noulard wrote:
> > ...
> >
> >> 1) Add more CPACK_RPM_XXX specific var such like:
> >> CPACK_RPM_POST_INSTALL_SCRIPT_FILE
> >> CPACK_RPM_POST_UNINSTALL_SCRIPT_FILE
> >>
> >> w
2009/5/9 Alexander Neundorf :
> On Friday 08 May 2009, Eric Noulard wrote:
>> Hi All CPack RPM users,
>>
>> Problems have been reported when using CPack RPM generator with
>> rpm/rpmbuild version greater or equal than 4.6.0.
>> (Fedora Core 10 or greater, Mandriva 2009 and greater, etc...)
>>
>> I
2009/5/9 Alexander Neundorf :
> On Thursday 07 May 2009, Eric Noulard wrote:
> ...
>> 1) Add more CPACK_RPM_XXX specific var such like:
>> CPACK_RPM_POST_INSTALL_SCRIPT_FILE
>> CPACK_RPM_POST_UNINSTALL_SCRIPT_FILE
>>
>> which may be used to specify the corresponding scripts
>> t
On Sunday 29 March 2009, Alexander Neundorf wrote:
> On Sunday 29 March 2009, Carlson Daniel wrote:
> > Yes, perhaps I already had some cmake generated build tree on my disk
> > when i tried this. I will try once again with a clean build tomorrow.
>
> Ok.
>
> > About the path-file: Does this really
Tyler Roscoe wrote:
> I don't know of a single place to gather all the flags CMake will pass
> to your compiler.
I've chceked those variables, but they provide not
a very useful part of the command line, for example
CMAKE_CXX_FLAGS_RELEASE gives me only
-O3 -DNDEBUG.
> get_target_properties() mi
22 matches
Mail list logo