[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Managing additional toolchain state
|
Treggiari, Leo wrote:
-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
Behalf Of Recoskie, Chris
Sent: Friday, January 21, 2005 6:34 AM
To: cdt-dev@xxxxxxxxxxx
Subject: RE: [cdt-dev] Managing additional toolchain state
I would suspect as well that you are going to have to create a new
makefile generator so that when you change this "module def file", the
build system detects the dependency and relinks the executable file.
[Leo] Good point!
Just for background's sake, I've been coding for a while. Since before
PDP-8s had bootstrap ROMS and you booted from paper tape to load the
magtape's OS (in high school.) Learned Unix from the System III man
pages. I'm not entirely clueless. I read code awfully well.
I have a makefile generator. It works.
I disclaim however that it's been a few months since I took a look at
the featureset of the work that Leo did in 2.1 so it might be that this
is already taken care of. I do recall that we had discussed having
"command formatters" that would allow you to specify printf-style how
you wanted the command for a particular tool to be generated, but I
don't recall if a) this included the ability to modify the dependency
portion of the makefile rule, and b) if this feature in general was
slated for 2.1 or beyond.
It's not a problem with a command formatter. What Leo's done is good
work and it works admirably. Apart from having to add the rest of the
various DMC compiler flags and switches, what I've got now will compile
Win32 CONSOLE subsystem or a DLL. It ain't that hard if you look at the
code.
You could add a dependency calculator to your linker tool. I haven't
tried this with the linker - hopefully it will work....
I'll look into it. But look at my penultimate reply: I'd just like to
save some extra data in .cdtbuild or .cdtproject, if that's at all possible.
