I'm in the process of adding Cmake-build capability to a Fortran project that
currently follows a traditional recursive-make build structure. I've converted
all the makefiles to CMakeLists.txt files and can now produce all the target
libraries and executables with their dependencies correctly r
I just use:
set (CPACK_GENERATOR "ZIP")
and that seems to work.
I think those CPACK_BINARY_* variables you're setting are only
meaningful in CPack's context, not in CMake's (i.e. those vars are
what CMake writes out in CPackConfig.cmake for Cpack's later use).
hth,
tyler
On Fri, Mar 25, 2011 a
I have a project on OS X that I am using CMake 2.8.3 and generating makefiles.
When I do "make package" I get a .dmg, .sh, .stz and .zip files all created.
Here is what I think is the relative portion of my CPack code that gets
included in my CMakeLists.txt file:
SET(CPACK_BINARY_BUNDLE "OF
This should work, from an nmake command prompt:
mkdir build
cd build
set CC=C:/path/to/icl.exe
set CXX=C:/path/to/icl.exe
cmake -G "NMake Makefiles" ..\src
On Fri, Mar 25, 2011 at 1:02 PM, Andreas Fabri <
andreas.fa...@geometryfactory.com> wrote:
> Hello,
>
> Is there a generator for "nmake a
Hello,
Is there a generator for "nmake and icl.exe" on Windows.
I already tried to use the nmake generator and to set
the C and C++ compiler cmake variables, but that didn't
work either.
Any suggestion or help would be appreciated.
andreas
--
Andreas Fabri, PhD
Chief Officer, GeometryFactor
> Could you post the output of "make VERBOSE=1"?
>
> On *nix, the following CMakeLists.txt works as expected:
> The output of "make VERBOSE=1" contains:
>
>> .../c++ -DUNIX -o .../SetTargetProperties.cxx.o -c
>> .../SetTargetProperties.cxx
It is working properly now. I must not have done a 'make
Hi Alex,
>- CMakeFindEclipseCDT4.cmake : this is slightly changed version from the one
>shipped with cmake 2.8.4, it produces debug output. Please replace the
>CMakeFindEclipseCDT4.cmake in your cmake 2.8.4 installation with this file.
>Then create a fresh and empty build directory, and let cma
Hi Michael,
> AFAICS, this is not true, see cmFindBase::AddPathSuffixes(). The paths
> with the additional suffixes are searched first, but the paths without
> the suffixes are considered, too. Look at the following
CMakeLists.txt:
>
> CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
> PROJECT(PATH