Thanks' a lot!
From: David Cole [mailto:david.c...@kitware.com]
Sent: Monday, January 17, 2011 16:40
To: Dieter Oberkofler
Cc: CMake@cmake.org
Subject: Re: [CMake] Customize dependencies scanned by CMake
See this command:
http://cmake.org/cmake/help/cmake-2-8-docs
I'm using CMake 2.8.3 using makefiles for the OSX and Windows platform.
I very much like CMake but unfortunately the build performance consistently
causes some problems.
And the main performance problem is the absolutely correct but painfully
slow dependency checking.
In a large (Qt/C++) project
I'm having a hard time to understand why after upgrading from CMake 2.8.2 to
2.8.3 I get "the input line is too long" when running nmake.
The problem must be related to the upgrade because moving back to 6.8.2 with
the absolute same build environment works like a charm.
The error message seems to g
Hi!
I'm (once again) struggling with the creation of precompiled headers in
conjunction with gcc and Qt on the Apple platform.
When creating my precompiled header I use a code section based on
"PCHSupport_26.cmake" to extract the compile flags as follows:
--
STRING(TOUPPER "CMAKE_CXX_FLAG
Hi!
I'm (once again) struggling with the creation of precompiled headers in
conjunction with gcc and Qt on the Apple platform.
When creating my precompiled header I use a code section based on
"PCHSupport_26.cmake" to extract the compile flags as follows:
--
STRING(TOUPPER "CMAKE_CXX_FLAG
A couple of questions regarding the warning levels when compiling:
1) Is there a "preferred" way to change the warning level in CMake?
2) What is the default warning level CMake is using when compiling and how
can it be defined?
Thank you,
-D
___
Powered
> From: Tyler Roscoe [mailto:ty...@cryptio.net]
> Sent: Tuesday, September 29, 2009 19:45
> To: Dieter Oberkofler
> Cc: cmake@cmake.org
> Subject: Re: [CMake] CMAKE_SYSTEM not available
>
> On Tue, Sep 29, 2009 at 07:42:09PM +0200, Dieter Oberkofler wrote:
> > The installati
: Tuesday, September 29, 2009 18:36
> To: Dieter Oberkofler
> Cc: cmake@cmake.org
> Subject: Re: [CMake] CMAKE_SYSTEM not available
>
> On Tue, Sep 29, 2009 at 06:16:23PM +0200, Dieter Oberkofler wrote:
> > I seem unable to get/use the CMAKE_SYSTEM variable using CMake 2.6.4
> on t
I seem unable to get/use the CMAKE_SYSTEM variable using CMake 2.6.4 on the
Windows and Apple platform.
MESSAGE("CMAKE_SYSTEM=(" ${CMAKE_SYSTEM} ")") just shows an empty string
similar as does also CMAKE_SYSTEM_NAME, CMAKE_SYSTEM_VERSION and
CMAKE_SYSTEM_PROCESSOR.
Any ideas on what be the cause fo
> - Build
> - Test
> steps of a project.
Not yet but if they are as good as CMake is, I should probably have a look
at them.
Thank you for your comments and help.
-D
> -Original Message-
> From: Eric Noulard [mailto:eric.noul...@gmail.com]
> Sent: Wednesday, July
CHERS.
Thank you!
-D
> -Original Message-
> From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
> Sent: Wednesday, July 15, 2009 6:15 PM
> To: Eric Noulard
> Cc: Dieter Oberkofler; CMake@cmake.org
> Subject: Re: [CMake] Processing the output from CMake build
>
> Eric
ter and would be happy to learn
that what I'm doing is just no longer needed.
Thank you,
-D
> -Original Message-
> From: Eric Noulard [mailto:eric.noul...@gmail.com]
> Sent: Wednesday, July 15, 2009 2:12 PM
> To: Dieter Oberkofler
> Cc: CMake@cmake.org
> Subject: Re:
I might sound old fashioned but I'm still only building from the command
line and only use an IDE (XCode on Mac and VS on the PC) when debugging.
I therefore manually changed the CMake compile and link rules to always
generate an error file for each file that gets compiled or linked.
This is quite
Forget this post! (should have gone to the subversion list)
Sorry.
> -Original Message-
> From: Dieter Oberkofler [mailto:doberkofler.li...@gmail.com]
> Sent: Thursday, July 02, 2009 08:33
> To: 'CMake@cmake.org'
> Subject: Efficient way to create a new branch fr
The typical way how we create a new branch from a trunk is by copying the
trunk to a new branch on the server and then checkout the new branch to a
local working copy.
As this is a very common procedure, I was wondering if this can eventually
also be done in a more efficient/fast way.
Is there way
Hi,
is there a way (in CMake) to convert a relative directory (e.g.
/a/b/c/../../d/e) to an abolsute one (e.g. /a/d/e)?
Thank you,
Dieter
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opens
@gmail.com
> Cc: CMake@cmake.org
> Subject: Re: [CMake] CMP0005 warning as default
>
> Dieter Oberkofler wrote:
> > The warning offers a lot of information on how to disable but is it
> > really intended to get the following warning by default?
> >
> > --
The warning offers a lot of information on how to disable but is it really
intended to get the following warning by default?
--
CMake Warning (dev) at cmake/Definitions.cmake:51 (ADD_DEFINITIONS):
Policy CMP0005 is not set: Preprocessor definition values are now escaped
automatically.
t; upgrade from 2.4.6 to 2.6.3
>
> Dieter Oberkofler wrote:
> > I have been digging into this issue and found out that the problem
> > might be cause by the following command that might have
> changed it's
> > behaviour in CMake 2.6.4 == SET(
there now a better way to generate a file (*.ler in my example) with
the output of the linker?
Thank you for your help!
-Dieter
> -Original Message-
> From: Dieter Oberkofler [mailto:doberkofler.li...@gmail.com]
> Sent: Saturday, April 25, 2009 10:47 PM
> To: '
rade from 2.4.6 to 2.6.3
>
> Dieter Oberkofler wrote:
> > I'm also having problems with a library in the format
> > "D:\MyDev\ljs_app\trunk\tools\..\xvt\win\lib\tls12dvc71".
> > This library was successfully processed in CMake 2.4.6 but
> when using
&
5, 2009 9:19 PM
> To: doberkofler.li...@gmail.com
> Cc: CMake@cmake.org
> Subject: Re: [CMake] Problem with NMake generator after
> upgrade from 2.4.6 to 2.6.3
>
> Dieter Oberkofler wrote:
> > I'm also having problems with a library in the format
> > "
berkofler.li...@gmail.com
> Cc: CMake@cmake.org
> Subject: Re: [CMake] Problem with NMake generator after
> upgrade from 2.4.6 to 2.6.3
>
> Dieter Oberkofler wrote:
> > Thank you for your quick feedback!
> >
> > 1) Why does this warning appear in the first place
l.hoff...@kitware.com]
> Sent: Saturday, April 25, 2009 3:22 PM
> To: doberkofler.li...@gmail.com
> Cc: CMake@cmake.org
> Subject: Re: [CMake] Problem with NMake generator after
> upgrade from 2.4.6 to 2.6.3
>
> Dieter Oberkofler wrote:
> > After having upgraded CMake f
After having upgraded CMake from 2.4.6 to 2.6.3 I received the following
warning
==
...
-- The C compiler identification is MSVC
-- The CXX compiler identification is MSVC
CMake Warning at C:/Program Files/CMake
2.6/share/cmake-2.6/Modules/Platform/Windows-cl.cmake:32 (ENABLE_LANGUAGE):
You need to do the SET calls *before* the ADD_EXECUTABLE calls. The
ADD_EXECUTABLE uses the current value of those variables to configure an
Info.plist file for a bundle app...
HTH,
David
On Fri, Apr 18, 2008 at 3:23 AM, Dieter Oberkofler
<[EMAIL PROTECTED]> wrote:
I'm using CMake 2
I'm using CMake 2.4.4 on the Apple OSX platform and have problems in getting
CMake to generate correct bundles when specifying more then one target
executable.
In principle my CMakeLists.txt file looks as follows:
...
ADD_EXECUTABLE(LJS_001, MACOSX_BUNDLE ...)
SET(MACOSX_BUNDLE_BUNDLE_NAME LJSAppl
Our SVN repository is growing very quickly and we are starting to have
problems with the backup of the fully repository and would therefore like to
reduce it in size by reorganizing it. What are the best practices (in order
of importance) to:
1) Physically remove branches and tags that are no longe
D]
Cc: cmake@cmake.org
Subject: Re: [CMake] How to generate compiler error files with CMake
Dieter Oberkofler wrote:
> When compiling an individual file (file.cpp), I would like to have an
> error file (file.err) containing all errors generated during the
compilation.
> Is there an easy way
When compiling an individual file (file.cpp), I would like to have an error
file (file.err) containing all errors generated during the compilation.
Is there an easy way to generate a compiler error file (next to the stdout)
for each individual file compiled using CMake?
Thankk you,
Dieter
___
Can someone help on where I could find the release notes for 2.4.7 ?
Cheers,
Dieter
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
I'm having some problems when using the OUTPUT_NAME property in an Apple OSX
bundle.
1) It seems as if SET_TARGET_PROPERTIES( PROPERTIES OUTPUT_NAME
) would append the name to the current CMAKE_CURRENT_BINARY directory
instead of replacing the output name with a fully specified filename name.
On th
Original Message -------
dieter oberkofler wrote:
Is is somehow possible to convince CMake to compile (use the
build-in c/c++
compile rules and no explicit custom command) without having
specified a
LIBRARY
Is is somehow possible to convince CMake to compile (use the build-in c/c++
compile rules and no explicit custom command) without having specified a
LIBRARY or EXECUTABLE to be build?
-dieter
___
CMake mailing list
[EMAIL PROTECTED]
http://www.cmake.org
Is it possible to force CMake into using a specific object output directory
when compiling (c/c++) source files?
-dieter
___
CMake mailing list
[EMAIL PROTECTED]
http://www.cmake.org/mailman/listinfo/cmake
Is it possible to set a CMake variable on the CMake command line (-D
MYVAR:BOOL=ON) without having CMake caching this variable automatically?
Cheers,
Dieter
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
d to do in
order to have this addition moved into the main trunk of CMake?
Best regards
Dieter Oberkofler
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
To your feedback:
1) We are very much used to have one error file for each source file because
this is how our editor (good old CodeWrite) expects to get the errors and
because it is very convenient to check the results after a complete build.
Especially if run on a remote server or as a distribut
Hi!
I'm new to CMake and have ONE big question:
How can I force CMake to create error files for the output of each
individual compile or more general für the build rules?
(e.g.: gcc ... file.cpp > file.err)
Thank you in advance
-Dieter
___
CMake mailing
39 matches
Mail list logo
