FiveTech Support Forums

This is NOT a FWH problem but I hope the expertise here can help me find a solution.

I have 3 build scenarios:
+ xBuildw ( xHarbour.com ... current version )
+ UE Studio: builds with FWH, Harbour, MSVC++ 2013 libraries
+ Microsoft Visual Studio 2013
I use one set of source files ( .prg ). I get 3 different executables.

Recently my first build tool ceased to work.

xBuildw will build the .ppo, .c, and .obj files, but xLink is unable to write the resulting .exe. What is strange is that an older build set still works, but not a "newer" project.

I even tried a very simple Hello World type file.

The error is: xLINK: fatal error: Internal error: write_executable_image.

I have ample RAM ( nearly 7 GB avail ), plenty of drive space, and have no history of virus issues. Windows Defender says the system is clean. Other tools report no problems. The computer is less than a year old, and I am VERY cautious with what is downloaded.

So ... I'm looking for ideas before I go crazy ! Any thoughts would be greatly appreciated. Otherwise send cookies to our local mental hospital ... I'll turn myself in.

Tim

Tim,

I repeat my suggestions: try to ask xHarbour.com. It will not hurt.

EMG

Enrico,

I DID ASK on the xHarbour forum ... twice ... but no one knew the answer.

I found the problem ... now I have to figure out how to solve it.

When moving to the Visual Studio build with Harbour, I brought my .rc file into conformity with current standards. Apparently the Pelles RC compiler is having problems with it, and it is the RC file that is causing the problem. I now need to find instructions for the RC compiler to see what I may need to change.

Tim

Tim,

I just sent an email to Pelle Orinius (PellesC developer) with cc to you

OK ... so I ultimately used the process of elimination, and some thoughts from others, to resolve this thing.

I was working with background images for the main window. I had them as .bmps and two of them in the file totaled 32 MB. Yeah, crazy, but we old timer's don't always make sense !

I excluded them ( which is no loss ... I was planning to create a link to external images the user can change anyway ) and now everything is "MOSTLY" happiness.

So the linker just couldn't handle the size of the .RC with the big .bmp files ... but Visual Studio had no problem with it. Also, those two bitmaps inflated the size of the Windows .exe to 41MB, and without them we are back to the normal 9 MB.

Grrrrrr ................................ But really, thanks to all who contributed thoughts. I'm now back to 3 build options.

Tim