Watch, Follow, &
Connect with Us
Public Report
Report From: Delphi-BCB/Linker/ILINK32/Other    [ Add a report in this area ]  
Report #:  1542   Status: Closed
Linker doesn't produce a final image
Project:  C++Builder Build #:  10.157
Version:    6.0 Submitted By:   Andrew Cope
Report Type:  Basic functionality failure Date Reported:  6/17/2002 9:44:14 AM
Severity:    Serious / Highly visible problem Last Updated: 2/24/2005 2:00:07 PM
Platform:    All platforms Internal Tracking #:  
Resolution: Cannot Reproduce (Resolution Comments) Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (4 Total Ratings)
4.75 out of 5
Total Votes: 1
I've attached a self contained project to this report. Under the IDE a build appears to do nothing - at least it doesn't produce the required SRCDRV32_VL.DED

A Make does produce the required file though.

The .MAK file has the same problem.

I recreated the project using the DLL Wizard and it has the same problem.

FWIW the project is a DLL (with the extension DED) that contains German language alternatives to various messages.
Steps to Reproduce:

Andrew Cope at 8/15/2002 3:32:01 AM -
This may be related to the presence of a .RC in the project.

Markku Kinnunen at 8/19/2002 12:57:48 AM -
I upgraded from BCB5 to BCB6 a week ago. Now I have been trying to build my project for one week with BCB6 and EXE file is never generated!! Compiler does not give any error messages, it just stops working but no exe file is generated.

Very annoying problem, Borland!

Martin Rothschink at 10/21/2002 12:43:02 AM -
I upgraded a project from BCB5 to BCB6 SP2 German and have the same problem. A "build all" only compiles all files but doesn't link. If you have enabled "increment build number" this never happens any more.

Anthon Pang at 7/7/2003 11:13:12 PM -
I too have seen this problem in BCB6 Update 4.  Everything compiles, but ilink32 silently exits without producing an .exe (in this case, for the wxWindows "widgets" sample).  (If called within a Makefile, make exits with "error 128".)

I've experimented with various combinations of options: -Gk (to keep any intermediate files), -r (verbose), -v (full debug), -w (all warnings), and -Gn (disable incremental linking).

(CPU: P4, RAM: 512 MB, Disk space: 800 MB free, OS: Win XP)

Anthon Pang at 7/8/2003 12:19:03 AM -
Additional observations:

o  ilink32 silently fails when the wxWindows library is built with additional debug code; the resulting "wx24ds_bcc.lib" is 24.5 MB in size; the largest module bloats to 361K in size

o  ilink32 succeeds in generating the expected target .exe when the wxWindows library is built without the extra debug code; the "wx24s_bcc.lib" is only 7.2 MB in size (and all the modules are under 66K in size)

Since the "widgets" sample links against many of these modules, it would appear that the problem is related to object size.

Server Response from: ETNACODE01