jcl-jvcl-20070824,for delphi

-------------------------------------------------------------------------------- JEDI Code Library Unstable 1.101 Build 2647 30-May-2007 -------------------------------------------------------------------------------- Content of this file About this release Supported tools Installation notes Manual installation Distribution content Giving your feedback Reporting bugs Downloads of stable sources Development sources Getting involved in JCL development -------------------------------------------------------------------------------- About this release JCL release 1.100 provides an updated support for all targets (including CodeGear Delphi 2007 for Win32 and CodeGear C++Builder 2007). As always, multiple bugs have been fixed; for detailed change logs, use the facilities of our Subversion repository at Sourceforge.net http://sourceforge.net/projects/jcl/, see below. Head changes: - JclPeImage is significantly updated: it now supports 64-bit applications and libraries. - JclDebug is significantly updated: .jdbg files contain informations about all segments of code. A new option was added to limit exception handling to the main thread of the application. - PCRE (http://www.pcre.org/) updated to version 7.0. PCRE code can be included in the application not requiring "pcre.dll" anymore (experimental - read the comments at the beginning of source\common\pcre.pas for details and modifications to enable this feature). - JclMail : different file names can be specified for attachements - Collection of stream classes to make basic operations easier (getting random data, multiplexing several streams, buffering an other stream, being notifyed on changes, reading common data types, scoping a stream, delegating read/write/seek operations. - Integration of the JCL help into the help system of Delphi 2005, BDS 2006, Turbo Delphi and RAD Studio 2007. - New IDE expert to have TortoiseSVN (http://tortoisesvn.tigris.org/) and TortoiseCVS (http://tortoisecvs.sourceforge.net/) commands integrated in all supportted IDE. Important: - Note that the package naming has changed: the same package name is used by all versions of the compiler supporting suffixes (C++Builder 6, Delphi 6, Delphi 7, C#Builder 1, Delphi 8, Delphi 2005, BDS 2006 and RAD Studio 2007); a different suffix is added for each target to the BPL file name (for BDS 2006, the library file is named jcl100.bpl). The installer tries to remove old packages. 3rd party packages requiring old DJcl* resp. CJcl* packages need to be changed to accomodate the new naming scheme or they will cause conflicts in the IDE at load time. - DCP files are now created in the lib\target subdirectory of the JCL installation. 3rd party packages requiring JCL packages need to have this path in their "browse path" option to compile. (Windows only) Installation options: Packages compiled by the JCL installer don't contain any debug informations to keep their size as small as possible. The JEDI Code Library packages are required by some 3rd party packages (including the JEDI Visual Component Library - JVCL), the installer generates them if the "Packages" node is checked. The installer can generate MAP informations for each package. These informations can be linked into binaries to become JCL debug data or be converted to .jdbg files. Once linked MAP files could be deleted. These options are subnodes of the "Packages" node. For BDS 2006, the compiler introduced a new option to make the same packages available in C++, by checking the "Dual packages" option of the "Packages" node, you will be able to call functions of the JCL from C++ code. .net Framework support: A subset of JCL units was worked over to support Delphi.Net (Delphi 2005 & BDS 2006). The packages belong to the Jedi.Jcl namespace. The installer can generate these packages for Delphi 2005 and BDS 2006, it displays an other tab to configure options and directory. The installation process is similar to the native targets. -------------------------------------------------------------------------------- Supported Tools The JCL can be compiled and installed in the following environments Only runtime support: - Kylix 3 (cf Installation notes) Only design-time support (only experts): - C#Builder 1 (cf Installation notes). - Delphi 8.net (cf Installation notes). Both supports (run time and design time): - Delphi version 5, 6, 7. - C++Builder version 5 & 6. - Delphi 2005 (Delphi Win32 and Delphi.net personalities). - Borland Developer Studio 2006 (Delphi Win32, C++Builder Win32, Delphi.net and C#Builder personalities). - Turbo Delphi (explorer and professional - cf Installation notes). - CodeGear RAD Studio 2007 (Delphi Win32 and C++Builder Win32 personalities). -------------------------------------------------------------------------------- Installation notes - Not every unit supports all tools. Look out for *.exc files in the tool- specific lib/subdirectories for a list of units excluded from compilation. - Kylix 3 Delphi/C++ installation is back but specific code has not been tested with the latest versions of the kernel. Please ensure you use the flavor of the JCL with Unix EOL. - Free Pascal (http://www.freepascal.org/) support has not been updated for this release; most units fromsource/common should work with FP 2.0, as tests with a 2.0 beta (1.9.8)indicated, but this has not been verified. Note that there are no plans to support FP versions from the 1.0 branch. 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 http://www.codegear.com/Default.aspx?tabid=160 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 becompiled. 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.codegear.com/). The item (http://codecentral.codegear.com/Download.aspx?id=21333) contains the native compiler to be installed in Delphi 8. The item (http://codecentral.codegear.com/Download.aspx?id=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: Executable files (exe and dll) - BDS\X.0\bin Compiler files (dcp and dcu) - BDS\X.0\lib Toolsapi source files - BDS\X.0\source\ToolsAPI Default installation For all others versions of Delphi, C++Builder and BDS, simply launch Install.bat and the installer window will let you configure options and install the library. -------------------------------------------------------------------------------- Manual Installation Although it is not recommended, a manual installation is possible. You will have to manually configur