(Please copy it into an editor because the overview of this big source file is not that good here.) Here's the FASM.ASM (from the FASM DLL package, with some extensions (commented) for FASM version 1.67.27 that were posted by windwakr in that thread) with my specific changes. lib is linked into my application without errors, too, but when I call the Assemble function, the debugger shows me a memory access violation (read error at adress 290465279, which is far away from the memory area allocated for FASM or the mapped executable in memory). Wether FASM nor the linker produced any errors, the. So I converted the FASM Dll and made some little changes (see comments in code), exported it as MS COFF and linked it with a 3rd party linker (i tried the lib.exe from MASM32 package and polib.exe from Pelles C Compiler). But this method seems not to be very nice, firstly it's not very memory friendly (the dll resides in memory 2 times) and there's another better way I think: Creating a Library (.lib) file and then link it static into the executable. data section of the executable and then load it directly from memory. The first method I thought of would be to include the DLL as it is into the. The application should be ONE executable and I don't want to deliver it with the FASM.exe or the FASM.dll I've seen a few posts ago. I'm working on an application which uses FASM as backend.

Purebasic 4.20