Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] Re: cdt-dev Digest, Vol 22, Issue 6

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.
 
 
Date: Mon, 04 Dec 2006 12:54:03 +0000
From: Derek Morris <dmsubs@xxxxxxxxxxxxx>
Subject: Re: [cdt-dev] Adding a new tool to MBS
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Message-ID: <45741A6B.2080600@xxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Further to this, I found the 'secondaryOutputs' attribute of a toolchain, which
looks like what I want.

Unfortunately, I can't get it to work for me.

Looking at the generated makefile, it adds a secondary_outputs target which
references a (generated) buildVariable. Unfortunately the buildVariable is never
assigned, so it doesn't build my secondaryOutput.

I tried using the EXECUTABLES variable but that cause it to build something
called USER_OBJS instead of my target name...

TIA,
--
Derek

Back to the top