Re: Delphi language support in CMake build system

On 2008-10-21, Maarten Wiltink <maarten@xxxxxxxxxxxxxxxxxx> wrote:
"eric.lemings@xxxxxxxxx" <eric@xxxxxxxxxxx> wrote in message
news:aab9f68b-b2ba-47e8-8d27-8ac6de9647f7@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[...]
This example translates Delphi source directly into an executable.
Does anyone have an example of translating/compiling the source for a
simple Delphi program into an intermediate representation before
"linking" the executable?

Compiling individual units will generate .dcu files, which are object
files.

There is more in there than just the object code, I'd say at least
- the interface of the unit in some form,
- the base object code
- list of used units (maybe splitted into separate interface and implementation
lists), probably with data to check version integrity (simple CRC over
foreign unit interface or used functions, complicated: signatures of all
functions that are used, per unit with additional type info)
- (D2005 (2006?)+) inlined procedures in some tree form

Probably also
- list of defines on start compilation (IOW IDE+cmdline preprocessor state)
- List of imported object files ({$I xxx.obj}) At least it should be able to
do a timestamp check on it.

Maybe also: (I'm really guessing here)
- Data for other parts of the IDE (ITE, OI, Syntax highlighter. I'd put my
cards on the latter, since there is some speed requirement)
- Stuff related to ActiveX use.
.