|
Okay. Thanks anyway.
Delicia.
----- Original Message ----- Date: Fri, 08
Dec 2006 08:01:45 +0000
From: Derek Morris <dmsubs@xxxxxxxxxxxxx>
Subject:
Re: [cdt-dev] Re: cdt-dev Digest, Vol 22, Issue 6
To: "CDT General
developers list." <cdt-dev@xxxxxxxxxxx>
Message-ID:
<45791BE9.6050604@xxxxxxxxxxxxx>
Content-Type:
text/plain; charset=ISO-8859-1; format=flowed
Delicia,
I gave up
and used a custom build step. This satisfied my current
requirements.
Either there is something wrong with the secondaryOutputs
attribute or its usage
is so obscure as to be useless.
--
Derek
Delicia Pacheco wrote:
> Hi Derek,
>
> Did you find a solution to getting the
EXECUTABLES variable defined
> to something?
> I have a similar
situation.
> I need a variable (set to the generated executable - o/p
from
> linker/archiver) that I can use for a further execution
step.
> But the build variable used in the outputType (of the linker
tool)
> doesn't get set to anything.
>
> Please let
me know of any suggestions?
>
> Thanks!
>
Delicia.
|
