Loadrex

Indy 10 Installation Instructions

All package names are followed by X0 (where X0 is your Delphi/C++Builder/RAD Studio product version).

Installing components under Delphi XE3 is a nightmare. First I need to add source files to Tools - Options - Library then I need to find a normal package and compile it finally I need to find Stack Overflow. Close all projects in IDE, click Component - Install packages. From the main menu, find the package that contains your component, select it and click Remove button. Install the 32-bit version of the component as it described above and add to Tools/Options/Delphi Options/Library/Library Path, selected platform: 64-bit Windows the path of the Win64 subfolder of the component.

For Example:

A Delphi component can be used to add functionality to your Delphi application or project, without spending a lot of time writing it yourself. Delphi 7.0 Delphi 6.0 Product Class Business Components Test and Review Status Installation Tested - Yes. Read more Show more. For Delphi/CBuilder XE and higher LiteDAC additionally supports. Question Description. I am preparing an installer to install my component package into Delphi XE without having to manually fiddle in the IDE.How do I install a Delphi component package (for example, MyComponent.bpl) into Delphi without having to manually do it via the ‘Install Packages’ menu item?

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.

Note: this naming convention will be changed in Indy 11 to drop the version numbers from the package names!

Before you begin

Some important notes before you install Indy 10:

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

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

• In D/CB/RAD 2009-XE, Embarcadero's DataSnap framework is compiledagainst the Indy 10 packages that ship with the IDE. Installing a newversion of Indy will render DataSnap unusable, as it will not be ableto load the Indy packages anymore, and DataSnap cannot be recompiled byend users. If you need to use DataSnap, then you will need to maintainthe original Indy 10 packages for use in DataSnap projects. You canuse a separate installation of Indy 10 for non-DataSnap projects. Thiswas addressed by Embarcadero in D/CB/RAD XE2 so Indy 10 upgrades andDataSnap can co-exist.

• 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.

• In D/CB/RAD XE2 Update 4, the DCLIPINDYIMPL160.BPL package has a link to Indy's IdHeaderCoderUTF unit, which does not exist in Indy anymore and was replaced with the IdHeaderCoderIndy unit. Installing a newer version of Indy will cause a linker error in this package. According to Embarcadero, this package is the only design-time package that should require rebuilding after upgrading Indy with any kind of interface changes or unit list changes. The source for this package is provided in XE2, users can find it under $(BDS)sourceindyimplementation.

Update: interface changes have been made to Indy since XE2's release, so Embarcadero's IndyPeerImpl.pas unit will no longer compile as-is. Have a look at the following discussion on the Embarcadero forums for some of the issues you may run into and how to work around them: https://forums.embarcadero.com/thread.jspa?threadID=90684 (due to a server crash, the earlier discussion thread has been lost. Refer to the following archived discussion: http://www.codenewsfast.com/cnf/thread/0/permalink.thr-ng1921q9564, in particular this reply: http://www.codenewsfast.com/cnf/article/1430996872/permalink.art-ng1921q9582).

