Indy

Page 1 of 3

home

about

license

support

K/Base

search

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. Note: the SuperCore package is outdated and not currently usable. Note: 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. Note: In D/CB/RAD 2009-XE, DataSnap uses Indy 10 internally. Installing a new version of Indy will render DataSnap unusable, as it will not be able to load the Indy packages anymore. DataSnap is compiled against the Indy packages that ship with the IDE, 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. This will be addressed by Embarcadero in D/CB/RAD XE2 so Indy 10 upgrades and DataSnap can co-exist. Download source from the Development Snapshot and extract the source files to a folder of your choosing on your PC.

Corporate Sponsors

http://www.indyproject.org/Sockets/Docs/indy10Installation.de.aspx

22/08/2011

Indy

Page 2 of 3

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

http://www.indyproject.org/Sockets/Docs/indy10Installation.de.aspx

22/08/2011

Indy

Page 3 of 3

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 Lazarus Installation

home

about

license

support

K/Base

site map

links

Copyright 1993 - 2008 Chad Z. Hower (Kudzu) and the Indy Pit Crew.

Website design by RuInternet.ru

http://www.indyproject.org/Sockets/Docs/indy10Installation.de.aspx

22/08/2011