The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11973
==
Reported By:Aaron Simmons
Assigned To:
Using 2.8.4, I'm trying to add an assembler file with cmake (64 bit VS2008
build), but I'm at a loss, I tried:
ENABLE_LANGUAGE(ASM_MASM)
IF(NOT CMAKE_ASM_MASM_COMPILER_WORKS)
MESSAGE(FATAL_ERROR No assembler found!)
ENDIF(NOT CMAKE_ASM-MASM_COMPILER_WORKS)
but the ml64 assembler does not seem
On Tue, Mar 15, 2011 at 1:44 AM, Michael Hertling mhertl...@online.dewrote:
To be exact, it's a rule variable which describes how to compile a C
source file to an object file. On my system, it currently expands to:
CMAKE_C_COMPILER DEFINES FLAGS -o OBJECT -c SOURCE
AFAIK, these rule
Hi David
Your solution works fine, but i still got the problem with execute_process.
Right now I use it this way:
#cmakelists.txt
ADD_LIBRARY(${project_name} SHARED ${sources} ${headers} ${idls} ${generated}
${resources} )
SET(project_out ${INSTALL_LIB_DIR}/${project_name}_d.dll)
STRING(REGEX
Robert Bielik skrev 2011-03-15 08:59:
Using 2.8.4, I'm trying to add an assembler file with cmake (64 bit VS2008
build), but I'm at a loss, I tried:
ENABLE_LANGUAGE(ASM_MASM)
IF(NOT CMAKE_ASM_MASM_COMPILER_WORKS)
MESSAGE(FATAL_ERROR No assembler found!)
ENDIF(NOT CMAKE_ASM-MASM_COMPILER_WORKS)
On 03/15/2011 09:53 AM, arrowdodger wrote:
On Tue, Mar 15, 2011 at 1:44 AM, Michael Hertling mhertl...@online.dewrote:
To be exact, it's a rule variable which describes how to compile a C
source file to an object file. On my system, it currently expands to:
CMAKE_C_COMPILER DEFINES FLAGS -o
2011/3/15 Robert Bielik robert.bie...@xponaut.se:
Robert Bielik skrev 2011-03-15 08:59:
Using 2.8.4, I'm trying to add an assembler file with cmake (64 bit VS2008
build), but I'm at a loss, I tried:
There has been a lot of work done (Alex and Brad I think) in topic
ReworkedAsmSupport
it has
Ralph Barth will be out of the office starting 15.03.2011 and will be
returning on 21.03.2011.
Ich werde Ihre Nachrichten nach meiner Rückkehr beantworten.
Deutsche Börse Systems AG
Chairman of the Supervisory
Hi,
My collegae has created the required patch for QtCreator 2.1.0 which
actually uses the defines created by the CMake patch.
Attached.
I'd apply a patch like that to Creator. (There are some minor issues with it
and it has to come via a merge request, but in general it does the right
Hi Alex,
Yes, that is correct, that one pathentry line added to .cproject is all that is
needed from the generator. The scanner simply detects the built-in symbols and
paths and sticks them in the container. Then, the container contribution has
to be added as part of the project paths.
Eric Noulard skrev 2011-03-15 10:36:
There has been a lot of work done (Alex and Brad I think) in topic
ReworkedAsmSupport
it has been merged to master last week.
May be you can try a nightly build
http://www.cmake.org/files/vCVS/cmake-2.8.4.20110314-gf52ca-win32-x86.exe
in order to see if this
I'm trying to use this in my CMake file for a simple executable:
SET_TARGET_PROPERTIES(
your_executable
PROPERTIES LINK_FLAGS /MANIFESTUAC:\level='requireAdministrator'
uiAccess='false'\)
This worked in vs2008, but not in vs2010. The project contains:
On Mon, Mar 14, 2011 at 6:54 PM, Belcourt, Kenneth kbe...@sandia.gov wrote:
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.
Generator expressions (like your TARGET_FILE_NAME:${project_name})
are only valid within the context of an add_custom_command call. Some
are also available from the newer signature of the add_test command.
See the docs for each of those for specific supported generator expressions.
In the
What are you going to do with it once it's in the value ARCH or x?
It's hard to see the literal contents of a cmake variable without
using in the message command.
This code:
set(x -DCMAKE_OSX_ARCHITECTURES=i386\\;x86_64)
message(${x})
produces this output:
On Tue, Mar 15, 2011 at 12:20 PM, Michael Wild them...@gmail.com wrote:
Just one warning: AFAIK these rule variables are only used for
Makefile-based generators, *NOT* for Xcode and VisualStudio and the
like. I'd prefer the route via add_custom_command/add_custom_target...
Michael
Oh,
Hi again,
I'm not sure if it is the time I posted this happened to be Sunday
that no one has read it or we simply cannot specify a precedence to
let cmake change its default sequence of searching for available
compilers?
Thanks,
Roc
On Fri, Mar 11, 2011 at 6:10 PM, rocwhite168
Hi,
Another add_test() question. I reuse the same test directory because
I run both Fortran and C executables on the same test and the input
files are so large that I don't want to replicate the entire test
hierarchy. The problem is that I need to remove files both before I
run the
I'm trying to add the vendor name ot the CPACK_NSIS_INSTALL_ROOT variable.
Right now, I have this line:
set( CPACK_NSIS_INSTALL_ROOT $PROGRAMFILES\Atmel)
Unfortunately policy CMP0010 keeps kicking in and warning me that \A is
invalid. I can't find any escape sequence that makes the
Hi,
On Tuesday 15 March 2011, Robert Bielik wrote:
Robert Bielik skrev 2011-03-15 08:59:
Using 2.8.4, I'm trying to add an assembler file with cmake (64 bit
VS2008 build), but I'm at a loss, I tried:
ENABLE_LANGUAGE(ASM_MASM)
IF(NOT CMAKE_ASM_MASM_COMPILER_WORKS)
MESSAGE(FATAL_ERROR
On Tuesday 15 March 2011, Daniel Teske wrote:
Hi,
My collegae has created the required patch for QtCreator 2.1.0 which
actually uses the defines created by the CMake patch.
Attached.
I'd apply a patch like that to Creator. (There are some minor issues with
it and it has to come via a
On Tuesday 15 March 2011, Chatterjee, Shash wrote:
Hi Alex,
Yes, that is correct, that one pathentry line added to .cproject is all
that is needed from the generator. The scanner simply detects the built-in
symbols and paths and sticks them in the container. Then, the container
Hello,
Sorry if this question is too primitive. I am trying to extract the
build dir into the source code by populating it in a variable in my
config.h file.
I do this by adding the following line in config.h.in
#cmakedefine PROJ_BUILD_DIR_CMAKEDEFINE ${PROJECT_BINARY_DIR}
In the config.h,
On 2011-03-15 16:26-0600 Balamurali Ananthan wrote:
Hello,
Sorry if this question is too primitive. I am trying to extract the build dir
into the source code by populating it in a variable in my config.h file.
I do this by adding the following line in config.h.in
#cmakedefine
Alexander Neundorf skrev 2011-03-15 21:19:
Assembler support works currently only in the makefile-based generators.
For having assembler supported in VisualStudio contributions from users are
needed (I don't have Windows, so I can't do that).
Thanks Alex, that pretty much explains it :) Ok,
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via a4219aa435a53fffd48a6cfba869819b9100cad2 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via d69220fb4894fe999eb6603a003347567003695f (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via b035e638c0948e99cd193d362dd6d125ecef3172 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 0e4b5caa81fe299ec619e004f33d2e26b0c3b404 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 3b6dbf71149c47e1e391e3e0663ae8476a7deaa9 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 9349de14c7c25bc1341c813cb040d6c4fad03453 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via c7278633a7acfc4afc9d7976dc522fb4027e8cd2 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 0554e5e50f6eb3117b4e207f4b01876dbe5a75a4 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 94f7d2e848c74b9f6c67e732a583bee812cb5502 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 01fb58738bac8a6e910c4344cbf400c385045e0b (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 73cd0c1e5e69806d4a4a76d1c27655d3d2e5a913 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 87ae722a5386b1560896b68d9c53b278ef655d9a (commit)
via
37 matches
Mail list logo
