Hello there.
Compiling open source project OpenCV-2.3.1 on Windows works with cmake 2.8.9.
The other day I updated to cmake 2.8.10, and it stopped working. If I go back
to cmake 2.8.9 it works again.
Has anyone seen this or can anyone point me in the right direction to start
investigating? I'm
Hi,
To download the common file(s) at configure time, you could follow the
approach discussed here:
http://cmake.3232098.n2.nabble.com/is-it-possible-to-download-CMake-modules-at-configure-time-td7583968.html#a7584113
Hth
Jc
On Mon, May 13, 2013 at 6:17 PM, Matthew Woehlke <
matthew.woeh...@kit
On 2013-05-11 17:22, Shlomi Fish wrote:
many of my CMake-based projects carry a common top-level "Common.cmake" file
that I copy from one project to another and enhance, and since this is
duplicate code/functionality I would like to consolidate it.
What I want to be able to do is say something l
Hi,
I currently have a CMake project with multiple sub-projects where
the sub-projects are libraries and executables. The project works on
windows and iOS (via XCode). One such sub-project is an executable that can
only be run on OSX and must be run after every build. This executable makes
a few c
I'm converting a Fortran package that was using GNU make to build to CMake, but
I've run into a problem compiling F90 module code where the source code is
stored under many directories.
The package has a directory structure
src/
src/dir1
src/dir2
:
:
Each dir* has *.F f
Hi,
I'm using the current WinCE support in the nightly build to build
various things through cmake generated VS2008 solutions. I wondered
about not beeing able to set the correct entry point for my executables
until I debugged the issue. The VS generator used always outputs
hardcoded EntryPoi
