Coping with underscore decoration conventions

[AntiPasta]

A good day to you all,

I had an old code project lying around, written in C + assembly and
targeted for X86 Linux, that I intended to compile on Win32 as well.
I'm using GCC and NASM on Linux (not really sure which version but
nothing too esoteric), and MingW and NASM on Windows. I quickly ran
into the problem of differing calling conventions between Linux and
Windows: my assembly code exports several symbols, but the MingW GCC
won't link to them unless I prepend a _ to the symbol names, whereas
GCC on Linux seems not to care about this. I guess I can add an
underscore to the required variable names, but I intended to retain
code portability - is there a way around this?
Thanks in advance.

 

[Kenny McCormack]

A good day to you all,

I had an old code project lying around, written in C + assembly and
targeted for X86 Linux, that I intended to compile on Win32 as well.
I'm using GCC and NASM on Linux (not really sure which version but
nothing too esoteric), and MingW and NASM on Windows. I quickly ran
into the problem of differing calling conventions between Linux and
Windows: my assembly code exports several symbols, but the MingW GCC
won't link to them unless I prepend a _ to the symbol names, whereas
GCC on Linux seems not to care about this. I guess I can add an
underscore to the required variable names, but I intended to retain
code portability - is there a way around this?
Thanks in advance.

<OT>
The usual method is to define macros that are turned on in the Winders
compiles.
</OT>

 

[AntiPasta]

<OT>
The usual method is to define macros that are turned on in the Winders
compiles.
</OT>

Well, actually, I'd need to define macros in NASM to do this, but that
is probably impossible in this case. I was looking for a way to get
MingW to "forget" the underscores.