Silverfrost Forums

Welcome to our forums

SLIM vs SLINK

9 Nov 2017 12:08 #20706

What are the differences?

If I am trying to group a number of object files together, then have SLINK search that archive for the relevant modules and include in the executable only those object files, which library manager should I be using?

9 Nov 2017 8:41 #20707

SLIM is much the same as using SLINK with the 'archive' command. In both cases a static library (.LIB) is created. This kind of lib contains the object code and should not be confused with a 'stub' library that is used as a companion to a DLL.

At the moment there is no 64 bit equivalent to either approach. It is unlikely that SLIM will be ported to 64 bits.

9 Nov 2017 11:23 #20716

Why won't there be a 64 bit equivalent to either approach ? Does this mean that my approach of using selective loading from .lib is also an obsolete approach ? Using LE in SLINK64 would certainly much easier that my present approach of doing a 32-bit build then analysing the load map in an excel spreadsheet and listing all referenced files in a pivot table.

Is there a technical reason that 64-bit .lib files aren't being provided.

John

10 Nov 2017 7:43 #20717

John

It's only SLIM that won't be ported and even then it's just my opinion. I expect it will be added to SLINK64.

Please login to reply.