Been trying some more…
It seems like the “Regenerate resource” option is enabled by default if “Use Version Info from project file” is enabled, which I guess would make sense.
As for the Eurekalog option, I tried it with a completely empty new Delphi project, and it worked fine, but for some reason I just cannot get it to work with another one of my projects. So that might not be a Final Builder problem either, but I really don’t know what else to try at the moment.
Hi Michael
I have been testing with eurekalog 6.02 trial version, and I cannot get it to work at all with FB5 and Delphi 2007. I’m not sure why, I check that we are definitely calling ecc32.exe and that is in the correct folder etc, but nothing seems to happen. It may be because I’m only using the trial at this time, I’ll have to contact the author to see if this is the case. It did work fine with Delphi 2006 though…
The Regenerate resource option behavior is correct, to generate version info in the application the resource file has to be regenerated.
Hi Vincent,
it may be a trial thing. My memory might be wrong, but I think it is entirely possible that the command line compiler is not available in that version.
In any case, after spending two hours debugging, I’m 99% sure that this is not a Final Builder issue, so don’t bother investigating. If anybody has a similar problem: It seems my project file had an UTF-8 signature at it’s beginning, which threw off the parsing code of ecc32, so that it failed to find the project name and therefore the map file. Going to report this to Fabio now…
Is there any estimation when FinalBuilder will be shipped with support for D2007?
Regards Roland
Roland, I don’t know when a major release will be done, but the downloads here have worked just fine from the first release. Matthew
see this thread for some more information:
https://www.finalbuilder.com/forums.aspx?forumid=15&postid=3532&view=topic
And as Matthew mentioned, the current test build should work fine.
Hallo.
I guess I found an error in the latest test build. We have about 240 delphi projects that are compiled with Finalbuilder. Everything worked fine with Finalbuilder 4 and Delphi 2006 but Finalbuilder 5 cannot compile any of our Delphi 2007 projects.
We are using relative paths in our projects’ search paths and the Finalbuilder actions are configured to read them from the project files. This way the compiler is not able to find the required units. I also tried to set the relative paths in the action manually but that did not help. At last I replaced the relative paths in the action with absolute paths and this helped. Unfortuantely this is not an option for us beacause every developer in our team has his/her working copy in a different location. Therefore we developed some IDE tools to help us manage the relative search paths.
Is it no longer possible to use relative paths or is it just some kind of bug?
Kind regards
Kay Zumbusch
Hi Kay
I will have to test this on monday, but my suspicion is with the delphi compiler. None of the path handling code changed between finalbuilder 4 and 5. One thing you can do is turn on the “Keep generated .cfg” option on the compiler settings page of the delphi action. After running there will be a file in the delphi project folder with a .used extension. Send that, along with the finalbuilder project and the dproj and .dpr/dpk files from the delphi project to support so we can see if we can reproduce the issue here.
Hi.
As my test package for you works perfectly well, there seems to be a problem with the installation of Finalbuilder on our build computer. The button “Load Settings from Project file” on the Project tab of the “Compile Delphi for Win32” action is permanently disabled on the build computer but on my development system everything works fine. Our large Finalbuilder project works well on my development system, too.
I just reinstalled Finalbuilder 5 on our build computer but the button is still disabled and I can’t compile our projects. I also cleaned the registry and removed anything I could find relating to Finalbuilder or VSoft. Is there some limitation in Finalbuilder 5 for virtual computers? Our build system is runtime as a guest operating system using VMWare Server.
Kind regards
Kay Zumbusch
Hi.
I just found another problem. Finalbuilder 5 seems to get the search path from the wrong project file. I set the “Compile Delphi for Win32” action to read the search path from the project file. I have an.DOF file of the project with an old and incomplete version of the search path. The .DPROJ file has the correct search path. I’m not able to compile the project from Finalbuilder (Error: F1026 File not found: ‘uWwCCDSUpd.dcu’). If I restore the .BDSPROJ file of Delphi 2006 or fix the path in the .DOF file everything works fine. Finalbuilder seems to ignore the .DPROJ file or the file is not parsed correctly.
As newly created Delphi 2007 projects do not have an .DOF file Finalbuilder should always read the .DPROJ file if Delphi 2007 is the selected compiler.
Kind regards
Kay Zumbusch
Two things. First, the general options for Delphi sets which environment variable is loaded - that may have an influence on things. Second, the really annoying thing about D2007 projects is they have this “debug” and “release” modes. I have found that my debug mode is always up to date, but the release version is as I converted the project and is all wrong. Of course I’d like FinalBuilder to be a release version, so my compiles failed. I’ve not worked out the resolution yet, but I suspect I’ll either delete the release version if I can, or always use the release settings. Why I’d want my paths to be different between versions I don’t know.
Yesterday I tried to load the old Finalbuilder 4 projectfiles into the latest FB5 beta. There is 2 projectfiles.
NightlyBuild.fbp5 and Attracs.fbp5. NightlyBuild.fbp5 include the Attracs.fbp5 file and the reason is that Attracs.fbp5 is checked into the source control (StarTeam). It also contains the main logic of the build.
I found 3 problems with the beta (with the reservation for my mistakes…)
1. Project that build fine in D2007 IDE fails in FB5 because missing paths. I have tried both to load paths from projectfile and set them directly in the directories tab. I then tried to start a new project from scratch and copy paste the old actions. This seems to work better.
2. In Delphi Win32 action property, tab Project there is a "Use settings from project file" checkbox to choose what config to build from. The state of this is not saved in the fbp5-file.
3. For the same property look at Action Inspector panel at the left. CompilerVersion says "Delphi 5" and Delphi 2007 is not available here. Delphi 2007 is choosen in the propery dialog.
Regards Roland Bengtsson
Hi there.
Fortunately I got all my problems fixed. The reasons were:
1. problem with relative paths
The first action in our Finalbuilder project run a script to set identical version information and compiler settings in each compile action. This script reset the compiler back to Delphi 2006 and these project files had incomplete search paths.
2. disable button "Load Settings from Project File"
This button is disabled if there is no .DPROJ file available. We didn’t open every project in Delphi 2007. Therefore nearly all .DPROJ files were missing. We opened every project in Delphi and now the button is enabled for every compile action
3. reading settings from .DPROJ file
That was some kind of misinterpretation of the error messages. The .DPROJ file is parsed correctly and the updated settings are correctly stored in the .DPROJ file and the .RES file.
We had another problem because of the empty project config setting. This problem was already mentioned. We fixed that with our initial script and added the necessary command. Now everything works fine.
Thanks a lot for this very fine tool. It really helps a lot.
Kind regards
Kay Zumbusch
Hi Roland
1) I wasn’t able to reproduce this, I would need more info to be able to tell if this is a bug or not.
2) The state of that check box is driven by whether any of the other check boxes under it are checked. If none are then it will not be checked when you re-open the dialog.
3) Thanks, fixed for next build.