... "3C" using MSVC and "Microsoft Resource Compiler" Sorry, never used "Microsoft Resource Compiler", I don't like the bloated, limited and bugged MS tools. You have to find what is the syntax it requires for base64 embeded resources. Probably it doesn't support them. ...
Antonio, did you mean by "FWH libs replace Harbour errorsys", that the FWH owned errorsys is linked automatically and the size of the .exe can be explained by this? yes Then why this sample is still 3195904 in size? FUNCTION MAIN() RETURN NILFUNCTION ERRORSYS() RETUR...
gkuhnert wrote:Antonio, did you mean by "FWH libs replace Harbour errorsys", that the FWH owned errorsys is linked automatically and the size of the .exe can be explained by this?
I wanted to share my observations. First, on WIndows, I use msvc and msvc64 exclusively. Never BCC. If I compile the sample program as is I wind up with a 650 KB executable. If I add #include "fivewin.ch" to the top of the sample, but still with no calls at all to FWH code, and no other ch...
Can you paste a map file piece ? Perhap, the trick is searchs map some file symbol in rtl of xHarbour and if founded then they are. You work es very usefull for found if fwh overwrite some basis rtl functions. I have a no explicable problem with harbour+ fwh... only if fwh is linking, http://forums....
Building exe is task of linker. If exe no decrease on remove lib is a linker problem. The linker is forced to link a module if a symbol of that module is referenced in the program. In my sample, no FWH symbols are referenced. This is demonstrated by the fact that the linker doesn't complain if I re...
Allright, but note what increase problem is no a fwh problem or harbour problem: it's a C linker problem No, it isn't. If I remove or add an unused lib from the list, the EXE size doesn't change. EMG No, it isn't ?? :shock: Building exe is task of linker. If exe no decrease on remove lib is a linke...