I assume that it does do these aliases, because the source compiles, but
later causes a LINK Error.
Well now that I know it is not too much of a problem as least I know what it
is and how to fix it.
The Compiler is probally generating code to say that this function is in the
WINPROCS unit because I have specifically specified it as such.
WinProcs.SetTextAlign(Canvas.Handle, TA_TOP);
If I do not have the ALIAS prefixed to a function it works fine, so it must
be just that. I only do that on a couple of files, so it is pretty easy to
fix.
Now the major problem.
Any control from Delphi does not get installed onto the component paleete in
C++ Builder 3. If I use a new package, it just says that the package was
correctly installed, but I have NO components, C++ 1 & 4 have no problems.
Chris
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Carl Reynolds
Sent: Wednesday, 22 September 1999 08:57
To: Multiple recipients of list Delphi
Subject: RE: [DUG]: [LinkerFatal Error] Fatal: Illegal EXTDEF fixup
index in module 'C:\ADROCK\C1\adcolob.pas'
In Delphi, when one unit is replaced by another you can set up a project
alias to cater for this. Later versions of Delphi have the (default)
aliases
"WinTypes=Windows;WinProcs=Windows;DbiTypes=BDE;DbiProcs=BDE;DbiErrs=BDE
;". Can you not do the same in C++ Builder?
Setting up these aliases would mean that you wouldn't need to change the
source of every pascal unit you wanted to use.
Cheers,
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
