Philip Lowman wrote:
Neal Meyer wrote:
Is there any particular reasoning why for a shared library project the
.dll file is created in the LibraryOutputPath rather then the
ExecutableOutputPath. The Import library(.lib) should be placed in
the LibraryOutputPath, but it doesn't make any sense
Josef Karthauser wrote:
Hello again,
I'm wondering what the best way to going about producing make files
and visual studio files at the same time is. I want to use nmake to
build my tree, but want visual studio project files so that the
developers can continue to with within the visual
Josef Karthauser a écrit :
Hello again,
I'm wondering what the best way to going about producing make files and
visual studio files at the same time is. I want to use nmake to build
my tree, but want visual studio project files so that the developers can
continue to with within the visual
Hello again,
I'm wondering what the best way to going about producing make files and
visual studio files at the same time is. I want to use nmake to build
my tree, but want visual studio project files so that the developers can
continue to with within the visual studio environment, which would
-Original Message-
From: Torsten Martinsen [mailto:[EMAIL PROTECTED]
Sent: 01 October 2007 14:43
To: Josef Karthauser; Cmake Mailing List
Subject: RE: [CMake] Building both make files and visual studio files.
Josef Karthauser wrote:
Hello again,
I'm wondering what the best
On 2007-10-01 11:30+0200 Maik Beckmann wrote:
I opened a bug-report as a repository for patches and a place for discussions
on this issue:
http://www.cmake.org/Bug/view.php?id=5809
please join to...
... contribute patches,
... test the patches,
... report things which doesn't work,
...
Hi,
Is there a way to change the default installation path in cpack?
This is for NSIS installer on Windows. I tried changing
CPACK_PACKAGE_INSTALL_DIRECTORY but
no matter what I set it to, Program Files always gets added. Anyway
to get around it?
We use CPack to package
I've got a static library that contains generated code, today this is
done in a make file so I can check the dependencies before the PERL
script is called again during the build process. I'm adding a
CustomBuildCommand to the project, so the dependecies are properly
checked in my vcproj files.
Brad King wrote:
This was fixed months ago in the CVS version of CMake. I've updated the
bug report to link to information on the fix.
Thanks Brad! Sorry for the duplicate bug report. :)
--
Philip Lowman
Simulation Development Engineer, Modeling and Simulation Technology
General Dynamics
Could somebody modify FindZLIB.cmake to search
/Program Files/zlib directory for zlib include and lib directories?
This is the default location that CPack generated NSIS installer uses.
FIND_PATH(ZLIB_INCLUDE_DIR zlib.h
/usr/local/include
/usr/include
/Program
On 2007-10-01 08:54-0700 Alan W. Irwin wrote:
On 2007-10-01 11:30+0200 Maik Beckmann wrote:
I opened a bug-report as a repository for patches and a place for
discussions
on this issue:
http://www.cmake.org/Bug/view.php?id=5809
please join to...
... contribute patches,
... test the
Hi,
Apparently it's is the way the library is built, in my case, it should
be build with the -c option, but I don't know how to specify that in the
cmakefile.txt, could someone help me out,
Thanks
Marie
___
CMake mailing list
CMake@cmake.org
On 2007-10-01 14:15-0700 Neal Meyer wrote:
I've got a static library that contains generated code, today this is
done in a make file so I can check the dependencies before the PERL
script is called again during the build process. I'm adding a
CustomBuildCommand to the project, so the
13 matches
Mail list logo
