-
Hey Embarcadero!  Please tell me that version info works right in the next update/release!?  Being able to set attributes for all build types is really a great feature.  HAVING TO set them for all build types (separately) really makes me want to stomp on kittens.  Proper inheritance should work here...

Comments

  1. Jim McKeethMarch 15, 2015 at 6:20 PM

    Did you submit a bug with an example? I'm happy to escalate the bug and test it for you.

    ReplyDelete
  2. David HeffernanMarch 16, 2015 at 2:40 AM

    It's better to automate this yourself as part of your own build process.

    ReplyDelete
  3. Lübbe OnkenMarch 16, 2015 at 4:26 AM

    I gave up on version info in Delphi projects years ago. As David Heffernan says, it works better when you handle it with your own build process. The only "disadvantage" is, that IDE builds don't have the correct version info, but who releases these anyway? ;)
    I even had some scripting in place that injected the correct version info back into the dproj files, but disabled this, since it is not necessary.

    ReplyDelete
  4. David HeffernanMarch 16, 2015 at 4:29 AM

    Lübbe Onken It's possible to get IDE builds to have the correct version info too. I manage that with my build process. My build process is based on pre-build actions which I implement with Python scripts. Somewhat ad-hoc, but we are developers after all. Writing tools is what we do.

    ReplyDelete
  5. Nathan WildMarch 16, 2015 at 5:12 AM

    Jim McKeeth Thanks very much. Apparently this has been an issue for all XE versions. I will try to get it submitted today! Perhaps it is only an issue because no-one else has submitted it...

    ReplyDelete
  6. Nathan WildMarch 16, 2015 at 5:15 AM

    Lübbe Onken odd question. What are you doing differently in non-ide builds that makes them more release-worthy than ide builds? Maybe i an misinterpreting something, but doesn't the ide use the same compiler anyway?

    ReplyDelete
  7. Lübbe OnkenMarch 16, 2015 at 5:47 AM

    Nathan Wild yes it uses the same compiler, but we're using a central include file in our build system where we set the major version numbers plus compiler defines and other stuff for a lot of projects from the same product family.

    This way I have to change only one file for a new release and don't have to touch any of the dozens of .dproj files. We have removed the release configurations from the .dproj files altogether. Only different debug settings are there.

    ReplyDelete
  8. Nathan WildMarch 16, 2015 at 8:38 AM

    Jim McKeeth Looks like this has been submitted and discussed at length.  Odder still, it was marked as completed in QualityCentral.

    http://qc.embarcadero.com/wc/qcmain.aspx?d=99275

    ReplyDelete
  9. Nathan WildNovember 6, 2015 at 12:36 PM

    This is still a problem in XE8 and still drives me nuts...

    ReplyDelete
  10. David HeffernanNovember 6, 2015 at 1:07 PM

    +Nathan why don't you script a solution. It's very simple to do.

    ReplyDelete
  11. Nathan WildNovember 7, 2015 at 5:19 AM

    Indeed, or they could fix the problem that has been reported and documented since XE4 or so... ;)

    ReplyDelete
  12. David HeffernanNovember 7, 2015 at 5:45 AM

    Programmers are happy to write their own tooling to support their work.

    ReplyDelete

Post a Comment