More Build Machine Woes:

-
More Build Machine Woes:

Our build machine, when building with Seattle, is not always putting MAINICON into the EXEs.  I've looked with a resource explorer.  They simply aren't there.  But sometimes the are (We build like 200 different EXEs).  

In each case, the main icon is set in the project options, the DPR has the {$R *.RES} right there, and the RES file is part of the build.

Any thoughts anyone?

Comments

  1. Nick HodgesNovember 12, 2015 at 12:56 PM

    More details:  In some cases, the default "Window" icon is shown.  In one case, and Icon is shown that isn't even in the resources of the EXE!  Very strange.

    ReplyDelete
  2. Nick HodgesNovember 12, 2015 at 1:06 PM

    BTW, the mystery, where-the-heck-did-that-come-from icon is a black 'X', and a number of our EXE's display it in Windows Explorer.

    ReplyDelete
  3. Ron MaupinNovember 12, 2015 at 1:31 PM

    I think Embarcadero embedded special code that detects when you are using it. :)

    ReplyDelete
  4. Nick HodgesNovember 12, 2015 at 1:42 PM

    Well, I think the answer is that these projects in question have never been opened in the new IDE, so the IDE hasn't had a chance to generate the default *.ico file, as it now does.  Those *.ico files aren't checked in to the repository, and thus not getting included.  What a pain -- now I have to open like 50 DPROJ files and compile them just to get the Icon files and check them in.  Grrrr.

    ReplyDelete
  5. Thomas Mueller (dummzeuch)November 12, 2015 at 1:56 PM

    Just be glad that it's only 50 and not all projects.

    ReplyDelete
  6. Nick HodgesNovember 12, 2015 at 2:33 PM

    Good point.  ;-)

    ReplyDelete
  7. Heinz ToskanoNovember 12, 2015 at 7:41 PM

    Seems related with your previous trouble with missing or incorrect manifests. You may invest some time to check that everybody in your team is working with the same configs. You may also need a way to warn you if something unexpected, like a missing .res file happens. Or you will be damned to seek and solve too many ghost in the future.

    ReplyDelete
  8. Jeroen Wiert PluimersNovember 12, 2015 at 10:49 PM

    Always include your own resources. Always clear the icon cache on your local machines when testing.

    ReplyDelete
  9. Lars FosdalNovember 13, 2015 at 1:21 AM

    The black X is probably from TMS. Been there, seen that.

    ReplyDelete
  10. Nick HodgesNovember 13, 2015 at 9:44 AM

    Lars Fosdal​ you are right.

    ReplyDelete
  11. David HeffernanNovember 14, 2015 at 5:11 AM

    This all stems from you letting the IDE manage resources. Take control.

    ReplyDelete
  12. Joseph MitzenNovember 14, 2015 at 9:06 PM

    The Ballad Of Nick Hodges

    Our build machine is not always putting MAINICON into the EXEs.
    Not even when we say "Please".

    I've looked with a resource explorer.  They simply aren't there. 
    They're not under the table. They're not under the chair.

    Sometimes we do find a black "X".
    It has us rather vexed.
    Lars blames TMS.

    It looks like we have to open all the projects in the new IDE.
    But when I say "we", I don't mean with Bruce McGee.
    Just me.

    I shall be up all night fighting this battle...
    you might say I'll be Sleepless in Seattle.

    ReplyDelete

Post a Comment