Hi,
My CMake file contains the install comands like this
install(TARGETS MyExe RUNTIME DESTINATION .)
When I use the standard NSIS template, the installer is created with
"MyExe". But our project needs a custom NSIS template so I have written
one, and it is generating an installer *without* MyEx
The problem disappeared now. I suspect some application (may be the
antivirus or a virus) was keeping that file
("C:/Users/user1/Desktop/xyz/abc-1.0.0-win32.exe")
open.
On Tue, Mar 25, 2014 at 3:33 PM, Lloyd wrote:
> Hi,
>
> I am using CPack (CMake) with Visual Studio 2010. When I "build" Packa
Hi All,
The way the cross-compiling is described with a separated file with the
cross-compilation is working
set(COMPILER_PATH /opt/Xilinx/SDK/2013.4/gnu/arm/lin/bin/)
set(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_SYSTEM_VERSION 1)
set(CMAKE_SYSTEM_PROCESSOR arm)
# specify the cross compiler
set (CM
I am proud to announce the CMake 3.0 third release candidate.
Sources and binaries are available at:
http://www.cmake.org/files/v3.0/?C=M;O=D
Documentation is available at:
http://www.cmake.org/cmake/help/v3.0
Release notes appear below and are also published at
http://www.cmake.org/cmake/
Hi everybody,
I am currently working on a cmake-buildsystem for a project that
exposes a plugin-interface. This plugin-interface also targets
make-based buildsystems and therefore I wanted to generate a small
makefile-fragment that contains appropriate CFLAGS, LDFLAGS etc. that
should be used to c
I noticed that stack overflow checking is still enabled in release modes;
Is there an option somehow to disable stack checking always(?) or I dunno
I figure stack checking is a debugging feature, and release should run in
an optimal mode.
Also is there a way to select linking against static runt
