Since I work on several projects that require multiple Delphi installations, I needed a way to start the correct Delphi IDE and call the correct command line compiler for each of these projects. There apparently is no way to automatically detect the Delphi version from the .dof,.dpr or .dproj file (or at least this is limited), so I added batch files to these projects that call the correct Delphi version.
Since I work on several projects that require multiple Delphi installations, I needed a way to start the correct Delphi IDE and call the correct command line compiler for each of these projects. There apparently is no way to automatically detect the Delphi version from the .dof,.dpr or .dproj file (or at least this is limited), so I added batch files to these projects that call the correct Delphi version.
One of the things that irked me was that I had to adapt these batch files whenever I was working on a different computer and Delphi was not installed in the default installation directory. Finally I found a solution for this: The required information is stored in the registry at
HKCU\Software\(Borland|CodeGear|Embaracdero)\(TheDelphiVersion)\root
And the place where this is stored does not vary. I set out to find a way to read the registry from a batch file and found this answer on stackoverflow.
So, here is the result. A batch file that, when called with a Delphi version as parameter, returns the directory it is installed in:
http://blog.dummzeuch.de/2014/04/17/determine-the-delphi-installation-directory-from-a-batch-file/
One of the things that irked me was that I had to adapt these batch files whenever I was working on a different computer and Delphi was not installed in the default installation directory. Finally I found a solution for this: The required information is stored in the registry at
HKCU\Software\(Borland|CodeGear|Embaracdero)\(TheDelphiVersion)\root
And the place where this is stored does not vary. I set out to find a way to read the registry from a batch file and found this answer on stackoverflow.
So, here is the result. A batch file that, when called with a Delphi version as parameter, returns the directory it is installed in:
http://blog.dummzeuch.de/2014/04/17/determine-the-delphi-installation-directory-from-a-batch-file/
I made some work on this area, check this unit http://code.google.com/p/delphi-dev-shell-tools/source/browse/trunk/units/uDelphiVersions.pas which include some classes to detect the Delphi ide version from a .dproj file, the current active configuration (Debug, Release) and platform (Win32, Win64, Android, OSX) and another useful information.
ReplyDeleteGreat! You made a universal version which I can use in place of the script in http://wiert.me/2014/04/08/spring4d-now-has-projects-for-appmethod-but-it-cannot-support-appmethod-in-the-automated-build-engine/ (:
ReplyDeleteNote that sometimes (I've not tracked down yet when) the information is in HKLM, not HKCU.
ReplyDeleteI think it's the other way round: The information is always in HKCU, but only sometimes in HKLM.
ReplyDeleteI think that depends if your machine has different users using Delphi or not. Need to dig into this deeper some day.
ReplyDeleteFYI; I haven't played with this issue. But thought I'd mention that... 32-bit apps (delphi) on a 64-bit platform will have HKLM redirected to a subkey called "Wow6432Node"
ReplyDeleteVin Colgin thanks for the tip Vin!
ReplyDeleteI just pushed a new version of that script.
ReplyDeleteFrom my experience, the registry key is in HKLM after installation, and it gets copied to HKCU when you start IDE from a user account if it doesn't already exist. (If you delete it from HKCU it will be copied again from HKLM.)
ReplyDeleteOndrej Kelle Thanks, that makes a lot of sense.
ReplyDeleteHere it is: https://bitbucket.org/jeroenp/besharp.net/commits/69f8e6ec0dce6eaa4f1e44e5465f47e7b5be6237#chg-Native/Delphi/Scripts/List-Delphi-Installed-Packages.ps1
ReplyDelete