(08-31-2021, 06:49 AM)wzehntner Wrote: Error dclIndyCore160.bpl
[DCC Fataler Fehler] IdDsnPropEdBindingVCL.pas(80): F1026 Datei nicht gefunden: 'IdIDN.dcu'
Like I said, all of the DCUs should be going to the same folder, preferably the IDE''s default output folder. If they are not, then there is a misconfiguration somewhere.
(08-31-2021, 06:49 AM)wzehntner Wrote: File exists in master\Lib\System
copying to Core =>> compiles now
Don't do that. System's .DCU files do not belong in Core's source folder.
(08-31-2021, 06:49 AM)wzehntner Wrote: Error dclIndyProtocols160.bpl
[DCC Fataler Fehler] IdDsnSASLListEditorFormVCL.pas(62): F1026 Datei nicht gefunden: 'IdIDN.dcu'
copying to Protocols =>> compiles now
Don't do that. Core's .DCU files do not belong in Protocol's source folder.
(08-31-2021, 06:49 AM)wzehntner Wrote: In the instruction it says to install 2 design-time packages:
1. dclIndyCoreX0.bpl
2. dclIndyProtocolsX0.bpl
I can not find any of these files ...
Yes, you can. They are the ...160 packages you just compiled. Perhaps you missed this note at the very top of the instructions?
Quote:All package names are followed by X0 (where X0 is your Delphi/C++Builder/RAD Studio product version).
For Example:
Delphi/C++Builder 6 is version 6.0, so the Indy packages are:
IndySystem60, IndyCore60, IndyProtocols60, dclIndyCore60, dclIndyProtocols60
RADStudio 10 Seattle is version 23.0, so the Indy packages are:
IndySystem230, IndyCore230, IndyProtocols230, dclIndyCore230, dclIndyProtocols230
Refer to Embarcadero's documentation for the complete list of which package version number belongs to which product release.
So, in your case, XE2 is version 16.0, so X0 is 160.
(08-31-2021, 06:49 AM)wzehntner Wrote: Edit3: (3 hours later) I found old bpl-files from 2012
Where can I find the newer files ?
Wherever your compiler is setup to output them.