I have just screwed together an early version of a project that is fully powered by Pelle's tools. It contain the latest versions of Pelle's normal tools and the current Beta of POASM.EXE. It is a simple Winrar install that MUST be put in the "poasm" directory directly off the root directory of any selected partition. Run it and it will copy the files and build the libraries as well as setting up a desktop icon for the editor.
There are a few working examples and I have pinched some of the masm32 library just to get it up and going. It should be a reasonable vehicle to help Pelle in developing POASM.
http://www.website.masmforum.com/poasm/poasm.zip <<<< UPDATED 4th February 2006
I have added a number of modules from the masm32 library, fixed a problem that Shantanu reported where a C calling convention API was failing. I have added a few C modules I had floating around and put a pair of options on the Project menu to build either STDCALL or C calling convention C modules.
Very nice, I will get a lot of use out of this package.
Thank You :U
Nice work Hutch, the package is installed without any problem on my Win Xp Home Sp2.
Hi, hutch,
I am still struggling with wsprintf.
I have installed the poasm.zip as per your instruction in C:\POASM
I get this error for wsprintf:
POLINK: error: Unresolved external symbol '_wsprintfA'.
Could you please explain what I might be doing wrong. I am quite at my wits ends here !!!
There is the nudef.zip (update to xplibs, I think) sitting in the def folder. Why ?
shantanu,
For the moment, just use the copy of user32.lib from the masm32 project.
LATER : Problem solved. Use the attached version of def2inc.exe and change the prototypes in the USER32.DEF file for both wsprintfA and wsprintfW so that they do NOT have a leading underscore.
LIBRARY user32
EXPORTS
"wsprintfA"
"wsprintfW"
"_ActivateKeyboardLayout@8"
[snip]
Place def2inc in the DEF directory and run makeit.bat AFTER you have modified the user32.def file.
Thanks for reporting this bug, made it easy to fix. :U
[attachment deleted by admin]
Thanks for the new release :U
A.) During lib creation I'm getting:
creating: libc.lib
POLIB: fatal error: Unable to read module-definition file 'libc.def'.
creating: libcntpr.lib
POLIB: fatal error: Unable to read module-definition file 'libcntpr.def'.
creating: libcpsx.lib
POLIB: fatal error: Unable to read module-definition file 'libcpsx.def'.
These DEFs do not exist.
B.) I do not have this package installed, but am using PORC as rc.exe and POLINK as link.exe and things work fine this way. I cannot get "GetFileVersionInfoA" to extern either, like what Shantanu was experiencing. Commenting out the underscore in version.def and rebuilding the libs does not help. "GetFileVersionInfoA" is also defined in minidump.def and miglib.def.
Mark, did you forget to unzip the archive to 'drive:\POASM' named directory ?
Mark,
I have updated the beta testbed, removed the defs and calls to them. There was a problem with C calling convention APIS which I have fixed by changing the tool that creates the include file and removing the leading underscore on their names in the def files. It is still a beta but its getting better as I can learn more about the assembler.
I added the capacity to use Pelle's C compiler as well as this is very useful for testing out C algorithms in assembler.
QuoteMark, did you forget to unzip the archive to 'drive:\POASM' named directory ?
Maybe it was silly, but i had that problem once or twice, till i thought that maybe that is.
I know it's written on the zip package, but i guess i was too tired to see it.
Dont get angry for that dump question, Mark.
Hi, am I forced to use PORC with POASM, are there any dependencies between it and other tools? I still want to use RC, can I ? I decided to code something big to see how good it is (or vice versa).
You can use either, all I do when converting an example from masm to poasm is change RC to PORC.
Hutch,
Very nicely done. Every time I open QEditor, I I find something I like to play with.
Paul
PORC 4.0.0.0 seems to ignore comments (";") in .RC files and read those lines anyway. Is that intentional?
Maybe it works the way rc does: understands C like comments
Quote from: ramguru on February 05, 2006, 05:51:12 PM
Maybe it works the way rc does: understands C like comments
Pelle's resource compiler accepts comments in C style :
100 BITMAP "Mybitmap.bmp" /* This is a comment */