FASMLIB is multiplatform library for x86 (32 bit) ASM programmers. It is designed to be easy to and powerful (you often have simple and powerful versions of same function). It's purpose is to get programmer rid of annoying routine coding, and to allow to write multiplatform programs easily in assembler. Also it is designed to catch many bugs in code.

There is version for win32 and linux platforms. It has support for FASM, MASM, NASM and YASM. Support for other platforms and assemblers can be added, just contact me.

Current official release is version 0.8.0.

Official Website
download FASMLIB 0.8.0

version 0.8.0 is out.

By the way, i just finished conversion from ASCII string to floating point number with great precision (same like FASM has). And it is just as slow as FASM's conversion routine too

We should have floating point conversions in FASMLIB 0.9.0

where is coming from the ascii string?
where do you remember the result of the convertion?

fixed memory in application?
stack?
registers?

these questions are just to follow the same way than you.
possibly, i'll use a fasmlib like to be compatible with your fasmlib.

so, function i don't made can be taken in your lib, and function you don't made can be taken from mine.

edfed: just download FASMLIB and check documentation and examples, it's all there. To explain entire FASMLIB calling standard again would take too much time.

please don't mind if I can ask!
i think standard C library does this and much more. why should you bother to write
fasmlib?

 o__=-
 )
(\
 /\  
    

Mostly just for fun

If you want reasoning and blah blah, here: http://en.wikipedia.org/wiki/FASMLIB#Why_not_libc.

LibC is a bit more pain in the ass to use (epecially to use properly) in assembly. And some things are simply fucked up in libc

plz dont mind again!

is fasmlib supposed to be run on both 32 and 64 bits systems?

 o__=-
 )
(\
 /\  
    

No, FASMLIB is 32bit only. But that has nothing to do with mentioned statement.

In theory, type "long" can still be 64bit on 32bit system too. Some libc implementations can not support any 64bit numbers on 32bit system. Etc.

Libc is usable as long as you use only one it's implementation. Problems start if you want portability. Even still, I think that FASMLIB has much nicer interface to use in assembly, than libc

Hello vid! Is it planned to implement additional filesystem operations like to open and read directories and setting file properties? I would like to move on to CGI programming with FASM, and FASMLIB seems perfect for that, since i'm actually programming on WINDOWS, while application should run on LINUX too...

I *did* plan it while i was working on FASMLIB, but now this project is paused at best (or likely, stopped completely). The most i will maybe do one day would be "completing" version 1.0 (support for floating point numbers and support for directory services), but even that is not sure, and surely it won't happen soon.

May i ask why you did stop it? Was it because of lack of time or where there simply other libraries with more functionality?

Because i slowly moved to other project, "serious" one, one that i am pursuing now. I'd like to finish things i listed in previous post, but i won't have time for that so soon.

Well, i see the problems with libc listed in your Wikipedia entry. If i really make the step towards CGI programming with ASM, i will try to expand FASMLIB as good as i can. In this case i will contact you of course, if you still like to maintain FASMLIB.

Hi Vid,


I'm having trouble with fasmlib... specifically linking?


I originally was working with alink to get my generated object files made into an executable... I've tried linking with microsoft's linker as well but I get similar errors.

Here's the assembly file I'm working with (hello.asm):



And here's the process that I'm going through to get the errors I've gotten:

nasm -fcoff "hello.asm" -o test.obj

alink -oPE -subsys console test.obj fasmlib.obj fasmlib2.obj fasmlib2.lib libcmt.lib -o test.exe

ALINK v1.6 (C) Copyright 1998-9 Anthony A.J. Williams.
All Rights Reserved

Loading file test.obj
Loading file fasmlib.obj
Loading file fasmlib2.obj
Loading file fasmlib2.lib
415 symbols
Loaded first linker member
Loading file libcmt.lib
5933 symbols
Loaded first linker member
matched Externs
matched ComDefs
Unresolved external __imp__GetProcessHeap@0
Unresolved external __imp__HeapAlloc@12
Unresolved external __imp__GetLastError@0
Unresolved external __imp__HeapFree@12
Unresolved external __imp__HeapReAlloc@16
Unresolved external __imp__CreateFileA@28
Unresolved external __imp__CloseHandle@4
Unresolved external __imp__ReadFile@20
Unresolved external __imp__WriteFile@20
Unresolved external __imp__SetFilePointer@16
Unresolved external __imp__ExitProcess@4
Unresolved external __imp__GetStdHandle@4
Unresolved external __imp__GetProcessHeap@0
Unresolved external __imp__HeapAlloc@12
Unresolved external __imp__GetLastError@0
Unresolved external __imp__HeapFree@12
Unresolved external __imp__HeapReAlloc@16
Unresolved external __imp__CreateFileA@28
Unresolved external __imp__CloseHandle@4
Unresolved external __imp__ReadFile@20
Unresolved external __imp__WriteFile@20
Unresolved external __imp__SetFilePointer@16
Unresolved external __imp__ExitProcess@4
Unresolved external __imp__GetStdHandle@4


Any help you could give would surely be appreciated, thanks,

Dominick

The errors you get are imports from Kernel32.dll missing. FASMLIB object doesn't build it's own import data. Usually there is "kernel32.lib" which does that for importing KERNEL32.DLL, etc. You should list it in linkers command line arguments, instead of libc (libcmt.lib). Sadly, FASMLIB doesn't get on well with libc (especially on linux), you shouldn't use both at the same time. It was aimed to be alternative, not extra library.

You also shouldn't link all three fasmlib.obj, fasmlib2.obj and fasmlib2.lib, only one of them. Did you the read manual (in doc/ subdir), section "Usage"? The manual gives full example including command line options for MS linker. I never used alink, but it should be analogous to MS link, you just need to get kernel32.lib compatible with it somewhere.

Sorry, I read the manual... but I've been trying to link with the comments suggested in hello.asm (in examples/nasm/portable/hello). I finally got it to work correctly:
nasm -fwin32 hello.asm -o test.obj

link /subsystem:console test.obj fasmlib.lib kernel32.lib
Microsoft (R) Incremental Linker Version 10.00.30319.01
Copyright (C) Microsoft Corporation. All rights reserved.

fasmlib.lib(init.obj) : warning LNK4078: multiple '.data' sections found with different attributes (C05000C0)

It correctly produces test.exe.


I know that fasmlib is public domain... but I've been wondering about link (which is only available with my install of vc) and kernel32.lib (which are only available with my install of the ddk - I believe) - what would I do in a client environment if I wanted to assemble/link a generated assembly file ... could these files be included with a distribution of my program?


Thanks for your patience and time Vid,

Dominick

You are right, I have somehow managed to put libcmt into that one example, no idea what for. Seems it shouldn't be needed.

I am not completely sure about MS link. There is VS Express which is free-as-in-beer, but you have to be agree to its license to use it. Under your circumstances, using different linker than MS link, one that is free-as-in-GNU, seems to be the right solution.

Hi,vid.
I thought the FASMLIB should contains some network interface.
Thanks for you and your FASMLIB.

Thanks for the FASMBLIB