Indy10installation de

 

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).  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.  11.  Note: the SuperCore package is outdated and not currently usable.  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.  package s. For D/CB/RAD 2010, 2010, use the Indy...140 packages.  packages.  Note: In D/CB/RAD 2009-XE, DataSnap uses Indy 10 internally 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 Snapshot and  and choosing extract the files to a folder of your onsource your PC.

Corporate Sponsors  

 

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

If Indy 10 is already installed, it needs to be uninstalled uninstalle d first. Remove the the pre-compiled pre-compiled BPL files - dclIndyCoreX0.bpl and dclIndyProtocolsX0.bpl dclIndyProtoc olsX0.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  Compilation  You can either: 1) use the command-lin command-line e 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. IndySyste IndySystemX0 mX0.dpk .dpk (in Lib\Sys Lib\System) tem) 2. Indy IndyCore CoreX0.d X0.dpk pk (in Lib\C Lib\Core) ore) 3. Ind IndyPr yProto otocol colsX sX0.d 0.dpk pk (in Lib\Protocols) 4. dclI dclIndyC ndyCoreX oreX0.dp 0.dpk k (in Lib\C Lib\Core) ore) 5. dclI dclIndyP ndyProtoc rotocolsX olsX0.dp 0.dpk k (in Lib\Protocols)  

If you encounter the following linker error: RLINK32: Error opening File  packagename.drf  package name.drf Try this workaround: 1. Delete Delete all .DCP and and .BPL .BPL files files for the the package. 2. Ope Open n the the .DPK file in the IDE, IDE, go into into its Project Options, and set the Build Control setting to "Explicit Rebuild". 3. Rebuil Rebuild d the the packa package ge.. 4. Repe Repeat at these these steps steps for each each depen dependant dant package. C++Builder Compiling  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 version of C++Builde C++Builder. r. This will will compile the .dpk files using C++Builder's command-line Delphi compiler (dcc32.exe). (dcc32.exe).  After Compiling In your Indy directory you should now see some compiled .dcu files. Open the IDE and

22/08/2011 Page 2 of 3

 

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

22/08/2011 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. dclIn dclIndyC dyCore oreX0 X0.bp .bpll 2. dcl dclIn IndyP dyProt rotoco ocolsX lsX0.b 0.bpl pl Kylix Installation  Installation  Kylix Instruction Instructions s  FreePascal/Lazarus Installation Lazarus Installation  Installation 

home

about

license

support

K/Base

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

site map

links

Website design by RuInternet.ru