Announcing NASMX v1.0rc1

[Rob Neff]

The NASMX v1.0rc1 release candidate is now available for download.

You can now choose the appropriate download for your distribution:

• Linux - http://sourceforge.net/projects/nasmx/files/nasmx-1.0/linux/
• Windows - http://sourceforge.net/projects/nasmx/files/nasmx-1.0/windows/

The main difference between the two packages is that the Windows version includes pre-built tool-chain executables as well as a compiled nasm help file while the Linux package does not.

Linux 32-bit support is official once again.  Linux 64-bit support will come eventually.
Additional Linux demos have been added with more to come.
Many thanks to Bryant for allowing me to modify his examples for this release!

Please download your platform's package and give it whirl.
The macro framework is stable with some non-GUI examples being able to easily cross-compile.
Enjoy! 

[Bryant Keller]

I took a glance over the Linux edition and I had a suggestion. If you are going to be using Makefile's anyway, why not set the include path there? Have the user define an environment variable NASMX_DIR then use -I$(NASMX_DIR)/inc in your ASFLAGS.

Code: (makefile) [Select]

##### Makefile #####
NAME=example
AS=nasm
ASFLAGS=-f elf32 -I$(NASMX_DIR)/inc
LD=gcc
LDFLAGS =-Wall -s
LIBS =-lc

# [ Suffixes ]
# Change the suffixes to match your system environment
O           = .o
ASM         = .asm
INC         = .inc
LST         = .lst

OBJS = $(NAME)$(O)

all: $(NAME)

demo2: $(OBJS)
$(LD) $(LDFLAGS) -o $(NAME) $(OBJS) $(LIBS)

$(NAME)$(O): $(NAME)$(ASM)
$(AS) $(ASFLAGS) $(NAME)$(ASM) -o $(NAME)$(O)

clean:
rm *$(O) ./demo2

##### End Makefile #####

That way, the code doesn't have to use relative includes, it can use:

Code: [Select]

%include "nasmx.inc"
%include "linux/libc.inc"
You might need to provide a setpath.sh in the base directory of the NASMX package, but that wouldn't really be much different than the old setpath.bat in Windows

[Rob Neff]

Do you think it also makes sense at this point to add in:

./configure
make
make install

as is normally done with other packages even though technically we're only interested in installing the include files?

[Bryant Keller]

Not really. I only suggested the makefile change because I never have liked the practice of using ../ to specify the include files, it just looks a little lazy. When setpath was first added to the project, I thought about doing the same thing for linux (setup.bat & setup.sh) to where it also configures NASMENV to contain the include settings for NASMX (ie running export NASMENV=-I$(cwd)/include/ while in the NASMX base directory for linux).