The JEDI Code Library (JCL) and JEDI Visual Component Library (JVCL) installers use the command line compiler dcc32.exe to compile the packages on the target computer. The JEDI projects use this technique to be a “source code release” and to support all the Delphi/C++Builder versions without increasing the download size with *.dcu, *.dcp, *.bpl, *.obj, *.lib and *.bpi files for all compiler versions.
The recently released Delphi/C++Builder Starter Edition doesn’t come with a command line compiler. This makes it impossible for all component installers, that rely on dcc32.exe, to compile the packages. And so the JCL and JVCL “source code releases” can’t be installed. Some time ago I had built a JCL and JVCL binary installer for RAD Studio 2009 and 2010, but I discontinued this binary installer with the rise of RAD Studio XE. Now that a binary installer is the only way to install the JCL and JVCL into the Starter Edition, I have revived the binary installer and made the creation of the binary installer (a InnoSetup installer) much easier with less hand work.
The JCL Binary Installer is based on the JCL’s svn trunk revision 3489.
Jedi Code Library Binary Installer for XE
The JVCL Binary Installer is based on the JVCL’s svn trunk revision 12971.
Jedi Visual Component Library Binary Installer for XE
(You must install the JCL with the JCL Binary Installer if you want to install the JVCL with the Binary Installer)
Pingback: JCL and JVCL Binary Installer for XE and Starter Edition
Source code distributions can be installed manually as long as source packages are available – and if it works calling the command line compiler it means it will work from the IDE too. Of course it is much slower, and can requires some attempts if the proper sequence is not documented, or a project group is not available, but it works. Maybe it will be a good push to some component developer to release libraries that can be properly built, instead of the mess I encounter sometimes.
The JCL and the JVCL have package groups that can be compiled in the IDE. But I find it hard to install 30 packages by hand.
And this is very useful also for the 30 days trial version, where the command line compiler is missing too.
Thank you very much for your effort!
if youhave no dcc32.exe, simply use bds.exe to compile.
You can start Delphi IDE with Parameter tu Build Project / ProjectGroups.
After Compiling Delphi IDE will close. The Compile Output (Warnings & Hints) are saved in a OutputFile.
exsample:
bds.exe c:\temp\PackageGroup.groupproj -b -oc:\temp\compile.log
or
bds.exe c:\temp\Package.dproj -b -oc:\temp\compile.log
All Parameter are stored in *.dproj Files of Packages.
This will work.
All Comanndlineparameters can be read in the onlinehelp.
For D2007 this is: ms-help://borland.bds5/devcommon/idecommandline_xml.html
For Delphi XE this is: ms-help://embarcadero.rs_xe/rad/IDE-Befehlszeilenoptionen.html
(German Delphi Help)
cu
MaBuSE
Pingback: Delphi Starter Editionen am Start? - Seite 33 - Delphi-PRAXiS
> the only way to install the JCL and JVCL into the Starter Edition
it is not so
one can aways open .dcp files into IDE and compile and install them like any other packages
installer is convenient and easy way to do the same
but not the only.
don’t lower the bar 🙂 i’m tired of guys, who cannot install package from source, yet call themselves Delphi programmers, and represent average level of all Delphi programmers in the eyes of many 🙁
А как это сделать? Другие пакеты инсталировать получается, а тут не понял что запустить (есть компилировать, собрать, запустить, но нет инсталировать, а запустить выдает ошибку).
And how? Other packages install it turns out, but here do not understand that to run (a compile, assemble, run, but not install, and run an error).