Brad King wrote:
> Alexander Neundorf wrote:
>> Von: Brad King <[EMAIL PROTECTED]>
>>
>>> Alexander Neundorf wrote:
Attached is a first try of a patch against 2.4 branch.
It introduces two new variables CMAKE_CREATE_PREPROCESS_RULES and
>>> CMAKE_CREATE_ASSEMBLE_RULES. I think especially
Alexander Neundorf wrote:
> Von: Brad King <[EMAIL PROTECTED]>
>
>> Alexander Neundorf wrote:
>>> Attached is a first try of a patch against 2.4 branch.
>>> It introduces two new variables CMAKE_CREATE_PREPROCESS_RULES and
>> CMAKE_CREATE_ASSEMBLE_RULES. I think especially the name
>> CMAKE_CREATE
Von: Brad King <[EMAIL PROTECTED]>
> Alexander Neundorf wrote:
> > Attached is a first try of a patch against 2.4 branch.
> > It introduces two new variables CMAKE_CREATE_PREPROCESS_RULES and
> CMAKE_CREATE_ASSEMBLE_RULES. I think especially the name
> CMAKE_CREATE_ASSEMBLE_RULES is not good (sin
Alexander Neundorf wrote:
> Attached is a first try of a patch against 2.4 branch.
> It introduces two new variables CMAKE_CREATE_PREPROCESS_RULES and
> CMAKE_CREATE_ASSEMBLE_RULES. I think especially the name
> CMAKE_CREATE_ASSEMBLE_RULES is not good (since actually everything except
> assembli
Hi,
Von: Brad King <[EMAIL PROTECTED]>
> Alexander Neundorf wrote:
> > Original-Nachricht
> > Von: Brad King <[EMAIL PROTECTED]>
> >
> >> Alexander Neundorf wrote:
> >>> Hi,
> >>>
> >>> it would be nice if it would be possible to have for each object file
> >> also a target whi
Alexander Neundorf wrote:
> Original-Nachricht
> Von: Brad King <[EMAIL PROTECTED]>
>
>> Alexander Neundorf wrote:
>>> Hi,
>>>
>>> it would be nice if it would be possible to have for each object file
>> also a target which only preprocesses the file and one which
>> preprocesses
Original-Nachricht
Von: Brad King <[EMAIL PROTECTED]>
> Alexander Neundorf wrote:
> > Hi,
> >
> > it would be nice if it would be possible to have for each object file
> also a target which only preprocesses the file and one which
> preprocesses and compiles, but not assembles
Alexander Neundorf wrote:
Hi,
Von: Brad King <[EMAIL PROTECTED]>
John Ellson wrote:
Brad King wrote:
John Ellson wrote:
Not sure that I'm following the converstation properly here, but
can any of this be used to provide access to a set of .o for use as a
"convenience library" ?
No, these v
Hi,
Von: Brad King <[EMAIL PROTECTED]>
> John Ellson wrote:
> > Brad King wrote:
> >> John Ellson wrote:
> >>>
> >>> Not sure that I'm following the converstation properly here, but
> >>> can any of this be used to provide access to a set of .o for use as a
> >>> "convenience library" ?
> >>
> >
John Ellson wrote:
Brad King wrote:
John Ellson wrote:
Not sure that I'm following the converstation properly here, but
can any of this be used to provide access to a set of .o for use as a
"convenience library" ?
No, these variables are used to specify rules for the generators to
put in t
Brad King wrote:
John Ellson wrote:
Not sure that I'm following the converstation properly here, but
can any of this be used to provide access to a set of .o for use as a
"convenience library" ?
No, these variables are used to specify rules for the generators to
put in the build files.
Th
John Ellson wrote:
Brad King wrote:
Alexander Neundorf wrote:
Hi,
it would be nice if it would be possible to have for each object file
also a target which only preprocesses the file and one which
preprocesses and compiles, but not assembles the file (so that you
get the assembler code).
Brad King wrote:
Alexander Neundorf wrote:
Hi,
it would be nice if it would be possible to have for each object file
also a target which only preprocesses the file and one which
preprocesses and compiles, but not assembles the file (so that you
get the assembler code).
Is there a way to do
Alexander Neundorf wrote:
Hi,
it would be nice if it would be possible to have for each object file also a
target which only preprocesses the file and one which preprocesses and
compiles, but not assembles the file (so that you get the assembler code).
Is there a way to do this with macros ?
Hi,
it would be nice if it would be possible to have for each object file also a
target which only preprocesses the file and one which preprocesses and
compiles, but not assembles the file (so that you get the assembler code).
Is there a way to do this with macros ?
I almost think this would h
15 matches
Mail list logo