Lost me there, trying to find that $EXTERNALSYM in the help file was a waste
of time, just more undocumented features.
Now here is some interesting facts:
I have made a test delphi control this is the code:
unit AdrockTestThisCPlusPlusPanel;
interface
uses
Windows, Messages, SysUtils, Classes, Graphics, Controls, Forms, Dialogs,
ExtCtrls;
type
TAdrockTestThisCPlusPlusPanel = class(TPanel)
end;
procedure Register;
implementation
procedure Register;
begin
RegisterComponents('Adrock', [TAdrockTestThisCPlusPlusPanel]);
end;
end.
1) If I use C++ 4 and install the .OBJ file into a new package and compile
the package the panel is installed and is useable.
2) If I use C++ 3 and install the .OBJ file into a new package and compile
the package, I just get a message "Package has been installed", but I have
no component installed, hence nothing to drop on the form.
3) If I use C++ 1 and install the .OBJ file, and recompile the .CCL library
I get a Link Error "Unable to open SYSINIT.OBJ", I do not know what that
file is.
Note the .OBJ file was compiled using Delphi 4 command line compiler using
the (undocumented) -JPH commmand. This produced .HPP header files from the
original .PAS files.
Chris
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Myles Penlington
Sent: Monday, 20 September 1999 10:09
To: Multiple recipients of list delphi
Subject: RE: [DUG]: Using .OBJ files compiled in D4, in C++ Builder
How about adding all those {$EXTERNALSYM xxx } to your delphi source that
seems to be scattered about the VCL? I believe these stop the C++ linker
errors from occurring.
> -----Original Message-----
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
