Michael Hertling
writes:
>>> So you add global compiler flags which are not meant to be global? A usual
>>> person would say: "then do not set them globally!".
>>> It's really that simple...
>>
>> No, I want to replace those automatically setted by CMake.
>
> AFAIK, CMake doesn't set compilatio
On 03/14/2011 11:55 PM, Óscar Fuentes wrote:
> Hendrik Sattler
> writes:
>
>>> "The COMPILE_FLAGS property sets additional compiler flags used to build
>>> sources within the target."
>>>
>>> So it *adds* flags. I want to *set* flags, i.e. replace the existing
>>> ones.
>>
>> So you add global co
Hendrik Sattler
writes:
>> "The COMPILE_FLAGS property sets additional compiler flags used to build
>> sources within the target."
>>
>> So it *adds* flags. I want to *set* flags, i.e. replace the existing
>> ones.
>
> So you add global compiler flags which are not meant to be global? A usual
>
On Mar 14, 2011, at 4:19 PM, Belcourt, Kenneth wrote:
Hi David,
Oops, busted. The modules I loaded inserted an older version of
CMake, v2.8.1. When I run with my local copy of CMake 2.8.4, the
error goes away.
Sorry about the noise.
-- Noel
_
On 03/14/2011 06:42 PM, arrowdodger wrote:
> On Mon, Mar 14, 2011 at 7:16 PM, Michael Hertling wrote:
>
>> 2) If you collect the affected files in a separate directory - which is
>> probably recommendable anyway - you might set CMAKE_C_COMPILE_OBJECT,
>> CMAKE_C_CREATE_SHARED_LIBRARY, CMAKE_C_
Hi David,
On Mar 14, 2011, at 3:34 PM, David Cole wrote:
What is the cwd when your test starts?
The directory where the executable runs from (/scratch/trunk/tools),
not the directory containing the test input.
It should be ${Bwr_Dir} according to your email's WORKING_DIRECTORY
arg.
(wr
What is the cwd when your test starts?
It should be ${Bwr_Dir} according to your email's WORKING_DIRECTORY arg.
(write a little code that prints it out right at the top of the
program's main before doing anything else...)
What version of ctest is this? (I assume 2.8.4?)
> always cd to the worki
Thanks guys. It is doing it right.
Best Regards
Enrique
On Mon, Mar 14, 2011 at 3:22 PM, Enrique Izaguirre <
enrique.izagui...@gmail.com> wrote:
> OK, I couldn't even imagine that.
>
> Really appreciate, I'll make another try.
>
> Best Regards
>
> Enrique
>
>
>
> On Mon, Mar 14, 2011 at 3:09 PM
Hi,
The documentation states that the add_test() WORKING_DIRECTORY option
will run the test in the given directory. This add_test rule in my
CMakeLists.txt file:
add_test(
NAME bwr_melgen
WORKING_DIRECTORY ${Bwr_Dir}
COMMAND melgen.x ${Bwr_Dir}/_BWR_v2-0.inp
)
with ${Bwr_Dir} == /sc
On Monday 14 March 2011, Chatterjee, Shash wrote:
> Hi Alex,
>
> The included dirs and preprocessor symbols that are added, come from the
> CMake definitions, and are needed. The container defintion is different,
> it adds the dirs and symbols that are built-in to the
> compiler/pre-processor, and
On 14.03.11 15:04:54, Enrique Izaguirre wrote:
> Hi Alex,
>
> This is the whole output from the make. I can only see warnings:
>
> /bin/gcc-linux -DCOMDRIVER_EXPORTS -DBUILD_FIX_TMP -DFIX_WIN32 -DNO_ZIP
> -D_DEBUG -D_CONSOLE -I/home/x0148488/omapflash/cmake_build
> -I/home/x0148488/omapflash -I/
YOu have this argument to gcc:
-Werror
which means treat warnings as errors. Either remove the flag or fix the
warnings.
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
Enrique,
I think the -Werror flag is the problem:
http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
"-Werror
Make all warnings into errors."
hth,
tyler
On Mon, Mar 14, 2011 at 2:04 PM, Enrique Izaguirre
wrote:
> Hi Alex,
>
> This is the whole output from the make. I can only see warn
Hi Alex,
This is the whole output from the make. I can only see warnings:
/bin/gcc-linux -DCOMDRIVER_EXPORTS -DBUILD_FIX_TMP -DFIX_WIN32 -DNO_ZIP
-D_DEBUG -D_CONSOLE -I/home/x0148488/omapflash/cmake_build
-I/home/x0148488/omapflash -I/home/x0148488/omapflash/comdriver/inc
-I/home/x0148488/omapfl
On Monday 14 March 2011, Enrique Izaguirre wrote:
> Hello friends,
>
> I have a problem when I try to compile several files, for some reason it
> takes only the first of the list to build it.
> It displays a few warnings and at the end the following error:
>
> make[2]: *** [CMakeFiles/omap.dir/host
Thank you Eric. The section in the main CMakeLists.txt is as follows:
set (FILES "")
message ("Adding subdirectory host...")
include (host/CMakeLists.txt)
message ("FILES = ${FILES}")
foreach (FILE ${FILES})
set (hostFiles ${hostFiles} host/${FILE})
endforeach (FILE)
message ("hostFiles = ${
2011/3/14 Enrique Izaguirre :
> Hello friends,
>
> I have a problem when I try to compile several files, for some reason it
> takes only the first of the list to build it.
> It displays a few warnings and at the end the following error:
>
> make[2]: *** [CMakeFiles/omap.dir/host/fastboot.c.o] Error
Am Montag 14 März 2011, 16:35:21 schrieb Óscar Fuentes:
> Hendrik Sattler
>
> writes:
> > Zitat von Óscar Fuentes :
> >> There are target properties such as LINK_FLAGS and LINK_FLAGS_,
> >> but I don't see properties for setting compiler flags. This makes
> >> impossible to build two targets on t
Hello friends,
I have a problem when I try to compile several files, for some reason it
takes only the first of the list to build it.
It displays a few warnings and at the end the following error:
make[2]: *** [CMakeFiles/omap.dir/host/fastboot.c.o] Error 1
make[2]: Leaving directory `/home/x0148
On Mon, Mar 14, 2011 at 7:16 PM, Michael Hertling wrote:
> 2) If you collect the affected files in a separate directory - which is
> probably recommendable anyway - you might set CMAKE_C_COMPILE_OBJECT,
> CMAKE_C_CREATE_SHARED_LIBRARY, CMAKE_C_LINK_EXECUTABLE etc. as well
> as their CXX coun
On 03/14/2011 12:06 PM, Michael Wild wrote:
On 03/14/2011 04:46 PM, The Wanderer wrote:
Michael Wild's response appears to be correct. In the
CMakeLists.txt provided for the external project in question,
INSTALL_DIR is being explicitly set to ${CMAKE_INSTALL_PREFIX}.
This did not appear to be
On Mon, Mar 14, 2011 at 11:17 AM, Urbach, Marcel [Rohmann GmbH]
wrote:
> I have already tried to use the SCRIPT. But there is a problem to submit the
> name of the dll or the project name to the extern script. I need something
> like a parameter and I guess that doesn't exsist. Do you have any
On 03/14/2011 03:15 PM, arrowdodger wrote:
> Hello. I'm using CMake as build system for a C/CXX project and i've faced
> the following problem: I need to compile some sources as bytecode for VM.
> This is achieved by using different linker (with different flags) and,
> probably, different compiler.
On 03/14/2011 04:46 PM, The Wanderer wrote:
> On 03/14/2011 11:05 AM, Eric Noulard wrote:
>
>> 2011/3/14 The Wanderer :
>>
>>> (I apologize for setting the Reply-To header, but I know of no
>>> other way to prevent my being sent an additional off-list copy of
>>> any reply even when there is no sp
On 03/14/2011 11:05 AM, Eric Noulard wrote:
2011/3/14 The Wanderer :
(I apologize for setting the Reply-To header, but I know of no
other way to prevent my being sent an additional off-list copy of
any reply even when there is no specific need to draw my attention
to that reply.)
I am runni
Im using CPack with CMake 2.8 and when I am installing my app, I get the
message:
Warning! PATH too long installer unable to modify PATH!
Seems that Im not the first:
http://public.kitware.com/Bug/view.php?id=11931
Is this an acceptable limitation? Or is there something Im doing wrong?
I have a
Michael Wild writes:
> On 03/14/2011 12:42 AM, Óscar Fuentes wrote:
>> There are target properties such as LINK_FLAGS and LINK_FLAGS_,
>> but I don't see properties for setting compiler flags. This makes
>> impossible to build two targets on the same CMakeLists.txt with
>> different compiler flag
Hendrik Sattler
writes:
> Zitat von Óscar Fuentes :
>
>> There are target properties such as LINK_FLAGS and LINK_FLAGS_,
>> but I don't see properties for setting compiler flags. This makes
>> impossible to build two targets on the same CMakeLists.txt with
>> different compiler flags (I was told
Hi Alex,
The included dirs and preprocessor symbols that are added, come from the CMake
definitions, and are needed. The container defintion is different, it adds the
dirs and symbols that are built-in to the compiler/pre-processor, and the
scanner detects those within Eclipse/CDT. So, yes the
I have already tried to use the SCRIPT. But there is a problem to submit the
name of the dll or the project name to the extern script. I need something like
a parameter and I guess that doesn't exsist. Do you have any ideas to solve
this?
INSTALL(SCRIPT "PostInst.cmake" PARAMETeR...)
I also tr
On Mon, Mar 14, 2011 at 10:16 AM, Paul Baumer
wrote:
> Sorry for not being clear enough. I meant (2).
>
>> (2) included in the "Build Solution" command, executing after all
>> other targets have been built, so that "F7" or "Build All" will
>> actually build the INSTALL target?
>>
>
>
In CMake's C
2011/3/14 The Wanderer :
> (I apologize for setting the Reply-To header, but I know of no other way
> to prevent my being sent an additional off-list copy of any reply even
> when there is no specific need to draw my attention to that reply.)
> I am running cmake 2.8.2, installed via Debian testin
On 03/14/2011 03:37 PM, The Wanderer wrote:
> (I apologize for setting the Reply-To header, but I know of no other way
> to prevent my being sent an additional off-list copy of any reply even
> when there is no specific need to draw my attention to that reply.)
>
>
>
> I am running cmake 2.8.2,
(I apologize for setting the Reply-To header, but I know of no other way
to prevent my being sent an additional off-list copy of any reply even
when there is no specific need to draw my attention to that reply.)
I am running cmake 2.8.2, installed via Debian testing. No more recent
version appe
Sorry for not being clear enough. I meant (2).
(2) included in the "Build Solution" command, executing after all
> other targets have been built, so that "F7" or "Build All" will
> actually build the INSTALL target?
>
>
___
Powered by www.kitware.com
Vi
Hello. I'm using CMake as build system for a C/CXX project and i've faced
the following problem: I need to compile some sources as bytecode for VM.
This is achieved by using different linker (with different flags) and,
probably, different compiler. At the moment, the only solution i see is to
creat
Zitat von Óscar Fuentes :
There are target properties such as LINK_FLAGS and LINK_FLAGS_,
but I don't see properties for setting compiler flags. This makes
impossible to build two targets on the same CMakeLists.txt with
different compiler flags (I was told that the last value of
CMAKE__FLAGS_ ap
Do you mean:
(1) selected by default as the "startup project" when opening the
solution in Visual Studio?
or
(2) included in the "Build Solution" command, executing after all
other targets have been built, so that "F7" or "Build All" will
actually build the INSTALL target?
On Mon, Mar 14, 20
Hello,
I use cmake most of the time with Visual Studio. By default the INSTALL
target is not selected in the Configuration Manager for a cmake solution.
I would like to change this default. Any suggestions ?
P.S. If this needs to make some changes to the generators, I have no problem
with that e
On 03/14/2011 05:58 AM, Paulo Silva wrote:
> Hi,
>
> if I do
>
> set(PCHDIR ../include.pch)
> add_precompiled_header( ${PROJECT_NAME} ${PCHDIR}/pch.hpp )
>
> an extra ../ is added to PCHDIR. Isn't this a bug.
> However if I do
> set(PCHDIR ../../include.pch)
> or anything else nothing gets added
On 03/14/2011 12:42 AM, Óscar Fuentes wrote:
> There are target properties such as LINK_FLAGS and LINK_FLAGS_,
> but I don't see properties for setting compiler flags. This makes
> impossible to build two targets on the same CMakeLists.txt with
> different compiler flags (I was told that the last v
41 matches
Mail list logo
