the hdf5 project uses a custom command to generate a C file from a previously
compiled exe.
it looks like this
#-
# Setup the H5Detect utility which generates H5Tinit with platform
# specific type checks inside
Forgot to ask : Is it possible that ctest is capturing the std out stream,
passing it into a std::iostream and the extra eol is being added there?
JB
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Biddiscombe, John A.
Sent: 05 August 2011 12:11
To: cmake@cmake.org
David
Yes, it's probably an intermediate (make, shell?) interpreting the output
along the way.
does that mean it's a bug?
You can try to add VERBATIM to the custom command call and see if that helps.
Nope. Same result. I think verbatim just leaves the args untouched rather than
the output.
...@cmake.org] On Behalf Of
Biddiscombe, John A.
Sent: 05 August 2011 14:34
To: David Cole
Cc: cmake@cmake.org
Subject: Re: [CMake] odd cmake/DOS bug/issue with eol
David
Yes, it's probably an intermediate (make, shell?) interpreting the output
along the way.
does that mean it's a bug?
You can try
Project A creates a target which links to hdf5 using the hdf5 cmake generated
cmake file which lists the imported location for the debug lib as hdf5d.lib
SET_TARGET_PROPERTIES(hdf5 PROPERTIES
IMPORTED_LINK_INTERFACE_LANGUAGES_DEBUG C
IMPORTED_LINK_INTERFACE_LIBRARIES_DEBUG
Sure, when project A is loaded into project B it either needs to search and
load the hdf5 cmake file or require that to be done in project B before loading
project A. Then the hdf5 target will be known in project B too and linking will
work fine.
Using find_package in project B is an option,
When using the install target command as follows
INSTALL (
TARGETS
${HDF5_LIB_TARGET}
EXPORT
${HDF5_EXPORTED_TARGETS}
LIBRARY DESTINATION lib COMPONENT libraries
ARCHIVE DESTINATION lib COMPONENT libraries
RUNTIME DESTINATION bin COMPONENT
] On Behalf Of
Biddiscombe, John A.
Sent: 07 June 2010 17:25
To: cmake@cmake.org
Subject: [CMake] ${PROJECT}-config.cmake
When using the install target command as follows
INSTALL (
TARGETS
${HDF5_LIB_TARGET}
EXPORT
${HDF5_EXPORTED_TARGETS
I'm sure someone has a better answer ... but ...
I have complete control over the test
program and can make it output whatever I want.
Have a look at the XML produced by ctest itself and generate it yourself? then
submit it and you should see each test separately
(Just thinking out loud)
JB
All in all it'd be much nicer if there was some kind of hook in ctest which
could be used to inform it that a number of tests had been run, and let it
populate and submit the XML report based on that information. But, if there's
any way to do that, it's highly undocumented...
It doesn't
-boun...@cmake.org] On Behalf Of
Michael Hertling
Sent: 08 June 2010 23:34
To: cmake@cmake.org
Subject: Re: [CMake] ${PROJECT}-config.cmake
On 06/07/2010 05:24 PM, Biddiscombe, John A. wrote:
When using the install target command as follows
INSTALL (
TARGETS
I tried and failed to generate working project files for the Fortran 12
compiler with Visual Studio 2010. (NMake works ok)
Has anyone else tried with success ?
If not ... is there any possibility of CMake Developers targeting the New Intel
tool suite in the near future?
I'd like to have a go
The latest 1.8.5.x release branch of svn is CMake friendly and you shouldn't
have this trouble is you're willing to recompile/install it
Something along these lines will work for an installation on win32 into
/program file/HDF5
FIND_PACKAGE(HDF5 1.8.5 REQUIRED NO_MODULE PATHS
When using ifort on windows I do the following
a) Make sure cmake is launched from inside a cmd prompt with the
ifort-vars.bat set so that the ifort compiler is on the path etc etc
b) always use nmake makefiles to do the initial configure and detection
c) once the project is
If I install using this kind of stuff
INSTALL (
FILES ${PROJECT_BINARY_DIR}/H5pubconf.h
DESTINATION ${HDF5_INSTALL_INCLUDE_DIR}
COMPONENT headers
)
and
INSTALL (
EXPORT ${HDF5_EXPORTED_TARGETS}
DESTINATION
There are some examples of usage in the hdf5 1.8.5/6 cmakelists files. Google
should find you a download location and if you then look in the fortran sub
directory there's some examples there.
JB
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Does fortran (intel 11.x integration) work in the latest MSVC 2010 supported
version. I tried several months back but the fortran project generator was not
upgraded so I dropped back to 2008. Has any progress been made?
thanks
JB
___
Powered by
First off, I just upgraded to cmake 2.8.4 (from 2.8.2) and the visual studio +
intel fortran support is much much better. Thank you whoever fixed it up.
Projects generate correctly and build out of the box
(Intel Fortran 10.x + visual studio 2008) - previously I had to generate nmake
makefiles
BIll,
Kitware has not had the funding or access to a Fortran compiler that
works with VS 2010. So, that has not yet been implemented.
I've got two projects that are using fortran heavily, so I may have a go at
fixing up the generator.
If I were to spend a few days improving the fortran
You compile cmake etc on the platform on which you are working (XT5 etc) and
then do things as usual. here's a snippet from some instructions I made about a
year ago for our xt5 (I've not tried this on BG)
begin snip
To actually run the tests : in ccmake configuration, ensure that the
...@cmake.org] On Behalf Of
Biddiscombe, John A.
Sent: 22 February 2011 08:51
To: Bill Hoffman; cmake@cmake.org
Subject: Re: [CMake] Fortran good and bad
BIll,
Kitware has not had the funding or access to a Fortran compiler that
works with VS 2010. So, that has not yet been implemented.
I've got two
I think that the cmVisualStudio10TargetGenerator.cxx would be the most
likely place for the fortran support to be added. They should be close
to what is done in the cmLocalVisualStudio7Generator for fortran support.
OK, that's what I ended up doing. I generated a simple fortran project using
First off, I'd like to say thanks to whoever is responsible for the huge
improvements in Fortran support in cmake-1.8.0. I've got most of the hdf5
Fortran testing framework essentially running smoothly on win32 intel visual
fortran 11.x - no changes necessary to the default Fortran flags and
Rather than try to explain, have a look at this one I made earlier it
inherits stuff from the parent project, but you should see what’s going on.
http://gitorious.org/hdf5/hdf5-v18/blobs/master/fortran/CMakeLists.txt
scroll down until you see
I am in the process of switching the hdf5 library used by paraview from the
older 1.6.x to the newer 1.8.x and I encountered a problem caused by the fact
that the new variable
CMAKE_LIBRARY_OUTPUT_DIRECTORY
is set by hdf1.8.x when included in the paraview main project - and it
overrides the
The command
INSTALL(
TARGETS ${PROJ_LIB_NAME}
EXPORT proj-targets
LIBRARY DESTINATION lib
ARCHIVE DESTINATION lib
RUNTIME DESTINATION bin
)
Works very nicely, when 'make install' is invoked, is there a way of achieving
a similar result which is generated in the build directory -
Michael
Thank you. That seems to do what I need.
JB
You can use
export(TARGETS target ...
[NAMESPACE namespace]
[APPEND]
FILE output_file
)
which you can then include() in your dependent project.
Michael
___
Powered by
Brad
Great. Thanks very much for looking at it.
JB
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: 02 December 2009 17:57
To: Biddiscombe, John A.
Cc: cmake@cmake.org
Subject: Re: [CMake] Fortran name mangling
Brad King wrote:
My guess is that CMake
Whilst setting up a dashboard for ParaView using windows + MPI, I noticed that
a number of tests always fail because the executable is not found. I find that
CMake code such as this
ADD_TEST(ParallelIso-image
${VTK_MPIRUN_EXE} ${VTK_MPI_PRENUMPROC_FLAGS} ${VTK_MPI_NUMPROC_FLAG} 2
-developers-boun...@paraview.org [mailto:paraview-developers-
boun...@paraview.org] On Behalf Of Biddiscombe, John A.
Sent: 15 December 2009 11:31
To: paraview-develop...@paraview.org
Cc: cmake@cmake.org
Subject: [Paraview-developers] CMake ParaView parallel testing on windows
Whilst setting up
Clint,
Nice. This works perfectly (or at least as far as I can tell so far).
Thanks a lot
JB
-Original Message-
From: Clinton Stimpson [mailto:clin...@elemtech.com]
Sent: 15 December 2009 15:51
To: Biddiscombe, John A.
Cc: paraview-develop...@paraview.org; cmake@cmake.org
given a config like this
TARGET_LINK_LIBRARIES(${KIT}CxxTests vtkIO vtkImaging vtksys)
I have the trouble that vtksys pulls in a whole bunch of DynamicLoader stuff
(kwsys) - which apart from being rather odd when building statically, forces
the linker to need -ldl added to the link line.
The
Bill
Does ParaView itself not
link static on linux?
In general no not really. On our Cray we have no dynamic lib support and this
kind of thing is very painful. On other machines even if you turn off shared
libs, in actual fact, the final exe does pull in all the system libs as shared
Michael/Bill
JB
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Biddiscombe, John A.
Sent: 04 March 2010 16:46
To: Bill Hoffman
Cc: cmake@cmake.org
Subject: Re: [CMake] static library link order
Bill
Does ParaView itself
We have a project where the data generated is very large and too costly to
store permanently, so we'd like to be able to
a) Tag the source code used when the run is initiated using the SCM
(svn/git etc)
b) Automatically store all the user configured CMake options (using cmake
There will be a new FindHDF5.cmake?
How will my CMakeLists.txt change?
I planned on spending a bit of time on resolving a few last CMake+HDF5 issues
before the 1.8.5 branch of hdf is closed (I believe April 15). I had planned on
looking at FindHDF5.cmake as clearly a new one will be
Within paraview we wish to build hdf5, which is now cmake based, so we
ADD_SUBDIRECTORY(blah) and hdf5 is compiled nicely with lib targets added to
the build.
Some settings (like lib names) are needed by the host project, so we want to
SET(HDF5_CONFIG
I can't seem to find a way of installing the compiled mod files from a mixed
fortran/C/C++ project (on windows and linux).
I can see all the mod files in ${CMAKE_Fortran_MODULE_DIRECTORY}, but various
attempts to install them after compilation fail.
My closest effort looks something like this
Kelly
First, I wrote a set of macros that would determine the how FC names module
files (evidently there is no standard naming scheme) by using the
try_compile() macro.Next, I created a macro that would take a list of
Fortran sources and return a list of 'predicted' module file names
I had a lot of trouble with cmake and VS 2010 due to the IDE crashing when
projects were regenerated by cmake and having to click reload millions of times.
Can anyone tell me if things are better with visual studio 2012? I want to
upgrade some projects, but will delay a while if I know these
I'm working on a big project with both VS2010 and VS2012, I don't have such
problems.
Now I use VS2012 almost only and to me it seems faster to load.
Thanks. that’s good to know.
(I suspect that because I do a lot of cmakelists.txt editing on large projects
that I get hit harder than most by
: Biddiscombe, John A.; cmake@cmake.org
Subject: Re: [CMake] cmake + VS 2012
The Visual Studio addin is from vscommands.com and is mentioned in this bug
report on the issue:
http://public.kitware.com/Bug/view.php?id=11258
As you can tell from reading through the notes, we never did find
I don't understand why this stripped down test gives the wrong results. Can
anyone point out what I've done wrong. I'm using cmake 2.8.9
Thanks
JB
=== TEST cmake ===
include (CMakeParseArguments)
MACRO(ADD_TEXT_TEST)
CMAKE_PARSE_ARGUMENTS(
TEST
NAME;COMMAND;ARGSLIST;BASELINE
Eric
Thanks for pointing that out, the help docs I was looking at didn't mention
multi_value_keywords, with that added it works as expected.
Cheers
JB
From: Eric Clark [mailto:ecl...@ara.com]
Sent: 19 October 2012 19:17
To: Biddiscombe, John A.
Cc: CMake Mailing List (cmake@cmake.org
Eric
Do you happen to know what docs you were looking at? It may be worth a little
bit to post that to this mailing list so that hopefully the person that wrote
those docs could be so kind as to update them with the correct syntax.
I can't find the ones I was looking at before. But hopefully
I don't really understand what these policies are for, but I always get the
error message in the title when I include cmake generate config files which
contain push pop such as the following example
== cmakelists
cmake_minimum_required(VERSION 2.8)
project(TEST)
# makes no
Ward
Currently, using find_package(HDF5 NO_MODULE) results in Visual Studio
attempting to link against the shared libraries (.dll) themselves, instead of
the associated import libraries (.lib). I'm still trying to figure out why
this is, exactly, but in the mean time I am using the
Just to follow up my earlier mail,
HDF5_C_LIBRARY C:/Program Files/HDF5/bin/hdf5_D.dll
Instead of
HDF5_C_LIBRARY C:/Program Files/HDF5/bin/hdf5_D.lib
Should have read
HDF5_C_LIBRARY C:/Program Files/HDF5/lib/hdf5_D.lib
To fix the problem a bit more obustly.
Trying to fix that left me with a
Sorry if this is off topic for the list.
If I
ctest –D ExperimentalStart
ctest –D ExperimentalTest –R test1
ctest –D ExperimentalSubmit
Then
ctest –D ExperimentalStart
ctest –D ExperimentalTest –R test2
ctest –D ExperimentalSubmit
It appears as two entries on the dashboard, but I’d like to have
time stamp tag, and all that follows
should be associated with the most recent start's tag.
HTH,
David C.
On Sep 5, 2014, at 5:07 PM, Biddiscombe, John A. biddi...@cscs.ch
wrote:
Sorry if this is off topic for the list.
If I
ctest –D ExperimentalStart
ctest –D ExperimentalTest –R test1
David
OK, understood.
Currently, the buildbot is running 145 unit tests, then 52 regression
tests in separate steps, every dashboard line has +145 and -52
respectively so the +/- numbers can’t get much worse!
My dashboard is 1.8.2 which dates back a few years. Just seeing the
red/green (and one
The dashboard I'm setting up is so helpful. Thanks cdash/ctest people.
After a submit, is it possible to get the ID so that I can generate URLs that
point to the test fails (because the buildbot is on another site and I'd like
to generate links back to the dashboard on it)
example URL :
I have a project which generates a project-config.cmake file and a
project-config-version.cmake file in the relevant place,
When another project tries to find_package it, I receive this message from cmake
Found package configuration file:
Nils
I wasn’t setting xxx_FOUND at all - and I never resolved this problem, but
it went away on its own after I made some changes to various config files
etc.
Thanks anyway.
JB
On 16/09/14 18:08, Nils Gladitz nilsglad...@gmail.com wrote:
On 16.09.2014 17:38, Biddiscombe, John A. wrote
If a projX is installed to
~/apps/projX
And when installed it creates
projXConfig.cmake
projXConfigVersion.cmake
projXTargets-debug.cmake
projXTargets.cmake
etc.
In ~/apps/projX/lib/cmake/projX
It is necessary to say
cmake –Dprojx_DIR=~/apps/projX/lib/cmake/projX …..
When configuring another
Using Mac OSX 10.9.5 and Eclipse Luna, I am unable to debug projects generated
with cmake.
Although the debugger stops on int main, I can’t get manually set breakpoints
to work (they used to work with a previous install – possibly earlier eclipse).
It always reports, “No source file named ….
Nils
Marvellous. Just what I needed. Works like a charm. and only 5 minutes between
posting my question and getting the answer.
Many thanks indeed
JB
From: Nils Gladitz [mailto:nilsglad...@gmail.com]
Sent: 14 January 2015 13:17
To: Biddiscombe, John A.; cmake@cmake.org
Subject: Re: [CMake
Hello list
I've got some test scripts which are called with test names and such like and I
am using cmake expansion of vars to get from this
$TARGET_FILE:${framework}_server
to
$TARGET_FILE:hg_test_server
which is correct. But unfortunately, when I use
file(WRITE stuff containing above
When generating Xcode projects on OSX, for larger projects I get this error
when I attempt to open them (smaller/simpler ones seem to be ok).
In one particular example the Xcode generated project is approx 14MB in size.
Does anyone know of any tools to diagnose what is wrong with the generated
Robert
Have you tried setting CMAKE_PREFIX_PATH
That seems to work. I will use it from now on.
Thanks
JB
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake
is?
thanks
JB
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Biddiscombe, John A.
Sent: 21 July 2015 14:54
To: cmake@cmake.org
Subject: [CMake] find_package and lib/cmake/Foo
I've asked this before, but never resolved it...
if I stall package Foo into
CMAKE_INSTALL_PREFIX=/my/path
I've asked this before, but never resolved it...
if I stall package Foo into
CMAKE_INSTALL_PREFIX=/my/path/prefix
and generate
/my/path/prefix/lib/cmake/Foo/FooConfig.cmake
etc
then with
Foo_DIR=/my/path/prefix
Foo_ROOT=/my/path/prefix
find_package(Foo)
does not find package Foo
One needs to
Magnus
>
Wouldn't a better solution be to use an options file, something like ld's
@file[1]?
<
Yes. That solution would require me to make some probably significant changes
to the cmake internals though, and I hoped to find out where the extra path /
directories were coming from and shorten
Alex
Thank you for this information. I shall test this out right away.
Yours
JB
-Original Message-
From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net]
Sent: 14 January 2016 23:17
To: cmake@cmake.org
Cc: Biddiscombe, John A.
Subject: Re: [CMake] cdash/ctest question
On Thursday
Apologies for posting a cdash question question to the cmake list…
CDash plots the run-time of tests, which is very useful indeed, but it would be
even more useful if one could output a performance related ‘time’ from a test
where a specific feature was being benchmarked and one could see how
When building OpenBLAS on OSX, the link line generated contains around 350K of
text, and the max supported arg length is
getconf ARG_MAX - returns 262144.
This causes the link phase to abort with
Error running link command: Argument list too long
The reason for the problem is that many
My system updated cmake to 3.10.1 and now findpackage(mpi) is now unusable
After trying everything I can think of, I have ended up with this, but it still
does not find mpi as the trycompile step fails to build a test mpi due to
missing mpi.h
It used to be so simple. I do not want to use
I have a problem with exported flags from a project.
If I use `target_compile_options(hpx PUBLIC ${flags})` hpx is compiled with the
flags, and all 500+ tests within the project that depend on hpx inherit the
flags too, so they get built correctly. However, the `HPXTargets.cmake` file
that is
Marc
Thank you. That fixes it.
JB
From: Marc CHEVRIER [marc.chevr...@gmail.com]
Sent: 09 October 2018 09:52
To: Biddiscombe, John A.
Cc: cmake@cmake.org
Subject: Re: [CMake] target_compile_flags and PUBLIC
Have a look at '$' and '$'
generator expressions.
Le
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).
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
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
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
[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
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
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,
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
90 matches
Mail list logo
