to be a VS problem rather than a cmake one. I will investigate
elsewhere.
Thanks for the suggestion and sorry for the noise.
JB
On 11/09/15 20:15, "Brad King" <brad.k...@kitware.com> wrote:
>On 09/11/2015 08:38 AM, Biddiscombe, John A. wrote:
>> I have been having probl
Using cmake 3.3.1
I have been having problems with projects in VS14 and it appears to be caused
by the generation of paths used by/in the IDE
D:\Code\hvtkm\vtkm\vtkm/worklet/GaussianSplatter.h
whereas it used to always be
D:\Code\hvtkm\vtkm\vtkm\worklet\GaussianSplatter.h
Note the forwardslash
May I ask one question related to the Target Usage Requirements ...
For HDF5 (for example), the user might enable Parallel IO, which requires MPI.
When enabled, the hdf5 cmakelists use find_package to get MPI and all is fine.
Users of hdf5 might not know that they are using an hdf which has
One important extra point.
The MPI library was NOT built with cmake, but the HDF5 and the user's project
would be. Not sure if that makes a difference
JB
From: Biddiscombe, John A.
Sent: 22 April 2013 16:46
To: 'Stephen Kelly'; cmake-developers@cmake.org
Subject: RE: [cmake-developers] CMake
] On Behalf Of Stephen Kelly
Sent: 22 April 2013 16:35
To: cmake-developers@cmake.org
Subject: Re: [cmake-developers] CMake 2.8.11-rc3 ready for testing!
Biddiscombe, John A. wrote:
May I ask one question related to the Target Usage Requirements ...
For HDF5 (for example), the user might
ready for testing!)
Brad King wrote:
On 04/22/2013 10:46 AM, Biddiscombe, John A. wrote:
C:\Program Files\hdf5-1.8.11\cmake\hdf5\hdf5-config.cmake
find_package(HDF5 NO_MODULE)
then the user’s project has a ‘hidden’ dependency on mpi
In similar cases (in VTK and ITK) we have the package
I think I hit the wrong key and my email disappeared, apologies if you get this
twice
The package config file should have only declarative effects and not
actually modify the loading project's build, so that advice was correct.
Understood. This seems sensible.
The _INCLUDE_DIRS, _LIBRARIES,
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
[mailto:bill.hoff...@kitware.com]
Sent: 10 March 2011 23:03
To: Biddiscombe, John A.
Cc: cmake-developers@cmake.org
Subject: Re: VS2010 fortran composer
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
to x64/etc ought to be allowed yes? If so, where does
it happen - or rather where can I do it?
JB
-Original Message-
From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
Sent: 10 March 2011 20:03
To: Biddiscombe, John A.
Cc: cmake-developers@cmake.org
Subject: Re: VS2010 fortran composer
[mailto:bill.hoff...@kitware.com]
Sent: 10 March 2011 21:53
To: Biddiscombe, John A.
Cc: cmake-developers@cmake.org
Subject: Re: VS2010 fortran composer
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
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
- if there's a better way I'll no doubt find out
eventually ...
JB
From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
Sent: 09 March 2011 13:54
To: Biddiscombe, John A.
Cc: cmake-developers@cmake.org
Subject: Re: RE: VS2010 fortran composer
http://software.intel.com/en-us/forums/showthread.php?t=80773
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
2011 14:22
To: Biddiscombe, John A.
Cc: cmake-developers@cmake.org
Subject: Re: VS2010 fortran composer
On 3/8/2011 6:41 AM, Biddiscombe, John A. wrote:
Using devenv.com, we're making progress - but the binary produced by
CMakeDetermineCompilerABI is in debug/bin and it's not looking
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
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)
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
\BuildLog.htm
1cmTryCompileExec - 0 error(s), 0 warning(s)
== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==
JB
-Original Message-
From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
Sent: 07 March 2011 15:42
To: Biddiscombe, John A.
Cc: cmake-developers@cmake.org
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).
21 matches
Mail list logo
