forums.silverfrost.com

silicondale · Posted: Wed Jun 08, 2016 6:34 pm Post subject: SLINK64 problem

I just tried to create a .LIB library in SLINK64 and this is what happens:

File c:\temp\LIB.TXT contains :-
archive C:\VM\OBJECT64\lib\MASTER.lib
addobj C:\VM\OBJECT64\binary\D2013\D_EXIST3.obj
addobj C:\VM\OBJECT64\binary\D2013\D_FCLOSE.obj
addobj C:\VM\OBJECT64\binary\D2013\D_FOPEN2.obj
addobj C:\VM\OBJECT64\binary\D2013\D_GETDDL.obj
... (plus a few more)
file

I run command -
slink64 c:\temp\LIBBLD.txt> c:\VM\OBJECT64\LIB\LIB.TXT

- and LIB.TXT gives
[SLINK64 v1.7, Copyright (c) Silverfrost Ltd. 2015-2016]
***SLINK64 does not know what to do with file c:\temp\LIBBLD.txt

Does SLINK64 not accept command files? Or is it simply not recognising the archive command? The equivalent commands in SLINK work fine and I have been using it in this way for many years.

ljfarrugia · Joined: 06 Jun 2016 Posts: 35

I think the current version of slink64 is quite limited. Apparently it can only build exe files and dll's but not libraries. It also does not understand wild cards, eg. slink64 *.obj does not work, but its fine for the 32-bit linker.

PaulLaidler · Posted: Wed Jun 08, 2016 7:09 pm Post subject:

Yes. SLINK64 currently can't build static libraries.
Details are in the document NotesOn64BitFtn95.txt.

You can create a single .obj file and use it as a static library.
Just use INCLUDE statements to include the source into one file and create a single obj file from it.

silicondale · Posted: Wed Jun 08, 2016 8:59 pm Post subject:

Thanks, Paul - a useful workaround! Hadn't thought of doing that - but since I actually use all the obj files there isn't even a space penalty