On Sat, Nov 6, 2010 at 2:30 AM, Michael Hertling wrote:
> If you want to ensure that an output-producing custom command without
> dependencies runs each time its output - present or not - is referred
> to you might use a second, say, dummy output which never exists, e.g.:
>
> ADD_CUSTOM_COMMAND(
>
On Fri, Nov 5, 2010 at 1:04 PM, Alan W. Irwin wrote:
> I agree the above idea should work, but dropping add_custom_command
> completely and moving the COMMAND to add_custom_target instead (and
> dropping all file DEPENDS for the custom target) is even a simpler way
> to insure COMMAND gets execute
On Thu, Nov 4, 2010 at 9:23 PM, SK wrote:
> On Thu, Nov 4, 2010 at 6:09 PM, Alan W. Irwin
> wrote:
>> then the custom make command
>> should always be run (since it has no DEPENDS option),
>
> Alan, you are absolutely right!!
No, sorry. Only if the add_custom_command
On Thu, Nov 4, 2010 at 6:09 PM, Alan W. Irwin wrote:
> then the custom make command
> should always be run (since it has no DEPENDS option),
Alan, you are absolutely right!! I missed this since the external
makefile I need actually does have a dependency to create the makefile
itself. So, the c
On Thu, Nov 4, 2010 at 5:41 PM, mina adel wrote:
> Thank you for your help.
>
> I used ADD_Custom_Command() to run the makefiles of 3rd-partylibraries.
>
> My problem is how to combine these generated (static) libraries into one
> static library using cmake to be used later in my project?
>
> The
On Tue, Nov 2, 2010 at 12:28 PM, SK wrote:
>
> ADD_CUSTOM_TARGET( OUTPUT foo1 foo2
> COMMAND "make foos"
> [DEPENDS [ALL]] )
>
I filed a feature request for better external makefile support by way
of output from add_custom_target()
http://cmake.
On Thu, Nov 4, 2010 at 4:29 PM, SK wrote:
> On Sat, Oct 30, 2010 at 8:31 AM, Alan W. Irwin
> wrote:
>> On 2010-10-29 20:50-0700 mina adel wrote:
>>
>>>
>>> Hi All
>>>
>>> I have an open source code that I use in my project. This open source
On Sat, Oct 30, 2010 at 8:31 AM, Alan W. Irwin
wrote:
> On 2010-10-29 20:50-0700 mina adel wrote:
>
>>
>> Hi All
>>
>> I have an open source code that I use in my project. This open source code
>> already has Makefile coded for it.
>>
>> I want to use cmake so that before it compile my project it
On Mon, Nov 1, 2010 at 11:25 PM, Rolf Eike Beer wrote:
> Am Monday 01 November 2010 schrieb SK:
>> I know add_custom_target does not produce output as far as CMake is
>> concerned. My situation is as follows:
>>
>> A traditional make process that I cannot modify prod
I know add_custom_target does not produce output as far as CMake is
concerned. My situation is as follows:
A traditional make process that I cannot modify produces a target on
which I must do some post-processing.
I use add_custom_target to force the makefile to always run. I use
add_custom_comm
)
Seems cumbersome to me, particularly since I need to intercept the
application build at ADD_EXECUTABLE time. I would have been much
happier to find:
ADD_LINK_ONLY_DEPENDENCY()
Maybe this is a reasonable feature request?
Cheers,
-steve
On Tue, Sep 7, 2010 at 12:04 PM, SK wrote:
> Hello,
Hello,
I have an external build process that produces a linker script that I
must use in my CMake project. I must leave the external build as-is.
I'm using gcc in Linux.
I must relink my application built with CMake if the linker script
changes. I'm trying to do this in a simple macro and it's
Hello,
With excellent help from Jens Mueller and Dean Calver, CMake for D2
now passes our small suite of unit tests on both Windows and Linux.
Our tests include mixed C-D applications and libraries. We tested
with CMake 2.8.2 and DMD 2.048. We'd appreciate if a few hardy souls
were willing to ta
Hello, In many cmake modules, I see <> used around names, as in:
SET(CMAKE_C_COMPILE_OBJECT " -o
-c ")
What does this notation mean? I looked around but missed
this in the documentation.
Thanks,
-steve
___
Powered by www.kitware.com
Visit ot
CMakeCInformation.cmake tests the value of _INCLUDED_FILE under the
incorrect assumption that CMAKE_COMPILER_ID is true.
For example, line 46 and line 57 from a very recent version in the git
repo. If CMAKE_COMPILER_ID is not true, then the value of
_INCLUDED_FILE is a left-over from earlier unrel
On Sun, Aug 15, 2010 at 2:19 PM, Magnus Therning wrote:
> On 15/08/10 22:11, SK wrote:
>> When using the D language compiler 'dmd' on windows, I'm stuck with a
>> linker that gets confused with object file names like foo.c.obj. The
>> linker can only handle
When using the D language compiler 'dmd' on windows, I'm stuck with a
linker that gets confused with object file names like foo.c.obj. The
linker can only handle a single dot in the object file name, as in
foo.o
How can I set target names to just be the base name without the source
extension? I
Hello List,
I've taken an interested in D lately and in order to play around
there, of course I want CMake. There was an effort in 2007 to support
D, since abandoned, but I'm trying to take up the cause.
The project is just getting off the ground here:
http://code.google.com/p/cmaked2/source/chec
18 matches
Mail list logo
