Alan W. Irwin wrote:
The GNU make documentation states the following:
Since it knows that phony targets do not name actual files that
could be remade from other files, make skips the implicit rule search
for phony targets This is why declaring a
target phony is good for [make] pe
Hi,
Does cmake have support for embedding version numbers in libraries and
executables? Specifically:
* generate a string with the library / executable name, containing the
version
* allow nightly builds to add build number
* add checksum (sha1) to uniquely identify a the library / executable
The GNU make documentation states the following:
Since it knows that phony targets do not name actual files that
could be remade from other files, make skips the implicit rule search
for phony targets This is why declaring a
target phony is good for [make] performance
Also,
Bill Hoffman wrote:
Matthew Woehlke wrote:
Tavitayya Varanasi wrote:
SUN is planing to port cmake on Indiana ( a version of open
solaris ).
There is porting to be done? Hmm... I successfully built and tested
cmake 2.4.8 on Solaris 10/x86... I admit I haven't actually *used*
that build,
Matthew Woehlke wrote:
Tavitayya Varanasi wrote:
SUN is planing to port cmake on Indiana ( a version of open
solaris ).
There is porting to be done? Hmm... I successfully built and tested
cmake 2.4.8 on Solaris 10/x86... I admit I haven't actually *used* that
build, though I have used 2.
Tavitayya Varanasi wrote:
SUN is planing to port cmake on Indiana ( a version of open solaris
).
There is porting to be done? Hmm... I successfully built and tested
cmake 2.4.8 on Solaris 10/x86... I admit I haven't actually *used* that
build, though I have used 2.4.6 on a different Sun b
Hello Martin,
You are missing a ( after the ADD_CUSTOM_COMMAND.
Andy
On Mon, Mar 17, 2008 at 2:18 PM, Martin Fischer <[EMAIL PROTECTED]> wrote:
> Hi Andy,
>
> it seems I don't understand the direction you are pointing me to. I
> used add_custom_command in some occasions. So now I tried:
>
>
Hi Andy,
it seems I don't understand the direction you are pointing me to. I
used add_custom_command in some occasions. So now I tried:
FOREACH( FILE ${SOURCEFILES})
ADD_CUSTOM_COMMAND ${FILE}.out
COMMAND ${tool_EXE} ${CMAKE_CURRENT_SOURCE_DIR}/${FILE}.in
${CMAKE_CURREN
On Monday 17 March 2008, Egon Kocjan wrote:
> On Mon, 2008-03-17 at 02:21 +0100, Pau Garcia i Quiles wrote:
> > Quoting Egon Kocjan <[EMAIL PROTECTED]>:
> > > Are/will-be there per target commands for adding include directories
> > > and preproc. defines?
> >
> > SET_DIRECTORY_PROPERTIES
> > SET_SO
On Mon, 2008-03-17 at 02:21 +0100, Pau Garcia i Quiles wrote:
> Quoting Egon Kocjan <[EMAIL PROTECTED]>:
>
> > Are/will-be there per target commands for adding include directories and
> > preproc. defines?
>
> SET_DIRECTORY_PROPERTIES
> SET_SOURCE_FILES_PROPERTIES
> SET_TARGET_PROPERTIES
>
> You
10 matches
Mail list logo