Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: Linker behavior clang 32-bit



Permlink Replies: 0
Dean Clark

Posts: 50
Registered: 6/12/08
Linker behavior clang 32-bit
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 30, 2018 8:46 AM
Migrating (trying to) from classic compiler to Clang, 10.2.3.

The linker that comes with Clang doesn't seem to be as "smart" as the original one. For example, we have a project group made up of static libs, BPLs and DLLs, and an exe. Typically if a DLL uses something that's in one of the libs, we add the lib to the DLL project. The Clang linker seems to insist that everything in the lib is resolved, whether or not it's ever used. For example, it's complaining about many unresolved references in a form that is part of a lib, even though that form is never instantiated anywhere in the project group.

Is there an alternative linker? Will we have to move most things out of the libs?

Thanks.
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02