I've been setting up FinalBuilder server and suddenly realized that I'd have to install Delphi on my build server. That means a big, bloated app, updates, etc. I looked around a bit and see that all I need is a few executables and the appropriate libraries, and I can get a build just using DCC32.exe.
After doing this at the command line myself, I went to see how FinalBuilder would think about it. The settings tab for Delphi doesn't have a place to put the path to the compiler - it expects to "know" where all that is based on the version. (presumeably info in the registry)
I was able to create a "dos command" action that calls the compiler, but now I lose all the options and settings that come with using the Delphi compiler option. (especially version and resource management)
FinalBuilder uses various registry entries to know about things like Delphi install paths.
If you start looking under HKLM\Software\Borland\Delphi\[version] then you'll see most of the relevant bits and pieces that you'll need to install on your build machine.
FYI, I don't know whether doing this is prohibited by the Delphi EULA, and in either case it's not a recommended or supported configuration for FinalBuilder use. It may work fine, though.
PS FYI, the "DOS Command" action is a much misused action. We strongly recommend using the "Execute Program" action to run everything apart from built-in actual DOS commands (like dir.)
Just wondering - did you (or anyone) get this to work? I was about to try putting in just the RootDir and library Search path entries in the registry and see whether FinalBuilder would cope.
I’t not really a case of FinalBuilder coping. All it needs are the registry entries so that it knows where to find Delphi and it’s library path. The real issue is getting delphi to work when it’s not installed, which is a lot more onerous with the newer versions and their licensing/activation policy than it was back in D7’s time.