flat assembler
Message board for the users of flat assembler.
Index
> Main > fasm packaging as a project for the community Goto page Previous 1, 2, 3, 4, 5 Next |
Author |
|
Tyler 09 Jun 2010, 00:56
Wow, that's an epic fail if I've ever seen one. I screwed up building the package data directory("data.tar.gz") it contains the same directory structure as the standard root, and all the files in it are merged into the existing data structure. "usr" was supposed to be the root dir of data.tar.gz, but the "data" folder became that by accident. I did test it, it's just that I forgot I'd already put fasm in my /usr/bin the manual way. Sorry for the screw up, and thanks for trying my package.
It's fixed now. I deleted the manually installed fasm from my /usr/bin, installed my package, tested with "$ fasm" and it worked. 100% positive. Should I append a package version number to 1.69.14? Making this 1.69.14.2. I'm going to delete the old ones to save space. For the little documentation I installed, look in "/usr/share/doc/fasm". Question: In your opinion, should I include documentation, or does it just take up space? Anyone know about making man pages?
|
|||||||||||||||||||||
09 Jun 2010, 00:56 |
|
Coty 09 Jun 2010, 02:10
@tyler, linux mint 9 i386... works perfectly Thanks, this is nice. and may help many people.
|
|||
09 Jun 2010, 02:10 |
|
goldenspider 25 Sep 2011, 06:03
Here is the GdiPlus APIs, translated from GdiPlus SDK.
It took me half a day, hope useful to you. INCLUDE: API\gdiplus.inc EQUATES\gdiplus.inc PCOUNT\gdiplus.inc ;================ struc GUID def { match d1=,d2=,d3=,d4, def \{ .Data1 dd d1 .Data2 dw d2 .Data3 dw d3 .Data4 db d4 \} } ;You can define GUID: ImageFormatPNG GUID <0xb96b3caf,0x0728,0x11d3,0x9d,0x7b,0x00,0x00,0xf8,0x1e,0xf3,0x2e>
|
|||||||||||
25 Sep 2011, 06:03 |
|
Akujin 23 Oct 2011, 06:31
Usage:
Drag and Drop a masm32 include file over the M2F.exe if the program dont crash! you obtain a fasm compatible include file in c:\ a message box will confirm the successful operation. Only prototype extracted, EQU and Structs ignored! Dont use EXTIA include type! Dont try windows.inc! UPDATED!
_________________ CLI HLT Last edited by Akujin on 29 Oct 2011, 06:48; edited 1 time in total |
|||||||||||
23 Oct 2011, 06:31 |
|
Akujin 24 Oct 2011, 04:50
315 Flat Includes...
only Kernel32.inc tested! opengl32 complain about glBeginA NFI!... Regards. [Deleted v0.000000000000000000000001] [New v1.01 on new post] _________________ CLI HLT Last edited by Akujin on 26 Oct 2011, 18:53; edited 1 time in total |
|||
24 Oct 2011, 04:50 |
|
Madis731 24 Oct 2011, 09:14
Is your version numbering binary and/or logarithmic? What's your incrementation policy?
|
|||
24 Oct 2011, 09:14 |
|
Akujin 26 Oct 2011, 19:44
315 Flat includes! No API errors this time! PCOUNT on separate files EQUATES and STRUCTS ready but that's another story!...(NOT included!) Madis731 Just used a CYA with a RZG version number feel free to mail me if you dont get it! Notes Kernel32 and others appears twice: kernel32.inc and kernl32p.inc include ending with 'p' are most up to date. Manual editing is still required for some includes. New M2Fx Tools included in a sub folder. Regards.
_________________ CLI HLT |
|||||||||||
26 Oct 2011, 19:44 |
|
LocoDelAssembly 01 Feb 2012, 01:54
FYI, madmatt provided a new update recently: http://board.flatassembler.net/topic.php?t=13931
|
|||
01 Feb 2012, 01:54 |
|
shadowomf 28 Mar 2012, 08:15
Hello,
I'm not sure if this is the right place to post this. I have made a few headers on my own for a planned cross-platform game. The game will propably not happen, but maybe someone else needs the includes. There are headers for: freeglut - which supports that you keep control of your event loop (unlike the original GLUT) OpenAL Soft - an updated open source version of OpenAL SI (sample implementation) physicsfs - which handles cross platform I/O and archive access (pak, zip, 7z, ...) and provides helpers to get the application and user path on all platforms (e.g. PHYSFS_setSaneConfig) OpenGL - I generated these from more current specs, most of the time you propably would want to use the defaults shipped with fasm Each library has it's own folder, which contains at most the following three files: equ.inc - defines and structs api.inc - imports ptr.inc - can be used to store the pointers for extension functions (OpenGL, OpenAL), you still have to get them yourself Note, I don't ship the binaries, but there are relativly easy to build (at least with visaul studio and cmake). I choose the libraries because they all allow dynamic linking without publishing your source code. The includes have not been thoroughly tested. They will propably only work on Windows in 64bit applications, but I haven't tested it. Most of them were created by a python script and some notepad++ regex magic. If I find the time I will make a clean script that I can publish. If you can give me any feedback (especially on how to create headers that can be used on linux, unix, bsd or whatever) I would try to add this to the script. One more thing, is there any way to prevent polluting the global "namespace" when you use libraries? My current approach to this is adding <libraryname>§ before all functions, structs and equates, but it isn't pretty. Example kernel32§CreateThread. Note the attached includes are clean and don't contain this "feature". -Christoph
|
|||||||||||
28 Mar 2012, 08:15 |
|
Goto page Previous 1, 2, 3, 4, 5 Next < Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.