View previous topic :: View next topic |
Author |
Message |
wahorger
Joined: 13 Oct 2014 Posts: 1217 Location: Morrison, CO, USA
|
Posted: Thu Nov 09, 2017 1:08 am Post subject: SLIM vs SLINK |
|
|
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? |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7924 Location: Salford, UK
|
Posted: Thu Nov 09, 2017 9:41 am Post subject: |
|
|
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. |
|
Back to top |
|
|
JohnCampbell
Joined: 16 Feb 2006 Posts: 2554 Location: Sydney
|
Posted: Fri Nov 10, 2017 12:23 am Post subject: |
|
|
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 |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7924 Location: Salford, UK
|
Posted: Fri Nov 10, 2017 8:43 am Post subject: |
|
|
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. |
|
Back to top |
|
|
|