Anybody with hands-on experience compiling with FPC for MASM, including the RTL ? The FPC compiler
option is there. The advantageis that ML.EXE can produce both COFF and OMF, so that VCC code can be
statically linked with FPC code, using the Microsoft linker. Or at least in theory
It is
In our previous episode, Adriaan van Os said:
It is rather unfortunate that fpc can only link OMF, not COFF on Windows (I
read on some previous
posts that it is the other way round, but according to
Marco van de Voort wrote:
In our previous episode, Adriaan van Os said:
It is rather unfortunate that fpc can only link OMF, not COFF on Windows (I read on some previous
posts that it is the other way round, but according to
Would it be possible to give some simple example code that could be
tested?
Did you try using the external linker to see if this makes a difference?
-Xe option should work for that.
Regards,
Pierre Muller
-Message d'origine-
De : fpc-devel-boun...@lists.freepascal.org
But if the formats are the same, what is the cause of the error
message Illegal COFF Magic when trying to statically link with FPC a
VCC produced .obj or .lib ?
I found the COFF docs here http://wiki.osdev.org/COFF and here
http://msdn.microsoft.com/en-us/gg463119.aspx
the Visual C++
The is no COFF magic.
the first 2 bytes indicate normally a MACHINE type.
The files I produced start etiher by:
0x8664 indicating a x86 coff header
or
0x014c indicating a i386 coff header.
Nevertheless,
0x is also listed as IMAGE_FILE_MACHINE_UNKNOWN
Could it be that your coff object
07.11.2014 17:01, Pierre Free Pascal пишет:
The is no COFF magic.
the first 2 bytes indicate normally a MACHINE type.
The files I produced start etiher by:
0x8664 indicating a x86 coff header
or
0x014c indicating a i386 coff header.
Nevertheless,
0x is also listed as
Sergei Gorelkin wrote:
Your header looks like a BigObjHeader
Ah, that's interesting, thanks.
This means that the object is prepared to handle relocation that are
not in
the 4-byte
range... A feature that Free Pascal indeed does not support IIRC...
There is probably an option somewhere
Am 07.11.2014 10:35, schrieb Adriaan van Os:
Anybody with hands-on experience compiling with FPC for MASM, including
the RTL ? The FPC compiler option is there.
NASM ist probably supported better and should be able to generate a lot
of different object file types.
Florian Klaempfl wrote:
Am 07.11.2014 10:35, schrieb Adriaan van Os:
Anybody with hands-on experience compiling with FPC for MASM, including
the RTL ? The FPC compiler option is there.
NASM ist probably supported better and should be able to generate a lot
of different object file types.
On Fri, Nov 7, 2014 at 12:55 PM, Adriaan van Os f...@microbizz.nl wrote:
(to my astonishment Xcode even installs nasm).
Just in case, you find this interesting:
http://forum.nasm.us/index.php?PHPSESSID=sl1i7lf3upjgenov75agnkui56topic=1972.msg8738#new
I have been using the safecall functionality in linux and it has been
working. I now am porting the same code to OSX and find that
safecall_exceptions is not turned on. In particular I need the
functionality that catches the HRESULT and passes it back to the calling
function. I see that
12 matches
Mail list logo
