View Issue Details

IDProjectCategoryView StatusLast Update
0005990JEDI VCL02 Installationpublic2013-01-15 16:20
ReporterachristodisAssigned Toobones 
Status resolvedResolutionwon't fix 
Product VersionDaily / GIT 
Target VersionFixed in Version 
Summary0005990: Add support for registering DCU path when installing both JCL and JVCL
DescriptionIn order to place DCU-files also in a centralized way like with BPL and DCP files, support is needed to register the path to the place where DCU files should be placed.

If possible, short-hand notation like $(DCU) is wanted (in case defined in the setup)

TagsNo tags attached.



2012-09-27 10:01

developer   ~0020232

That change should be made very carefully. The JVCL Installer deletes all *.dcu files in its DCU-Output directory that don't belong to the current JVCL source code base. So if you point the DCU output directory to a "shared" directory, this directory will only contain the JVCL *.dcu files after the installation. All other *.dcu files will be deleted.


2012-09-27 11:38

reporter   ~0020233

Well, if a restriction about starting all .pas files (.dcu) with jv(cl) or jcl, then, when changes are done, you could restrict the delete to jv(cl)*.dcu and jcl*.dcu so any others are kept.


2012-09-27 12:44

developer   ~0020234

That wouldn't hold for something like "jvalue.pas" that doesn't have anything to do with the JVCL. That "clean up" code must be deactivated when compiling to a different DCU output directory. But then we are back at a mix of old and new *.dcu files causing trouble when compiling applications (that's why this clean up code was introduced)


2013-01-15 16:20

administrator   ~0020390

I'm sorry, but I don't see the point for this. I mean, if you don't want to recompile the DCUs everytime, simply add the DCP path to your search path.

Issue History

Date Modified Username Field Change
2012-09-23 19:32 achristodis New Issue
2012-09-27 10:01 AHUser Note Added: 0020232
2012-09-27 11:38 achristodis Note Added: 0020233
2012-09-27 12:44 AHUser Note Added: 0020234
2013-01-15 16:20 obones Note Added: 0020390
2013-01-15 16:20 obones Status new => resolved
2013-01-15 16:20 obones Resolution open => won't fix
2013-01-15 16:20 obones Assigned To => obones