summaryrefslogtreecommitdiffstats
path: root/Source/cmVisualStudio10TargetGenerator.cxx
diff options
context:
space:
mode:
authorBill Hoffman <bill.hoffman@kitware.com>2011-08-03 21:24:43 (GMT)
committerBill Hoffman <bill.hoffman@kitware.com>2011-08-03 21:24:43 (GMT)
commit3c53fbb1f0d7276d0ef1f07facb2a1d937fc5153 (patch)
treef73fa1e39ea2396eb041ce680d67d4bd15cd5486 /Source/cmVisualStudio10TargetGenerator.cxx
parent6c72d25aee92c6cd412c79969b7b18a814ac99cb (diff)
downloadCMake-3c53fbb1f0d7276d0ef1f07facb2a1d937fc5153.zip
CMake-3c53fbb1f0d7276d0ef1f07facb2a1d937fc5153.tar.gz
CMake-3c53fbb1f0d7276d0ef1f07facb2a1d937fc5153.tar.bz2
Fix custom commands in VS2010 Fortran projects using CFG_INTDIR and test.
For custom commands in VS2010 Fortran projects the INTDIR variable is different than in the rest of the solution because Intel fortran still uses the old VS project files even in VS2010. So, we replace $(Configuration) directly in the project files. I have also added a FortranOnly test that tests this feature and is run on any generator that has Fortran abilities.
Diffstat (limited to 'Source/cmVisualStudio10TargetGenerator.cxx')
-rw-r--r--Source/cmVisualStudio10TargetGenerator.cxx7
1 files changed, 7 insertions, 0 deletions
diff --git a/Source/cmVisualStudio10TargetGenerator.cxx b/Source/cmVisualStudio10TargetGenerator.cxx
index d710405..183399f 100644
--- a/Source/cmVisualStudio10TargetGenerator.cxx
+++ b/Source/cmVisualStudio10TargetGenerator.cxx
@@ -1563,6 +1563,13 @@ void cmVisualStudio10TargetGenerator::WriteProjectReferences()
i != depends.end(); ++i)
{
cmTarget* dt = *i;
+ // skip fortran targets as they can not be processed by MSBuild
+ // the only reference will be in the .sln file
+ if(static_cast<cmGlobalVisualStudioGenerator*>(this->GlobalGenerator)
+ ->TargetIsFortranOnly(*dt))
+ {
+ continue;
+ }
this->WriteString("<ProjectReference Include=\"", 2);
cmMakefile* mf = dt->GetMakefile();
std::string name = dt->GetName();