Agreed, my thought is that hbmk2 in the two versions are using different compiler options, as the only difference is the two different versions of hbmk2 that I used to compile my app. Of course I'm probably looking at this in a somewhat less knowledgable direction. Based on the same hbm script, same Harbour.exe and Libs, same Mingw GCC and Libs, I thought both hbmk2 versions would make the same App EXE in the end. Well I took a look at the source for hbmk2 and Viktor, that is some piece of "artificial intelligence"!
Viktor Szakáts wrote: > > Change of executable size or even change in the > checksum of the generated executable by itself isn't > an indication of a problem. > > hbmk2 is using Harbour libs, which change size all > the time, plus it sometimes happens that C compiler > options used by hbm2 change over time. The final > executable will be created by C linker, which may > have its own side of the story. > > Point is to have a consistently and freshly rebuilt > Harbour, 3rd party and local libs, and app, when > doing tests. > > Viktor > > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour > > -- View this message in context: http://old.nabble.com/Harbour-%22random%22-GPFs-tp28375863p28451558.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
