I'm trying to get the entire hdf5 project compiling with the fortran stuff
enabled, but I've run into an issue
The solution has mixed fortran and c targets, and it adds dependency
information which includes the project file extension
cmVisualStudio10TargetGenerator::WriteProjectReferences ...
[mailto:cmake-developers-boun...@cmake.org] On Behalf Of Biddiscombe, John A.
Sent: 18 March 2011 14:19
Cc: cmake-developers@cmake.org
Subject: Re: [cmake-developers] VS2010 fortran composer
I'm trying to get the entire hdf5 project compiling with the fortran stuff
enabled, but I've run into an issue
If I create a cpp project with the IDE it goes into x64/Debug/blah, adding
fortran makes no difference and they both go into x64/Debug/blah
If I create a cpp project using cmake, it goes into debug/blah, adding a
fortran one puts the fortran one in x64/debug/blah, but the cpp one stays
behind.
On 3/11/2011 4:55 PM, Biddiscombe, John A. wrote:
If I create a cpp project with the IDE it goes into x64/Debug/blah,
adding fortran makes no difference and they both go into x64/Debug/blah
If I create a cpp project using cmake, it goes into debug/blah,
adding
a fortran one puts the fortran
On 3/10/2011 1:48 PM, Biddiscombe, John A. wrote:
It also has to match CMAKE_INTDIR, or tons of stuff will not work.
Can I change CMAKE_INTDIR from the generator since the fortran stuff uses its
own location (mostly)?
It has to be consistent with the C/C++ for mixed language projects.
What
Contrary to what I might have previously said ...(not sure if I did, but) ...
AFAICT if the cpp and fortran projects are all x64 configuration then
everything goes into x64/Debug or x64/Release.
(Mixing win32 and win64 causes trouble, but we don't care about that)
So changing CMAKE_INTDIR to
On 3/10/2011 3:09 PM, Biddiscombe, John A. wrote:
Contrary to what I might have previously said ...(not sure if I did, but) ...
AFAICT if the cpp and fortran projects are all x64 configuration then
everything goes into x64/Debug or x64/Release.
(Mixing win32 and win64 causes trouble, but we
If you create a new cpp project, by default it is win32 and visual studio puts
everything in debug/...
If you change platform to x64, then it goes into x64/debug/... even without any
fortran stuff added.
Adding fortran doesn't change anything.
JB
-Original Message-
From: Bill Hoffman
On 3/10/2011 4:36 PM, Biddiscombe, John A. wrote:
If you create a new cpp project, by default it is win32 and visual studio puts
everything in debug/...
If you change platform to x64, then it goes into x64/debug/... even without any
fortran stuff added.
Adding fortran doesn't change anything.
OK, that is odd... Is there a way to change that in the project files
that you generate?
Seems like it would be odd for the C/C++ stuff to end up in Debug, and
the fortran to be in X64/Debug...
It does not appear to be something I can control.
JB
Thanks
It's a bit of a hack, but testing for the target name and overriding the output
path seems to work.
This gets me past the trycompile step so now projects are being generated from
scratch.
if (this-Name==cmTryCompileExec) {
std::string path =
On 3/9/2011 1:49 PM, Biddiscombe, John A. wrote:
*Thanks*
**
*It’s a bit of a hack, but testing for the target name and overriding
the output path seems to work.*
*This gets me past the trycompile step so now projects are being
generated from scratch.*
**
*if (this-Name==cmTryCompileExec)
Using devenv.com, we're making progress - but the binary produced by
CMakeDetermineCompilerABI is in debug/bin and it's not looking there - does the
devenv do it differently from msbuild?
JB
C:\cmakebuild\fortrantestC:\cmakebuild\cmake\bin\Debug\cmake.exe
c:\Code\fortrantest -G Visual Studio
CMakeFiles\CMakeTmp\x64\Debug\cmTryCompileExec.exe
Apologies for the time lag, not at work this week. I realize I made a mistake
in the last post, it's the x64 in the path that's throwing it off.
JB
-Original Message-
From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
Sent: 08 March
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
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
26 matches
Mail list logo
