Re: golink with NASM
- From: Frank Kotler <spamtrap@xxxxxxxxxx>
- Date: Wed, 23 Jul 2008 07:23:56 GMT
Nucleo wrote:
GoLink is a clever choice.
Might as well mention where to find it:
http://www.jorgon.freeserve.co.uk/
To manage with DLL, three cases :[snip - Wow!]
1) You choose to declare them in your source,
so use #DYNAMICLINKFILE first.dll, second.dll
2) You choose to declare them in golink command line, place their names in
command line : test.obj first.dll, second.dll
3) You are too lazy to write all the required names in the command line
and use a @list_of_dll.txt
The file text contains the DLL names.
Example below for a huge API collection on Windows -32 :
(Of course you can prefer a 64-bit Windows.
GoLink is also 64-bit compliant.
;;;;;;;;;;;;;; Win32
;;;;;;;;;;;;; Libraries
KERNEL32.DLL
HHCTRL.OCX
Happy to read you !
Likewise! Thanks for the info, Patrick!
[note: there's an assembler, too... I don't want to see any Nasm users being seduced away... :)]
Best,
Frank
.
- References:
- golink with NASM
- From: bwaichu@xxxxxxxxx
- Re: golink with NASM
- From: Nucleo
- golink with NASM
- Prev by Date: Having trouble posting?
- Next by Date: Re: Troubles with LIB files on Dos-mode
- Previous by thread: Re: golink with NASM
- Next by thread: Problem with Function Call with NASM
- Index(es):
Relevant Pages
|