Hello !

Hello !

In a compilation script, I need to set a version number (major-minor-revision)  to a set of executable .
Have I any other solution than doing myself a program that opens Dproj files and  put the version number inside it ?

Comments

  1. You can disable the .dproj version and add your own version resource in an .rc file?

    ReplyDelete
  2. OW nice idea ....  I'm not very up-to-date with resource files , I'll google about that ;

    Ty Lars Fosdal

    ReplyDelete
  3. If you use FinalBuilder there is an option to override the .dproj version info with your own.

    ReplyDelete
  4. +1 for FinalBuilder.

    Best tool for Delphi, version number management & build automatization. FB is also able to write back the overridden version info into the .dproj file.

    ReplyDelete
  5. FinalBuilder is for me just like Vi : I'd like to use it, but I don't have the time to put in it to understand how it works  ....

    ReplyDelete
  6. We use an external version resource for each single executable. These external version resource files have an include for another central version resource that includes the current version number and global version information for the whole project. The same resource file will also be used for setting the version numbers in our setup builder.

    For compatibility with older Delphi versions we define in each project a pre-built event like "brcc32 $(PROJECTDIR)\ver.rc".

    ReplyDelete
  7. Olivier SCHWAB I had the same, but within one hour I was able to set up a build script that checks out from SVN and compiles.

    After spending some more time I included updating the version number, create an installer with Inno and move the binaries to a new folder. Well worth the investment in time! I think a better ROI then spending time on learning Vi :-)

    ReplyDelete
  8. Looks really temptating , Birger, what you describe is EXACTLY what I do with batch files atm .... I'll try to find a couple of hour to go in FinalBuilder...

    ReplyDelete
  9. +1 more for Finalbuilder. Thinking about what it was like before we started using it is like looking back at a much darker age :)

    ReplyDelete
  10. At work, once the code is checked in after QA, it gets automatically compiled and deployed to their host computers. This happens several times a day. I can't imagine doing this without FinalBuilder. In fact, the only reason we can service our internal customers as quickly as we can is because of FinalBuilder. It was definitely worth the money and time spent to learn using the tool. Just do it!

    ReplyDelete
  11. OK, guys, I spent a part of the week end to dive into FinalBuilder, and you were right, this tools defininitely worth the time you spend to learn it . Many thanks to you all !

    ReplyDelete

Post a Comment