[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Linker must be the target Tool ?
|
When I was at TI, I got around this by just not using the libs type, but
making my libraries option a string list instead. This worked fine but I
had to make sure my library search path option appeared first in the option
list, otherwise it could never resolve the libraries. Dependencies on lib
files weren't being tracked then, but I was able to live with that at the
time.
===========================
Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt
"Treggiari, Leo"
<leo.treggiari@in
tel.com> To
Sent by: "CDT General developers list."
cdt-dev-bounces@e <cdt-dev@xxxxxxxxxxx>
clipse.org cc
Subject
13/06/2006 05:08 RE: [cdt-dev] Linker must be the
PM target Tool ?
Please respond to
"CDT General
developers list."
<cdt-dev@eclipse.
org>
Hi Enrico,
I was not aware of this problem - maybe Chris or Mikhail is. I suggest
that you add a bugzilla report. This is probably left over from a
couple of releases ago when a tool-chain had to end with the linker or
archiver.
Regards,
Leo
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Enrico Ehrich
Sent: Tuesday, June 13, 2006 4:51 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Linker must be the target Tool ?
Hi,
I see you are busy with the RC3 release but I have something to ask,
sorry ;)
Actually I'm creating a little managed builder plugin for an ARM gcc to
use for an embedded system (Nintendo DS).
I don't want spent allot time on this, because I do this in my spare
time and simply want use and share it.
So I though I can use the usual gnu MBS which is included in the CDT.
That was easier as I though so a made a
new plugin and inherited the buildDefinitions from
org.eclipse.cdt.managedbuilder.gnu.ui and added my special options etc..
The problem I had was, that I need some additional build steps by
default as the predefined: cpp,cc,as,ld
I need to convert the linked ELF file to an absolute code file and then
convert it to a special ROM file with header and so on.
Therefor I added 2 more tools with options, input/outputTypes and set
the "targetTool" to the last tool and the extension to
the final file extension (e.g. *.nds) in the toolChain.
So it worked well but one thing is not working as I guessed:
The static link libraries (-l) and additional object files does not
appear in the autogenerated objects.mk file.
I analysed it and found that the makefile generator class search for
this special "libs" and "userObj" valueTypes in the
"targetTool". But my targetTool is not the linker!!
I don't want write my own MBS thats too much work. Now I made the
workaround that the libs are added as usual stringList
to the command line. The same with the other objects but I have to take
care about the order.
But I think thats not the right way.
I simply wanted to ask if this problem is known ? Or I missed something
and it works using some other tricks ?
It would be nice if this scenario will be supported in future releases
of CDT.
ciao
Enrico
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier
anmelden: http://mail.yahoo.de
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
