Benjamin Roy wrote:
And i try to avoid the step 3 and 4 in order to generate a make that
build directly the executable after build static lib without re-run
Cmake.
I try few solution based on test with IF or
SET_SOURCE_FILES_PROPERTIES(... GENERATED ) or try to use dependencies
and ADD_CU
At 07:19 PM 10/11/2006, Axel Roebel wrote:
>This is exactly what I do currently.
>I thought there would may be exist an easier way.
>I now see that my main problem is how I replace the compiler:
>
>I patch CMakeFiles/CMakeCCompiler.cmake
>from within CMakeLists.txt,
>while I probably should simply
On Wednesday 11 October 2006 15:28, you wrote:
> Axel Roebel wrote:
> > The problem is that to my knowledge the only way to communicate the
> > deployment target to gcc is via environment variables. I admit this is a
> > really strange way (probably its save to say silly) to select compiler
> > opt
On Wednesday 11 October 2006 15:24, you wrote:
> Axel Roebel wrote:
> > I frequently struggle with the problem to set
> > global linker flags. Global here means these flags should be used
> > whenever the linker is used. The main example where I need that
> > is the -mno-cygwin flag of the cygwin c
William A. Hoffman wrote:
At 05:11 PM 10/11/2006, Eran Guendelman wrote:
Hi, we are trying to track down why cmake 2.4 is crashing when generating the
VisualStudio 7 build files whereas cmake 2.2 worked fine. I built a debug
version of cmake and narrowed it down to the following issue:
In cm
At 05:11 PM 10/11/2006, Eran Guendelman wrote:
>Hi, we are trying to track down why cmake 2.4 is crashing when generating the
>VisualStudio 7 build files whereas cmake 2.2 worked fine. I built a debug
>version of cmake and narrowed it down to the following issue:
>
>In cmLocalGenerator::ComputeL
Hi, we are trying to track down why cmake 2.4 is crashing when
generating the VisualStudio 7 build files whereas cmake 2.2 worked fine.
I built a debug version of cmake and narrowed it down to the following
issue:
In cmLocalGenerator::ComputeLinkInformation it goes through the
libraries and
At 05:10 PM 10/11/2006, Warren Turkal wrote:
>On Wednesday 11 October 2006 12:52, Brad King wrote:
>> Mike Jackson wrote:
>> > BTW, when is the next release?
>>
>> When it's ready.
>
>Typical open source answer:-)
Unlike commercial software which always releases on fixed
and reliable schedule
On Wednesday 11 October 2006 12:52, Brad King wrote:
> Mike Jackson wrote:
> > BTW, when is the next release?
>
> When it's ready.
Typical open source answer:-)
wt
--
Warren Turkal, Research Associate III/Systems Administrator
Colorado State University, Dept. of Atmospheric Science
_
Mike Jackson wrote:
> Thanks for the fix. I look forward to the next release of Cmake. BTW, when
> is the next release?
When it's ready.
-Brad
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Thanks for the fix. I look forward to the next release of Cmake. BTW, when
is the next release?
On 10/11/06 12:59 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
> Mike Jackson wrote:
>> On 10/10/06 4:56 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
>>> SET_TARGET_PROPERTIES (DislocationIO
>>> PROPERT
At 12:29 PM 10/11/2006, Sean McBride wrote:
>
>Any ideas?
It is a bug in the Xcode generator happens with any version of Xcode.
I am working on a fix.
-Bill
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Pablo Odorico wrote:
> Some questions now:
> - Can't QUIET be used with components?
The entire find is either quiet or not.
> - _all_ components have to be REQUIRED?
The component syntax is just a list of components that are requested.
You can interpret it however you wish in the Find module
On 2006-10-10 17:08, William A. Hoffman said:
>There is a dashbaord, and it seems to be working.
>eno Darwin-XCode24-dbg
>So, I think it should work. The output you have is not very helpful.
>You may want to try a cmake --debug-trycompile, then look at
>the CMakeFiles/CMakeTmp directory and
Mike Jackson wrote:
> On 10/10/06 4:56 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
>> SET_TARGET_PROPERTIES (DislocationIO
>> PROPERTIES BUILD_WITH_INSTALL_RPATH 1
>> INSTALL_NAME_DIR "@executable_path/../PlugIns"
>> )
Okay, there was a bug in the code that computes the final value
Mike Jackson wrote:
>
>
> On 10/10/06 4:56 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
>
>> Mike Jackson wrote:
>>> On 10/10/06 4:08 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
cmake --help-command SET_TARGET_PROPERTIES
>>> OK.. Reading all the output from that command there seems to be some
On 2006-10-11 02:20, Axel Roebel said:
>The problem is that to my knowledge the only way to communicate the
>deployment target to gcc is via environment variables. I admit this is a
>really strange way (probably its save to say silly) to select compiler
>options, but as far as I know, this is the
Original-Nachricht
Datum: Wed, 11 Oct 2006 16:29:11 +0200
Von: Benjamin Roy <[EMAIL PROTECTED]>
An: cmake@cmake.org
Betreff: [CMake] building executable from static libs
> Hi,
>
> My question should sound like a dummy one, but can't find the answer by
> myself, maybe I have no
Cmake 2.4.3
Unix Make files
On 10/11/06 9:38 AM, "David Cole" <[EMAIL PROTECTED]> wrote:
> Are you using CMake 2.4.3?
> Xcode or Unix Makefiles generator?
>
> Mike Jackson wrote:
>
>>
>> On 10/10/06 4:56 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>>> Mike Jackson wrote:
>>>
>
Hi,
My question should sound like a dummy one, but can't find the answer by
myself, maybe I have not understand clearly the spirit of Cmake...
I try to change a build system from automake/autoconf under Cmake on
linux, due to some portability issues...
So I need to build some executable fro
Axel Roebel wrote:
> The problem is that to my knowledge the only way to communicate the
> deployment target to gcc is via environment variables. I admit this is a
> really strange way (probably its save to say silly) to select compiler
> options, but as far as I know, this is the way it is done
Pecevski Dejan wrote:
> Hi,
>
> As part of our build process which uses cmake, we want to generate
> wrapper c++ files from existing sources, for python interfacing (using
> Py++ and boost.python).
> The dependency we want to achieve is :
>A1.cpp A2.cpp A3.cpp A1.h A2.h A3.h ... <- Ab
Are you using CMake 2.4.3?
Xcode or Unix Makefiles generator?
Mike Jackson wrote:
On 10/10/06 4:56 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
Mike Jackson wrote:
On 10/10/06 4:08 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
cmake --help-command SET_TARGET_PROPERTIES
Axel Roebel wrote:
> I frequently struggle with the problem to set
> global linker flags. Global here means these flags should be used
> whenever the linker is used. The main example where I need that
> is the -mno-cygwin flag of the cygwin compiler.
> This flag creates objects that will not make
Hi again,
Filipe Sousa wrote:
ADD_CUSTOM_COMMAND(
OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/copy.h
COMMAND cp ${CMAKE_CURRENT_SOURCE_DIR}/a.h
${CMAKE_CURRENT_BINARY_DIR}/copy.h
DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/a.h
)
INCLUDE_DIRECTORIES(
${CMAKE_CURRENT_BINARY_DIR} # for copy.h
${CMAKE_CURRENT
Hello,
I frequently struggle with the problem to set
global linker flags. Global here means these flags should be used
whenever the linker is used. The main example where I need that
is the -mno-cygwin flag of the cygwin compiler.
This flag creates objects that will not make use of the cygwin dl
Pecevski Dejan wrote:
> Filipe Sousa wrote:
>
> Hi Filipe,
> Thanks for the reply.
> I have setup a simple example based on your solution, but it doesn't
> seem to work. Files of the example are attached to the e-mail.
> Basically in the example I am building a library libtest from these files:
>
Filipe Sousa wrote:
ADD_CUSTOM_COMMAND(
OUTPOUT ${CMAKE_CURRENT_BINARY_DIR}/A1.cpp
${CMAKE_CURRENT_BINARY_DIR}/A1.h .. A2.cpp ...
COMMAND generate.py ${CMAKE_CURRENT_BINARY_DIR}/Abase.h
DEPENDS genereate.py ${CMAKE_CURRENT_BINARY_DIR}/Abase.h
)
You have to add the genareated file to ADD_LIBRA
28 matches
Mail list logo
