MASM32 Project Builders

[PBrennick]

Hi everbody.
I, originally, coded these to projects using the GeneSys SDK. When I posted them, I mistakenly said that if you wanted to use these files to build MASM32 type projects all you had to do is change all occurrences of GeneSys to MASM32. Rainstorm tested this and reported to me that it did not work. After I examined it, I found that it was because of the library functions I am using.

For that reason, I did the conversion myself and I am including the complete sources here along with the executables.

The two projects are as follows:
MBuildW.exe is used to build a WINDOWS Project.
MBuildC.exe is used to build a CONSOLE Project.

I hope you enjoy them as much as I do. I have done extensive testing of them and so has JDoe and Vortex.

The programs require that the user have only one .asm file in the project folder. If there is more than one file, the additional files should be put into a subfolder such as ASM, for example. The same goes for .RC files. This is already done by most by putting additional .RC files in a subfolder called RES.

The programs will detect if there is no resource file at all and acts accordingly by not trying to link one.

The way it works is the MBuildW program will search for the existing .ASM file and will use that name to build the .OBJ file. It will, also, use that name in the link command. The program will do a separate search for the .RC file because it might be named RSRC.RC and will use that filename to create the .RES file. If a resource file is found, it will be linked. MBuildC works in the same manner.

I am using ML.EXE, RC.EXE and LINK.EXE for the moment as they are very stable. Other tools may be just as stable but they are aftermarket tools.

Enjoy,
Paul


[attachment deleted by admin]

[Vortex]

Thanks for these new tools, nice work :U

[Rainstorm]

thanks!..   :U

Rainstorm

[PBrennick]

No problem, guys.

I included the sources so people could see how to add that capability to their own projects. Makes it more fun.  :U

Paul