Indy 10 Installation Instructions

All packages are followed by X0 (where X is your Delphi/C++Builder/RAD Studio verison).
Example: For Delphi/C++Builder 6, the IndySystem package would be named: IndySystem60.dpk

Note: this naming convention will be changed in Indy 11.

Before you begin

Some notes before you install Indy 10:

1) The SuperCore package is very outdated and not currently usable. Don't even try to compile or install it.

2) There was no Delphi/C++Builder v13, so do not use the Indy...130 packages.  For D/CB/RAD 2009, use the Indy...120 packages.  For D/CB/RAD 2010, use the Indy...140 packages.

3) In D/CB/RAD 2009-XE, Embarcadero's DataSnap framework is compiled against the Indy 10 packages that ship with the IDE.  Installing a new version of Indy will render DataSnap unusable, as it will not be able to load the Indy packages anymore, and DataSnap cannot be recompiled by end users.  If you need to use DataSnap, then you will need to maintain the original Indy 10 packages for use in DataSnap projects.  You can use a separate installation of Indy 10 for non-DataSnap projects.  This was addressed by Embarcadero in D/CB/RAD XE2 so Indy 10 upgrades and DataSnap can co-exist.

4) In D/CB/RAD XE2 up to, and including, Update 3, an erroneous dependancy on Indy has been identified in Embarcadero's dclnet160.bpl package.  Installing a new version of Indy will cause this package to fail to load correctly in the IDE, preventing all contained components (such as THTTPRIO, TXMLDocument, TWeb*Dispatcher, T*Producer, TTcp*, TUdp*), as well as Wizards and Property Editors for them, from appearing at design-time.  The run-time components can still be instantiated dynamically in your run-time code, though!  Embarcadero is aware of the problem, and has already fixed the problem for XE3.  Removing the dependancy causes an interface change in dclnet.dcp, and Embarcadero does not normally release interface changes in product Updates, however the change is internal to Embarcadero's code only and should not effect end users, so Embarcadero is hopeful that the fix can be included in a near-future XE2 Update.

Download

Indy 10 source code can be downloaded from the Development Snapshot. Extract the source files to a folder of your choosing on your PC.

If Indy 10 is already installed, it needs to be uninstalled first.  Remove the pre-compiled BPL files - dclIndyCoreX0.bpl and dclIndyProtocolsX0.bpl - from the IDE via the "Components > Install Packages" dialog.  Then delete all of the existing binaries - IndySystemX0.*, IndyCoreX0.*, IndyProtocolsX0.*, dclIndyCoreX0.*, and dclIndyProtocolsX0.* - and delete any Indy 10 source files, if present.

Delphi Compilation

You can either:

1) use the command-line FULLD#.BAT script that corresponds to your Delphi version.

2) Open the individual .dpk files in the IDE and compile them, in the following order:

1. IndySystemX0.dpk (in Lib\System)
2. IndyCoreX0.dpk (in Lib\Core)
3. IndyProtocolsX0.dpk (in Lib\Protocols)
4. dclIndyCoreX0.dpk (in Lib\Core)
5. dclIndyProtocolsX0.dpk (in Lib\Protocols)

If you encounter the following linker error:

RLINK32: Error opening File packagename.drf

Try this workaround:

1. Delete all .DCP and .BPL files for the package.
   
2. Open the .DPK file in the IDE, go into its Project Options, and set the Build Control setting to "Explicit Rebuild".
   
3. Rebuild the package.
4. Repeat these steps for each dependant package.

C++Builder Compiling

Indy does not include C++ .bpk project files, so you will need to use a FULLC#.BAT command-line scripts that corresponds to your version of C++Builder.  This will compile the .dpk files using C++Builder's command-line Delphi compiler (dcc32.exe).

After Compiling

In your Indy directory you should now see some compiled .dcu files. Open the IDE and go to the "Tools > Environment options > Select Library" dialog tab. Now add the path to your files into the filepath collection. Click Ok.

Now install the two design-time packages into the IDE in the following order:

1. dclIndyCoreX0.bpl
2. dclIndyProtocolsX0.bpl

Kylix Installation

Kylix Instructions

FreePascal/Lazarus Installation

Corporate Sponsors