🚀 go-pugleaf

No, I don't use that in the assembly module. The assembly module is extremly
simple:
.386
.model flat
PUBLIC _externproc
DATASEG
;one or two things here just to define something.
ENDS DATA
CODE
mov eax, 05Ah; just to have something happen
ENDS CODE
END

patterned after a previous post on this group. I created this file by
choosing File->New->Assembly then adding it to the project. Although I can
assemble it with the command-line assembler and add the object file to the
Builder project, it doesn't make any difference whether the asm file or obj
file is part of the project.

Borland's documentation advises to use the same .model in the assembly
module as the C++ program, but nowhere in Builder does it give any
indication of what the model is. Nor can I find anything that says anything
about what the COW32.obj file might be or do.

Any help is much appreciated since I'm going nuts.

D

"Bob Gonder" <notbg@notmindspring.invalid> wrote in message
news:ahiie31op322c33qt9t70a4jfu67mto5ih@4ax.com...
> Daniel wrote:
>
> >But I get an error about "symbol __PublicInfoTable defined in both
> >filename.obj and ...Borland\Lib\COW32.obj"
>
> Does your Asm module contain or use that name?
> define it external in your asm.
> extrn __PublicInfoTable:dword ;or whatever
>
>