I've made some progress on a Fortran Composer generator for VS2010
If I create a fortran project, I can load it in the IDE and everything works
OK, but in order to do this I must detect the fortran compiler first. I am
doing this by running cmake using nmake makefiles, then changing the
Nick,
We are using a modification on your patch internally.
Few things
1) It breaks projects that have resources. Fix is to attach the Executable
to only the 'copy to cmake build dir' phase. Even after the mailinglist
discussion I'm unsure of the need for this?
XCode basically claims it is a
and wow, the patch I just sent is broken because cmXCodeObject-Print() has
sideffects! :(
Will send a patch that fixes -Print() when I have some extra time.
/Johan
On Mon, Mar 7, 2011 at 1:33 PM, Johan Björk p...@spotify.com wrote:
Nick,
We are using a modification on your patch internally.
On Mon, Mar 7, 2011 at 6:58 AM, Biddiscombe, John A. biddi...@cscs.ch wrote:
I've made some progress on a Fortran Composer generator for VS2010
If I create a fortran project, I can load it in the IDE and everything works
OK, but in order to do this I must detect the fortran compiler first. I
No. The cmake generated project is identical to the one I create using visual
studio - and both compile fine inside the IDE
but both give the same error when I try to compile using MSBuild
here is the outpur from a simple TestApp generated using the IDE (New Project
etc etc)
http://software.intel.com/en-us/forums/showthread.php?t=81140
This is explained in the release notes for the Fortran compiler.
Please read the section on VS2010..
John, do you have the release notes?
On Mon, Mar 7, 2011 at 8:57 AM, Bill Hoffman bill.hoff...@kitware.com wrote:
On Mon, Mar 7,
Bill
What if you run DevEnv.exe from the command line with the /Upgrade on
the vfproj file? Does it change it? Does it work with MSBuild after?
No change. Still fails.
http://software.intel.com/en-us/forums/showthread.php?t=81140
This is explained in the release notes for the Fortran
On Mon, Mar 7, 2011 at 9:17 AM, Biddiscombe, John A. biddi...@cscs.ch wrote:
Bill
What if you run DevEnv.exe from the command line with the /Upgrade on
the vfproj file? Does it change it? Does it work with MSBuild after?
No change. Still fails.
I tried the /Upgrade with devenv.exe and it did nothing.
After reading more intel forum posts I discover that the fortran projects
cannot be built using msbuild. Intentional at some levele.
But I realized that I should be using devenv.com not devenv.exe
C:\Program Files (x86)\Microsoft Visual
I just tried this on a remote machine with the compiler and can confirm what
John is seeing. That said. If you run msbuild on the top level solution you
get a slightly more informative error.
c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1msbuild
Console1.sln
Microsoft (R) Build
On Mon, Mar 7, 2011 at 10:13 AM, Biddiscombe, John A. biddi...@cscs.ch wrote:
I tried the /Upgrade with devenv.exe and it did nothing.
After reading more intel forum posts I discover that the fortran projects
cannot be built using msbuild. Intentional at some levele.
But I realized that I
Or, maybe only use it for fortran, but that would be hard...
Ah. That was going to be my next question. I wanted to know how to get the
cmTarget object inside the GenerateBuildCommand function, because I need to
tell it to use vfproj instead of vcxproj (since I'm using different
extensions).
On Mon, Mar 7, 2011 at 10:29 AM, Biddiscombe, John A. biddi...@cscs.ch wrote:
Or, maybe only use it for fortran, but that would be hard...
Ah. That was going to be my next question. I wanted to know how to get the
cmTarget object inside the GenerateBuildCommand function, because I need to
On Mon, Mar 7, 2011 at 10:35 AM, Bill Hoffman bill.hoff...@kitware.comwrote:
On Mon, Mar 7, 2011 at 10:29 AM, Biddiscombe, John A. biddi...@cscs.ch
wrote:
Or, maybe only use it for fortran, but that would be hard...
Ah. That was going to be my next question. I wanted to know how to get
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=11937
==
Reported By:Daniel R. Gomez
Assigned To:
On Friday 04 March 2011, Brad King wrote:
On 03/03/2011 05:04 PM, Alexander Neundorf wrote:
On Thursday 03 March 2011, Brad King wrote:
Hi Alex,
The Sun compiler still fails:
http://www.cdash.org/CDash/testDetails.php?test=85204365build=888421
It's because the execute_process in the
The following issue has been SUBMITTED.
==
http://cmake.org/Bug/view.php?id=11938
==
Reported By:strcasecmp
Assigned To:
Usually there are 2 ways: 1) put them into separate directories (like Debug
and Release), probably specifying different output directories or 2) use
different file names, say adding suffixes like D, or d8.
BTW, what's the point to have different configurations in the same workspace
(do you
On 03/06/2011 12:12 PM, Gabriel Petrovay wrote:
Hi,
Is there a way to read the arguments that were passed to CMake from
inside a CMakeLists.txt file?
There is a problem that some generators (like NMake Makefiles) set a
default value for certain variables (like CMAKE_BUILD_TYPE=Debug,
Hi,
I just wanted to read the documentation on
CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT, but discovered
that the variable is not listed in the cmake docs.
Is there a reason for this? Should I open a bugreport on it?
Cheers,
Johannes
--
Johannes Zarl
Virtual Reality Services
Johannes
On 03/07/2011 11:33 AM, Michael Hertling wrote:
On 03/06/2011 12:12 PM, Gabriel Petrovay wrote:
Hi,
Is there a way to read the arguments that were passed to CMake from
inside a CMakeLists.txt file?
There is a problem that some generators (like NMake Makefiles) set a
default value for
Thanks for the tips, Michael.
We will do so, using project specific BUILD_TYPE and INSTALL_PREFIX.
Gabriel
On Mon, Mar 7, 2011 at 12:20 PM, Michael Hertling mhertl...@online.de wrote:
On 03/07/2011 11:33 AM, Michael Hertling wrote:
On 03/06/2011 12:12 PM, Gabriel Petrovay wrote:
Hi,
Is
On 03/07/2011 12:37 PM, Gabriel Petrovay wrote:
Thanks for the tips, Michael.
We will do so, using project specific BUILD_TYPE and INSTALL_PREFIX.
However, the downside of this approach is that your project's users
should not refer to the well-known CMake variables CMAKE_BUILD_TYPE
and
In order to build the project the users have to land on a doku page or
a README.FIRST anyway. There we can give the command instead of
documenting how this behaves with different generators. So I think
this is a good tradeoff.
On Mon, Mar 7, 2011 at 1:06 PM, Michael Hertling mhertl...@online.de
On 3/7/2011 1:14 AM, Rolf Eike Beer wrote:
In my solution I have several samples, some of which are windows based
while other are console based.
So I need to be able to change the link flag /SUBSYSTEM:CONSOLE (or
/SUBSYSTEM:WINDOWS) depending on the executable I'm building
Am I missing something
On Monday 07 March 2011, Johannes Zarl wrote:
Hi,
I just wanted to read the documentation on
CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT, but discovered
that the variable is not listed in the cmake docs.
Is there a reason for this?
It's an internal variable.
Should I open a bugreport on
I looked at the code and the possibility of introducing a policy to
allow the alternate behavior. Looks quite straight forward, so I ask:
What is the policy on adding policies?
Aaron C. Meadows
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Meadows, Aaron C.
Any progress on it ? One more information, this n900-devel image uses
internally qemu and I am not sure that can cause any issue for the
build system.
That is also interesting why the debian packaging worked just fine in
the scratchbox using also qemu internally.
Best Regards,
Laszlo Papp
On
Hi,
Try putting set(CMAKE_USER_MAKE_RULES_OVERRIDE MyCompilerFlags) before
project() command.
Then, override variable CMAKE_BUILD_TYPE_INIT (with plain unconditional set
command, without putting into cache) in MyCompilerFlags.cmake file (make
sure you put it into location CMake can reach).
2011/3/7 Laszlo Papp djsz...@archlinux.us:
Any progress on it ?
Nope.
I won't be very responsive this week.
One more information, this n900-devel image uses
internally qemu and I am not sure that can cause any issue for the
build system.
I don't like I said I'm not that experienced with
On Mon, Mar 7, 2011 at 9:11 PM, Eric Noulard eric.noul...@gmail.com wrote:
2011/3/7 Laszlo Papp djsz...@archlinux.us:
Any progress on it ?
Nope.
I won't be very responsive this week.
That does not sound too good.. !
One more information, this n900-devel image uses
internally
As said, the working OBS spec files can be found here:
http://repo.pub.meego.com/home:/sandst1/standard/armv7l/
http://repo.pub.meego.com/home:/sandst1/standard/i586/
http://djszapi.homelinux.net/gluon.spec - this is the cpack/cmake
generated one.
Well, the cpack one doesn't really do anything,
On Friday 04 March 2011, Campbell Barton wrote:
On Thu, Mar 3, 2011 at 5:10 PM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
On Tuesday 01 March 2011, Campbell Barton wrote:
On Tue, Mar 1, 2011 at 2:47 PM, Marcus D. Hanwell
marcus.hanw...@kitware.com wrote:
On Tue, Mar 1, 2011
My first subject line was Who decided to break FindITK.cmake in
2.8.4? but that isn't probably very tactful.
We have a whole bunch of projects that used to configure and build
just fine with CMake 2.8.3. With 2.8.4 they fail.
The error message we get is:
CMake Error at
I have several compilers setup on my box for various reasons.
I definately know this shows up when building for mingw and using the
wrong command prompt with say visual studio in the path, and gcc not
in the path.
First, I create a new build output directory go into that directory
and run a
I have been looking at this webpage:
http://www.kitware.com/products/html/CDashSubprojects.html. I have created a
Project.xml file to list my subprojects. Right now I am just trying to use
Project.xml to add subprojects to a dashboard. I am trying to submit the file
to the dashboard like so:
Further news, I have just tried the rpm generation on my host system
out and it worked like a charm, here are the logs:
http://djszapi.homelinux.net/cpack_host.log
http://djszapi.homelinux.net/gluon_host.spec
I hope it helps with something...
Best Regards,
Laszlo Papp
On Mon, Mar 7, 2011 at
On Mon, Mar 7, 2011 at 7:03 PM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
It's an internal variable.
May we use it? Or is it not intended for users to use it?
--
MSc Gabriel Petrovay
Mobile: +41(0)787978034
www.28msec.com
___
Powered by
2011/3/7 Laszlo Papp djsz...@archlinux.us:
As said, the working OBS spec files can be found here:
http://repo.pub.meego.com/home:/sandst1/standard/armv7l/
http://repo.pub.meego.com/home:/sandst1/standard/i586/
Not really, since binary RPMs do not contains the spec file,
but I did find the spec
Well: http://public.kitware.com/Bug/view.php?id=11595
That is fixed in cmake 2.8.4.
Changelog: http://www.cmake.org/pipermail/cmake/2011-February/042839.html
CPackRPM fix bug 0011595 : Can't generate RPMs (on FC11...)
I am trying to build this version now on MeeGo since the available
binary one
2011/3/8 Laszlo Papp djsz...@archlinux.us:
Well: http://public.kitware.com/Bug/view.php?id=11595
That is fixed in cmake 2.8.4.
Changelog: http://www.cmake.org/pipermail/cmake/2011-February/042839.html
CPackRPM fix bug 0011595 : Can't generate RPMs (on FC11...)
I am trying to build this
On Tue, Mar 8, 2011 at 12:45 AM, Eric Noulard eric.noul...@gmail.com wrote:
2011/3/8 Laszlo Papp djsz...@archlinux.us:
Well: http://public.kitware.com/Bug/view.php?id=11595
That is fixed in cmake 2.8.4.
Changelog: http://www.cmake.org/pipermail/cmake/2011-February/042839.html
CPackRPM fix bug
1st run:
ca
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX
2011/3/8 Laszlo Papp djsz...@archlinux.us:
On Tue, Mar 8, 2011 at 12:45 AM, Eric Noulard eric.noul...@gmail.com wrote:
2011/3/8 Laszlo Papp djsz...@archlinux.us:
Well: http://public.kitware.com/Bug/view.php?id=11595
That is fixed in cmake 2.8.4.
Changelog:
Hi,
I am starting a separate thread on this hanging issue.
-- Forwarded message --
From: Laszlo Papp xx
Date: 2011/3/8
Subject: Re: [CMake] CPack and RPM packages
To: Eric Noulard eric.noul...@gmail.com
Cc : CMake ML cmake@cmake.org
1st run:
ca
-- The C compiler
Are you calling ctest_start(Experimental) or ctest_start(Nightly) before
callng ctest_submit...?
On Mon, Mar 7, 2011 at 4:32 PM, Zou, Di (Cont, ARL/CISD) di@us.army.mil
wrote:
I have been looking at this webpage:
http://www.kitware.com/products/html/CDashSubprojects.html. I have created
1) What is the hackaround to install the newest version on arm ?
2) What is the final solution ? I think there are severe thread issues
debug output contains almost the same information as the normal, not
much addition...
Should I open a bugreport instead with critical priority ? Put it
Hi guys,
Good news -- the system admins are installing 2.8.4 on all the government Cray
machines!
Bad news -- I can't actually get anything to work. I pulled the git repo
version and built the master branch because of what David pointed out. However,
I cannot figure out how to make it
I could not still build cmake.. But I did this modification
locally you suggested and that is the output:
CPack: Create package using RPM
CPack: Install projects
CPack: - Run preinstall target for: Gluon
CPack: - Install project: Gluon
CPack: Create package
CPackRPM: Will use GENERATED spec
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 be9af61f723194d6efd5cf20254b8935e49b8bac (commit)
from
50 matches
Mail list logo