Thank you, it worked.
On 2011-10-13 16:35, David Cole wrote:
As this grep from a Visual Studio build tree shows, the variables
containing "/O" compiler flags are the configuration-specific
variables:
$ grep "/O" CMakeCache.txt
CMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1
CMAKE_
Am Donnerstag, 13. Oktober 2011, 20:09:04 schrieb Michael Hertling:
> On 10/12/2011 03:40 PM, Rolf Eike Beer wrote:
> >> On 10/03/2011 09:18 AM, Yuri Timenkov wrote:
> >>> Hi Michael,
> >>>
> >>> On Sun, Oct 2, 2011 at 6:07 PM, Michael Hertling
> >>>
> >>> wrote:
> On 10/01/2011 10:07 AM, Yu
Hi cmake list!
I've been playing around with cmake for a couple of weeks now, and am
loving (almost) every minute of it. A thing I really like about cmake
and that I feel will add the greatest value for me, besides the
cross-platform capabilities, is the "build products go outside the
source tree"
On 10/13/2011 10:56 PM, Robert Dailey wrote:
> On Thu, Oct 13, 2011 at 3:47 PM, Michael Hertling wrote:
>
>> You might use an installation component for the concerned headers:
>>
>> CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
>> PROJECT(INSTCOMP C)
>> SET(CMAKE_VERBOSE_MAKEFILE ON)
>> SET(F_PR
On Thu, Oct 13, 2011 at 3:47 PM, Michael Hertling wrote:
> You might use an installation component for the concerned headers:
>
> CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
> PROJECT(INSTCOMP C)
> SET(CMAKE_VERBOSE_MAKEFILE ON)
> SET(F_PREFIX "/dev/shm" CACHE PATH "")
> FILE(WRITE ${CMAKE_BIN
I used
EXECUTE_PROCESS(COMMAND cmake -E copy_if_different ${SOURCE}
${CMAKE_BINARY_DIR}/${BASENAME}.cpp )
which is done when cmake is run (before vs builds)
only problem with this is that to update that souce you need to always
run cmake before build
On Thu, Oct 13, 2011 at 10:09 AM, Rob
On 10/13/2011 07:09 PM, Robert Dailey wrote:
> First of all I'm using cmake 2.8.6 and generating Visual Studio 2003
> projects with it.
>
> There is a particular project that needs to first copy its header files to a
> specific directory in a specific structure. After that, all other projects
> ne
On Thu, Oct 13, 2011 at 3:16 PM, David Cole wrote:
> On Thu, Oct 13, 2011 at 3:37 PM, Robert Dailey wrote:
> > In visual studio, there is a way to exclude a source file from the build
> on
> > a per-configuration basis (debug vs release). The actual VCPROJ looks
> like
> > this when you exclude
On Thu, Oct 13, 2011 at 3:37 PM, Robert Dailey wrote:
> In visual studio, there is a way to exclude a source file from the build on
> a per-configuration basis (debug vs release). The actual VCPROJ looks like
> this when you exclude a CPP file from the build for only DEBUG
> configuration:
>
> Re
In visual studio, there is a way to exclude a source file from the build on
a per-configuration basis (debug vs release). The actual VCPROJ looks like
this when you exclude a CPP file from the build for only DEBUG
configuration:
Is there a way in CMake to make it generate this? There has t
On Thursday 13 October 2011, Bernhard Sputh wrote:
> Hi Alexander,
>
> 2011/10/12 Alexander Neundorf :
> > Hi,
> >
> > On Wednesday 12 October 2011, Bernhard Sputh wrote:
> >
> > Cool :-)
> > Please create an entry in the bug tracker for that, so it doesn't get
> > lost.
>
> OK, will do this la
On 10/13/2011 08:26 AM, Yuri Timenkov wrote:
> See my comments inline.
>
> I could make an implementation proposal, but I don't have time till the end
> of November. So this discussion is quite pointless.
>
> On Wed, Oct 12, 2011 at 3:02 PM, Michael Hertling wrote:
>
>> On 10/03/2011 09:18 AM, Y
On 10/12/2011 03:40 PM, Rolf Eike Beer wrote:
>> On 10/03/2011 09:18 AM, Yuri Timenkov wrote:
>>> Hi Michael,
>>>
>>> On Sun, Oct 2, 2011 at 6:07 PM, Michael Hertling
>>> wrote:
>>>
On 10/01/2011 10:07 AM, Yuri Timenkov wrote:
> that's the problem: you don't know neither file name nor it's
>
> This works:
> set( project_count 0 CACHE INTERNAL "")
> function( define_project )
>math( EXPR count "${project_count}+1" )
>set( project_count ${count} CACHE INTERNAL "")
> endfunction()
> define_project()
> message(${project_count})
> define_project()
> message(${project_count})
> def
First of all I'm using cmake 2.8.6 and generating Visual Studio 2003
projects with it.
There is a particular project that needs to first copy its header files to a
specific directory in a specific structure. After that, all other projects
need to reference this project's source code from the insta
For now, no. ATTACHED_FILES uses a hard-coded file type:
type=\"file\"
(in CMake/Source/CTest/cmCTestTestHandler.cxx, line 1293 in today's 'next')
Instead of using ATTACHED_FILES, you could alternatively emit your own
NamedMeasurement text in the stdout output stream of your test
program. (Or
Hi,
I was looking around on the internet for how to attach files, specifically
images, to CDash submissions with CTest. I saw some other mailing list posts
related to it in which people said the attached files were showing up as plain
text instead of images on the dashboard.
The solution was
As this grep from a Visual Studio build tree shows, the variables
containing "/O" compiler flags are the configuration-specific
variables:
$ grep "/O" CMakeCache.txt
CMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG
CMAKE_CXX_FLA
Hi,
Comparing Xcode generator output to standard Xcode output...
If I look at a different project file (non CMake) which shows correct behavior,
a part of the project.pbxproj looks like:
...
/* Begin XCBuildConfiguration section */
1D6058940D05DD3E006BFB54 /* Debug */ = {
Hi all,
I would like to port a hardcoded build line from an old make file to my
CMakeLists.txt file for a fortran 90
project using ifort compiler.
The line is the following:
ifort *.o -o myexec -static-intel -Bstatic -lXm -Bdynamic -lXt
First, if I get it right (sorry for my ignorance but
Thanks Michael,
Just found it out myself as well (and yes, XCODE_ATTRIBUTE was the google
entry).
SET_TARGET_PROPERTIES( ${RT_APP_NAME} PROPERTIES
XCODE_ATTRIBUTE_CODE_SIGN_ENTITLEMENTS[variant=Debug]
${RT_IOS_CODE_SIGN_ENTITLEMENTS_DEBUG} )
SET_TARGET_PROPERTIES( ${RT_APP_NAME} PROPERTIES
XC
On 10/13/2011 02:26 PM, Daniel Dekkers wrote:
> Hi,
>
> How can I separate settings for different configurations in Xcode.
>
> As an example...
>
> SET_TARGET_PROPERTIES( ${APP_NAME} PROPERTIES
> XCODE_ATTRIBUTE_CODE_SIGN_ENTITLEMENTS ${IOS_CODE_SIGN_ENTITLEMENTS} )
>
> ... sets
Hi,
How can I separate settings for different configurations in Xcode.
As an example...
SET_TARGET_PROPERTIES( ${APP_NAME} PROPERTIES
XCODE_ATTRIBUTE_CODE_SIGN_ENTITLEMENTS ${IOS_CODE_SIGN_ENTITLEMENTS} )
... sets the same entitlement file for all four configurations (Debug, Re
> Hi everyone,
>
> I'm trying to compile in Windows an app that I have been working on in
> Ubuntu for a while.
>
> My problem is that FindBoost.cmake does not find my boost libraries even
> though they are in the system.
>
> I have them compiled with the compiler "vc71, vc80.and so on"
>
> I i
Hi everyone,
I'm trying to compile in Windows an app that I have been working on in
Ubuntu for a while.
My problem is that FindBoost.cmake does not find my boost libraries even
though they are in the system.
I have them compiled with the compiler "vc71, vc80.and so on"
I indicate in my cmak
Hi Alexander,
2011/10/12 Alexander Neundorf :
> Hi,
>
> On Wednesday 12 October 2011, Bernhard Sputh wrote:
> Cool :-)
> Please create an entry in the bug tracker for that, so it doesn't get lost.
OK, will do this later today.
> Since 2.8.5 the "ASM" language is the one to use for assembler fil
I have code like below:
IF(MSVC)
set(CMAKE_CXX_FLAGS /Ox)
set(CMAKE_C_FLAGS /Ox)
ENDIF(MSVC)
However, the flag is ignored and CMake generates projects that use /O2.
How can I fix it?
--
Twoje radio
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www
27 matches
Mail list logo
