jejej and we do not needto make that *.lib stuf ..

when we want to use a DLL :)


neither LoadLibrary....




we just do



extern NameFunction
import NameFunction cucu.dll
CALL




:)
Posted on 2004-02-14 12:53:52 by Nguga
nuMIT_or , for ONLY NASM

have you any RC example with this last no reloc

method ?


ha NICE bss is working :)

but i can always use data section :)

buffer resb 100

i make it in data

buffer times 100 db 0



opf resb OPENFILENAME

i make in data

opf times OPENFILENAME db 0
Posted on 2004-02-14 13:00:24 by Nguga
> nuMIT_or , for ONLY NASM
> have you any RC example with this last no reloc
> method ?

Well, I've advised you:
http://groups.yahoo.com/group/win32-nasm-users/files/PEMAC/NPEMAC_v0.0.zip

in the dlg folder

> ha NICE bss is working
> but i can always use data section
> buffer resb 100
>
> i make it in data
> buffer times 100 db 0

But that has not sense if you want a small file, because the
"times" operator will produce a array of zeros, meanwhile
the "resx" operator will reserve memory to use in run time.

> nuMIT_or i can not use the same NAGOA *call* macro becouse > that macro calls functions via IAT
> without any import table jump.
>
> its just a call directly to the function , it does not call the adress
> table .
>
> and nagoa *call* makes this .
>
> push dword 0
> extern ExitProcess
> import ExitProcess kernel32.dll
> CALL

Ah yes, I forgot it. With the new macros you don't need
to link the obj files, and the "extern" and "import"
directives are not necessaries. But you can use the
traditional "call".

You know that I use only one hl macro to invoke imported
functions and I`ve included there some "%IFs" to switch
correctly between the different calls. So your source
codes are portable. You can use the codes that you want
to link with any linker and assemble it using NASM and
the PEMAC.INC includes by only adding a definition via
command line (using the -D NASM switch).
Posted on 2004-02-15 08:51:44 by n u M I T_o r
> for every *call* and us you know BIN nasm option
> does not suport tha

With the BIN nasm option you can do anything, but...
you have to write it all.

In the old versions of PEMAC.INC you can see a lot
of predefined sections. I can use a different section
for resources and for import info. And, when I need it,
I include a section table for the .bss section If I want
share it in a DLL. I have not tested this with the
section directive and I suspect that is not so easy.

By now, the main problem that I find with the new
PEMAC.INC is how include relocation info in the
PE file. This is necessary if you want a kmd or a dll
with shared sections.
Posted on 2004-02-15 09:07:41 by n u M I T_o r