Permission to include Pelles tools with the future Masm SDKs

[Vortex]

Hi Pelle,

To keep alive the legacy of Steve Hutchesson, the maintainer of the MASM32\MASM64 SDKs , I would like your permission to include the following tools and required DLLs with the future releases of the Masm SDKs :

Code: [Select]

poasm.exe
polib.exe
polink.exe
porc.exe

The current versions of your tools coming with the Masm SDKs are old.

Shortened version of the file \masm32\bin\pelle.txt :

Pelle Orinius has given permission to include a number of his high tech
tools in the MASM32 Project.

Pelle's tools are available from his website as a complete programming
package called Pelles C.

http://www.smorgasbordet.com/pellesc/

The tools included in the MASM32 Project are the command line tools
suitable for building assembler projects and/or modules in assembler.
Pelles C contain a complete IDE that includes its own resource editor
and a complete range of tools and accessories for building C and
mixed C and ASM projects.

With current testing the linker produces more efficient PE headers and
generally results in a smaller EXE file.

With the current build style batch files used in MASM32, the main difference
when using PoLink.exe instead of the Microsoft Link.exe is that the
resource file must be appended as a RES file, not an OBJ file converted
by CVTRES.EXE.

Below are the available command line options for PoAsm.exe, PoLink.exe
Porc.exe and PoLib.exe.

[Pelle]

Hello,

To keep alive the legacy of Steve Hutchesson, the maintainer of the MASM32\MASM64 SDKs , I would like your permission to include the following tools and required DLLs with the future releases of the Masm SDKs :

Code: [Select]

poasm.exe
polib.exe
polink.exe
porc.exe

The current versions of your tools coming with the Masm SDKs are old.

Sure, go ahead!

/Pelle

[Vortex]

Hi Pelle,

Many thanks. I will inform the members of the Masm Forum.

[John Z]

Hi Vortex,

I've watched MASM32 for many years.  Downloaded many times but never went very far because of the restrictive license.  While I highly respected Steve I could not agree with restricting use based on an individuals decision to release their own program code under a GPL license. No one is or should be forced to, but if they want/choose to they should be able to.

Do you think this could be reconsidered and possibly be modified by the team?

Code: [Select]

"Exclusion of open source projects and software.
The MASM32 SDK cannot be used to create open source software or any other form of software
under any form of licence that requires the user of the MASM32 SDK to surrender the rights
they are afforded under the MASM32 licence. In particular the MASM32 licence completely
excludes projects licenced under the GNU organisation's published GPL licence and/or variants."
John Z

[TimoVJL]

It was Steven's will, so respect that, so masm32 32-bit stay as he wanted.
Steven had a strange views of world.

[John Z]

Of course, no disrespect intended...just asking
In honor I post a few of my photos   Good thing this is in Chit Chat

John Z

[Vortex]

Hi John,

Sadly, Hutch passed away and we need to respect his decisions. He worked a lot on the Masm32\Masm64 packages. The licensing schemes are complicated and Hutch desired to protect his own work.