On Wed, Dec 1, 2010 at 10:59 AM, Kevyn-Alexandre Paré
kap...@rogue-research.com wrote:
Philip,
Thx for the reply. Neither of these solutions change a thing.
I try to play with ADD_CUSTOM_TARGET but same error...
ADD_CUSTOM_TARGET(RRThread.o ALL COMMAND ${CMAKE_C_COMPILER} -I
Hello
I know that the usage of relatives path out of the sources seems to be not an
easy one.
But maybe you can give me a workaround.
We use following directory structure
- dev
|--project1: CMakeLists.txt
|main.cpp
|stdafx.h
|project1.vcproj
|
On Tue, Nov 30, 2010 at 5:37 PM, Hicham Mouline hic...@mouline.org wrote:
As boost libraries naming convention doesn't include in the lib names
whether they are built by msvc9 win32 or x64, I am forced on a winxp 64 box
where I hold both versions to have a different lib directory under
Hi,
I have debugged a little why CMake always performs a full link instead
of an incremental one.
The problem is that after the linking, mt.exe comes and embeds the
manifest into the dll:
MT:
C:/Program Files/Microsoft SDKs/Windows/v7.0A/bin/mt.exe /nologo
/manifest
I was wrong. Dmytro pointed out that bjam allows building boost libraries
with the compiler and bitness in the boost library name --layout=versioned.
Therefore, I could have both 32 and 64bit versions in the same directory.
I wonder then if FindBoost is able to detect automatically the right
on win64 boxes, typically, 32bit binaries are under \Program Files (x86)
and
64bit are under \Program Files
It would be good if CMAKE_SYSTEM_PREFIX_PATH for e.g., and other similar
paths, were set to the appropriate
On win32 boxes:
. If msvc = \program files
. If msvc win64
Hello,
The compatibility matrix for different versions of cmake is now complete and
awaits review: http://www.cmake.org/Wiki/CMake_Version_Compatibility_Matrix
Apart from factual errors and things I might have missed, I am also interested
if someone has a better idea for embedding the
Am Samstag, 4. Dezember 2010 schrieb Philip Lowman:
On Tue, Nov 30, 2010 at 5:37 PM, Hicham Mouline hic...@mouline.org wrote:
As boost libraries naming convention doesn't include in the lib names
whether they are built by msvc9 win32 or x64, I am forced on a winxp 64
box where I hold
Am Samstag, 4. Dezember 2010 schrieb Soeren Freudiger:
Hello
I know that the usage of relatives path out of the sources seems to be not
an easy one. But maybe you can give me a workaround.
We use following directory structure
- dev
|--project1: CMakeLists.txt
|
|
the nightly build runs fine. but without checked in project files you cannot
ensure easily if it's the same as on your local machine.
nevertheless you still have the problem at renaming or moving the root
directory!!!
Am 04.12.2010 um 17:33 schrieb Rolf Eike Beer:
Am Samstag, 4. Dezember
You can configure this for your project:
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:STATIC_LIBRARY_FLAGS
Ryan
On Fri, Dec 3, 2010 at 7:07 PM, Belcourt, K. Noel kbe...@sandia.gov wrote:
Hi,
I'm on Mac OSX 10.5.8 with Intel 12.x compilers and CMake version 2.8.3.
CMake
On Dec 4, 2010, at 10:08 AM, Ryan Pavlik wrote:
You can configure this for your project:
http://www.cmake.org/cmake/help/cmake-2-8-
docs.html#prop_tgt:STATIC_LIBRARY_FLAGS
Thanks Ryan, I'll try it out.
-- Noel
___
Powered by www.kitware.com
On 2010-12-04 16:58+0100 Johannes Zarl wrote:
Hello,
The compatibility matrix for different versions of cmake is now complete and
awaits review: http://www.cmake.org/Wiki/CMake_Version_Compatibility_Matrix
Apart from factual errors and things I might have missed, I am also interested
if
Hi Ryan,
On Dec 4, 2010, at 10:08 AM, Ryan Pavlik wrote:
You can configure this for your project:
http://www.cmake.org/cmake/help/cmake-2-8-
docs.html#prop_tgt:STATIC_LIBRARY_FLAGS
This doesn't seem to do what I want it to. In my CMakeLists.txt file
I have this code.
Wow that is impressive. Not only does it lay out the version
information well, it also represents a very nice overview of available
knobs to tweak - I've already spotted one or two I need to roll back
into my own CMake scripts, and I'm sure there are more.Thank you
for all the time and effort
The name of the target property likely has to be matching the original case
(all caps)
Ryan
On Sat, Dec 4, 2010 at 1:10 PM, Belcourt, K. Noel kbe...@sandia.gov wrote:
Hi Ryan,
On Dec 4, 2010, at 10:08 AM, Ryan Pavlik wrote:
You can configure this for your project:
On Thursday 02 December 2010 07:48:55 Michael Wild wrote:
Use ADD_CUSTOM_COMMAND.
@Michael: that advice is not correct. add_custom_command sets up a
command to be run at make time. Instead, the execute_process command
should be used to run a command at CMake time which is what the
On Saturday, December 4, 2010, Hicham Mouline hic...@mouline.org wrote:
I was wrong. Dmytro pointed out that bjam allows building boost
libraries with the compiler and bitness in the boost library name
--layout=versioned.
Therefore, I could have both 32 and 64bit versions in the same
18 matches
Mail list logo
