I have a cmake setup that uses symlinks to place resource
files/directories/libraries relative to several different subcomponents
during the build process. This avoids excessive copying, and makes it
easier to build / test individual components. Something like this (*'s as
symlinks):
/build/comp
Did you try the workaround suggested in the first link you gave, i.e.
set( RatherLongLibraryName_GUID_CMAKE CACHE INTERNAL
"remove this and Visual Studio will mess up incremental builds")
On Sun, May 31, 2015 at 9:04 AM, wrote:
> Unfortunately, we're hitting an issue migrating from VS 2012 to
Unfortunately, we're hitting an issue migrating from VS 2012 to VS 2103 with
Cmake working with long target names.
Apparently the only know workarounds to the issues listed below is to shorten
target names but, we're working with fairly long set of projects and it's not
practical to rename the
Hi Falk!
I've read through the cl6x linker docs once again [1] SPRU187V Chapter 5,
page 137 and following.
>From my experience and the docs i'd say, yes you're right.
To prove the solution to your problem, see page 138:
"When you specify a library as linker input, the linker includes and links
Following your IOS instructions i get this error for the vtk Compile tools:
-- Build files have been written to: /Users/Guillaume/Downloads/VTK-6.2.0
[ 25%] Performing build step for 'vtk-compile-tools'
make[3]: *** No rule to make target `vtkCompileTools'. Stop.
make[2]: ***
[CMakeExternals/Pref
