Am Friday 19 September 2008 22:57:03 schrieb E. Wing:
> Interesting. I was expecting the PATH_SUFFIXES to work on Windows. I
> thought I had tested this general technique, though maybe not with the
> Freetype module and maybe not 2.6.0. I think this may be a CMake bug,
> but I'm not an authority on
Darren Weber wrote:
[]
Gnu libtool has a mechanism to deal with this situation (creating temporary
wrapper scripts for each executable), but if cmake has one, I haven't found
it.
I have a testing build that seems to create paths within the build
tree that are specific to the build, but once t
On Fri, Sep 19, 2008 at 9:15 PM, Tanguy Krotoff <[EMAIL PROTECTED]> wrote:
> Hi everybody
>
> I would like to change the directory layout generated by CPack given
> the generator used.
> In a way, I would like a more fine-grained control about what CPack
> generates and after reading the different
Interesting. I was expecting the PATH_SUFFIXES to work on Windows. I
thought I had tested this general technique, though maybe not with the
Freetype module and maybe not 2.6.0. I think this may be a CMake bug,
but I'm not an authority on the matter.
You might want to try a more generalized example
On Fri, Sep 19, 2008 at 12:30 PM, Darren Weber
<[EMAIL PROTECTED]> wrote:
> On Thu, Sep 18, 2008 at 11:35 PM, Martin Costabel <[EMAIL PROTECTED]> wrote:
>> Darren Weber wrote:
>>>
>>> I'm exploring how to build and install VTK-5-2-0 on OSX. I'm trying
>>> to use shared libraries, but the default s
On 2008-09-19 10:27-0500 kent williams wrote:
Never mind, I found it in the 'FILE' command...
Also, "cmake -E" has the make_directory subcommand. You can use that
both at cmake time and also at build time (as part of a custom command).
Alan
__
Alan W. Irwin
Astronom
Hi,
I have created a module for Google's protocol buffers. It works for me, but
will of course need adjustments for various non-unix platforms.
And testing :)
--
kind regards, Esben
# Try to find protocol buffers (protobuf)
#
# Use as FIND_PACKAGE(ProtocolBuffers)
#
# PROTOBUF_FOUND - system
On Thu, Sep 18, 2008 at 11:35 PM, Martin Costabel <[EMAIL PROTECTED]> wrote:
> Darren Weber wrote:
>>
>> I'm exploring how to build and install VTK-5-2-0 on OSX. I'm trying
>> to use shared libraries, but the default settings do not put full
>> paths in the .dylib file links for the libvtk* librar
Eric Noulard wrote:
2008/9/19 Christopher Harvey <[EMAIL PROTECTED]>:
Sorry about the long subject,
My question is about the way cmake defines dynamic link library search paths
for release builds of executables. I've got an executable, written in C++
that depends on a shared library within t
2008/9/19 Christopher Harvey <[EMAIL PROTECTED]>:
> Sorry about the long subject,
>
> My question is about the way cmake defines dynamic link library search paths
> for release builds of executables. I've got an executable, written in C++
> that depends on a shared library within the same project.
I really need to take a break.
INCLUDE (BundleUtilties)
NOT
INCLUDE (BundleUtilities.cmake)
Doh...
On Sep 19, 2008, at 1:42 PM, Mike Jackson wrote:
I am getting the following error when I am running the latest CMake
CVS:
include could not find load file:
BundleUtilities.cmake
I get
I am getting the following error when I am running the latest CMake CVS:
include could not find load file:
BundleUtilities.cmake
I get the same error with any file I try that is located in the
Modules directory. Was something changed in CMake-CVS over the last
day or so that would cau
Hi everybody
I would like to change the directory layout generated by CPack given
the generator used.
In a way, I would like a more fine-grained control about what CPack
generates and after reading the different docs I don't know if it is
possible.
I have a pretty complex multiplatform program wi
Sorry about the long subject,
My question is about the way cmake defines dynamic link library search
paths for release builds of executables. I've got an executable, written
in C++ that depends on a shared library within the same project. When I
run ldd on that executable I get this output
ld
Never mind, I found it in the 'FILE' command...
On Fri, Sep 19, 2008 at 10:26 AM, kent williams
<[EMAIL PROTECTED]> wrote:
> I am CMake-izing a non-CMake project -- or rather we have CMake-ized
> it, and are doing some clean up.
>
> We have a testing shell script that I'm converting to CTest tests
I am CMake-izing a non-CMake project -- or rather we have CMake-ized
it, and are doing some clean up.
We have a testing shell script that I'm converting to CTest tests.
The first thing it does is create a directory where it drops all the
testing output.
I'd like to do the same thing -- create a d
FILE(WRITE "${CMAKE_CURRENT_BINARY_DIR}/test_case_filesystem.tmp" "foo")
IF(FILE EXITS "${CMAKE_CURRENT_BINARY_DIR}/test_case_filesystem.TMP")
...
ENDIF()
You should also check if the file already exists.
But, be careful. On Mac for example HFS is case independent, but NFS or
other FS may not
Hi there,
I would like to write in a portable way the following cmake script:
FILE(GLOB myvar
"${fullpath}"/*.DCM
"${fullpath}"/*.dcm
)
How do I check that the target system is case sensitive or not ?
Thanks,
--
Mathieu
___
CMake mailing lis
2008/9/19 Esben Mose Hansen <[EMAIL PROTECTED]>:
> On Friday 12 September 2008 14:08:01 Esben Mose Hansen wrote:
>> Hi,
>>
>> I was unable to find a cmake module for google's protocol buffers, so I
>> wrote my own. Is there some sort of repository for these things? The module
>> probably does not h
On Tuesday 16 September 2008 21:48:16 ZNV wrote:
> > That is what dependency tracking is for. And that should be handled
> > automatically by the add_custom_target.
>
> My experience contradicts your statement.
Yeah, my bad. add_custom_command adds dependencies, not add_custom_target. In
fact, t
2008/9/19 Olaf Peter <[EMAIL PROTECTED]>:
> Hi,
>
> for a generated version header I need to convert a given hex to an integer.
> I've wrote:
>
> set(RELEASE_LEVEL_ALPHA 0xA)# For internal use
> set(RELEASE_LEVEL_BETA 0xB)# For internal use
> set(RELEASE_LEVEL_GAMMA 0xC)# For release c
On Fri, 19 Sep 2008, Boudewijn Rempt wrote:
> Hi,
>
> We're having a little problem when trying to compile a Qt-based library
> (libiris)
> using nmake. We're using cmake 2.6 and automoc, but running nmake results in:
>
> C:\WORK\HyvesDesktop\trunk\build>nmake
>
> Microsoft (R) Program Mainten
Hi,
I've now walked through the source, and it seems that using the -C
option with ctest does not do anything (useful). I've tried it with the
CDashTest project available from here
http://www.cdash.org/download/CDashTest.zip
For example, if I try to issue any test call from the command line
Hi,
for a generated version header I need to convert a given hex to an
integer. I've wrote:
set(RELEASE_LEVEL_ALPHA 0xA)# For internal use
set(RELEASE_LEVEL_BETA 0xB)# For internal use
set(RELEASE_LEVEL_GAMMA 0xC)# For release candidates
set(RELEASE_LEVEL_FINAL 0xF)# For final
Andreas,
well, considering the first issue I usually hoped that this might be
solved by Visual Studio somehow automatically by some internal magic.
After a cleanup of the WinCE.cmake and WinCE-cl.cmake a.s.o. these files
should mainly contain settings which are universal to all SDKs (I wonder
Hi,
I am still wondering how this all fits together.
The patch you are working on, will generate a visual studio file that
contains build rules for all installed SDKs.
But when generating for nmake we will have a cross compile
configuration for a single SDK. How can we ensure
that both things work
Hi,
We're having a little problem when trying to compile a Qt-based library
(libiris)
using nmake. We're using cmake 2.6 and automoc, but running nmake results in:
C:\WORK\HyvesDesktop\trunk\build>nmake
Microsoft (R) Program Maintenance Utility Version 9.00.30729.01
Copyright (C) Microsoft Corp
27 matches
Mail list logo