• In D/CB/RAD XE3, Embarcadero changed the signature of the TIdUDPServer OnUDPRead event in the bundled copy of Indy 10. This was done in an attempt to address a slew of related Quality Central bug reports (#88816, #89298, #89662, #92067, #93672, #94969, #97943, #99863, #103088, #104825), to allow the Delphi compiler to generate RTTI that allows the IDE to produce an event handler that is compatible with both Delphi and C++Builder without errors, and without requiring additional RTL/compiler changes (which are actually needed to solve the root cause of the original errors). Specifically, the AData parameter of the OnUDPRead event was changed from a Dynamic Array to an Open Array. Consequently, the parameter signature is now different, which means that pre-existing user code that uses the OnUDPRead event in earlier D/CB/RAD versions will no longer work correctly without being updated accordingly. This change was NOT approved by the Indy development team, and Embarcadero did NOT apply their change to other areas of Indy that are affected by the same issue, such as the TIdTelnet OnDataAvailable and IdIPMCastClient OnIPMCastRead events. To maintain a single codebase, these changes have been merged into subsequent SVN releases of Indy 10.

• In D/CB/RAD XE3+, Embarcadero's Metropolis UI LiveTile framework is compiled against the Indy 10 packages that ship with the IDE. Installing a new version of Indy will render LiveTiles unusable, as it will not be able to load the Indy packages anymore, and LiveTiles cannot be recompiled by end users. If you need to use LiveTiles then you will need to maintain the original Indy 10 packages for use in LiveTile projects. You can use a separate installation of Indy 10 for non-LiveTile projects. This has not been addressed by Embarcadero yet so Indy 10 upgrades and LiveTiles can co-exist.

There have been some reports that when compiling Indy for XE3, the compiler may complain about missing OTARES files. This is caused by a {$R *.otares} statement in the DPK files. The files that are checked in to SVN do not contain this statement, but apparently the compiler may decide to insert it on its own. If this happens, just remove the statement and recompile again. Indy does not use OTARES files. They are generated by the IDE when it encounters unknown resources while upgrading a project from an older IDE version.

Online Package Managers

Lazarus 1.8 and later has a built-in Online Package Manager.Indy has been included in the OPM, and thus can be installed intoLazarus with a single click, instead of having to manually download,compile, and install Indy yourself.

In a future version, Indy will eventually be included in Embarcadero's GetIt Package Manager to automate the following installation steps for you.

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 uninstalledfirst:

• Remove the pre-compiled design-time BPL files - dclIndyCoreX0.bpl anddclIndyProtocolsX0.bpl - from the IDE via the 'Components > InstallPackages' dialog.
• Delete all of the existing binaries - IndySystemX0.*, (dcl)IndyCoreX0.*, and (dcl)IndyProtocolsX0.*
• Delete any Indy 10 source files, if present.
• Be sure to check for files in the IDE's bin, lib, and source folders, Indy subfolders, and OS system folders.
  

Delphi Compilation

You can either:

• Use the command-line FULLD#.BAT script that corresponds to your Delphi version.

• Open the individual DPK files in the IDE and compile them, in the following order:

1. IndySystemX0.dpk (in LibSystem)
2. IndyCoreX0.dpk (in LibCore)
3. IndyProtocolsX0.dpk (in LibProtocols)
4. dclIndyCoreX0.dpk (in LibCore)
5. dclIndyProtocolsX0.dpk (in LibProtocols)

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.

Note for Cross-Platform compiling:

The current Indy 10 package projects are set for Windows compilations. The IndySystem and IndyProtocols packages do have a few platform-specific units in them, which are conditionally compiled via IFDEF statements in the DPK files. This is fine for command-line compilations, but the IDE usually doesn't handle IFDEFs in DPK files very well, and this can also cause an associated DPROJ file to be out of sync with its DPK file. So this may lead to issues if you want to compile Indy 10 via the IDE for non-Windows platforms (in Delphi versions that support this). You might need to edit the IndySystem project to remove the IFDEFs and replace the IdStackWindows, IdWinsock2, and IdWship6 units with the IdStackVCLPosix and IdVCLPosixSupplemental units instead, and then edit the IndyProtocols project to remove the IFDEFs and the IdAuthenticationSSPI and IdSSPI units. Perhaps in a future release, we will try to automate/cleanup this better.

C++Builder Compiling

Indy does not include BPK project files for C++Builder, so you will need to use the FULLC#.BAT command-line script that corresponds to your version of C++Builder. This will compile the DPK files using C++Builder's command-line Delphi compiler (dcc32.exe) or MSBuild toolchain (msbuild.exe), depending on IDE version.

After Compiling

In your Indy directory you should now see some compiled DCU files. Open the IDE and go to the 'Tools > Environmentoptions > 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

Delphi Xe Download

FreePascal/Lazarus Installation

• Documents:
• Documentation

  Search in JCL help

• JCL links at :

• JCL links at Github

• About:

• 1 JCL: JCL Installation
  • 1.1Automated installation

Automated installation

Default installation

If you're using either FreePascal, or a trial version of Delphi/C++Builder, or Turbo Delphi, see the 'Manual Installation' section below.

Delphi Xe Install Components

Otherwise (in most cases), the JCL should be installed using the automated installation process.

Automated Installation Process (recommended)

The recommended way to install the JCL is to run the source installer: once you've extracted the archive downloaded from one of the software sources, navigate into the JCL directory and execute 'install.bat'.

For each version of Delphi/C++Builder installed on the computer, this installer allows you customize the conditional defines, update the environment for the JCL, install some documentation, make the library units, install the packages and finally compile the demos. Castaway 2 download swf.

The default options are recommended, make sure you understand what these options do before toggling their states. Finally you can install the library by clicking on the 'Install' button at the bottom of the form.

Binary packages

Delphi Xe 10

TODO

Installation for Turbo Delphi

The JEDI Code Library can be compiled targetting Turbo Delphi Explorer and Turbo Delphi Professional. Turbo Delphi Professional is recognized as BDS 2006, you have to download its command line compiler from CodeGear website at https://downloads.embarcadero.com/Item/24146 to install the full JCL on this tool.

To install the JCL targetting Turbo Delphi Explorer, consider the following checks:

• If you have an other supported version of Delphi/C++Builder on this computer, it should automatically be detected and the installer will process as usual.
• If you only have Turbo Delphi Explorer (and no other tools) on the computer, the installer cannot be compiled. You have to use the Turbo Explorer flavor of the JCL that contains a precompiled installer. However, you will not be able to install any experts.

Installation on C#Builder 1 and Delphi 8

These products cannot be used to build the JCL installer, you need an other supported product to install JCL experts on these products. These products are not able to use the JCL library as a runtime library. You cannot write managed applications and managed packages based on the JCL.

These products are not shipped with their native compilers, you have to download it from codecentral http://cc.embarcadero.com/:

• The item https://downloads.embarcadero.com/Item/21333 contains the native compiler to be installed in Delphi 8.
• The item https://downloads.embarcadero.com/Item/21334 contains the native compiler to be installed in C#Builder 1.

These zip files have to be extracted in the products directory using the standard pattern:

Manual Installation

Although it is not recommended, a manual installation is possible. You will have to manually configure options for the library. That is done by modifying an included file.

For each tool you want to install the JCL in, repeat the following steps:

1. Open and edit included file to customize options:
   • For C++Builder 6: sourceincludejclc6.inc
   • For Delphi 6: sourceincludejcld6.inc
   • For Delphi 7: sourceincludejcld7.inc
   • For Delphi 2005: sourceincludejcld9.inc
   • For BDS 2006 (Delphi and C++Builder): sourceincludejcld10.inc
   • For CodeGear RAD Studio 2007 (Delphi for Win32 and C++Builder): sourceincludejcld11.inc
   • For Delphi 2009 and C++Builder 2009: sourceincludejcld12.inc
   • For Delphi 2010 and C++Builder 2010: sourceincludejcld14.inc
   • For Delphi XE and C++Builder XE: sourceincludejcld15.inc
   • For FreePascal: sourceincludejclfpc.inc
2. In the IDE, open and compile package Jcl.dpk (or Jcl.bpk for C++Builder) located in a subdirectory of the 'packages' directory matching your version of the IDE. This package doesn't have to be installed since it doesn't provide any components.
3. If you want to install experts, open package JclBaseExpert.dpk and compile it, then you can install all the experts you want (packages are located in the same directory).