Rasm Z80 assembler v1.3 [update 2020.11.24]

[reidrac]

Thus, make clean deletes .asm files and they are excluded from source code history.
Currently I use .rasm for assembly source to be compiled by RASM, vs .s for assembly source to be compiled by sdasz80.

Use .z80 for example (I prefer it because I can set specific syntax highlighting for Z80).

[cpcitor]

Well, in perfect world maybe. But in real life Makefiles never work out of the box and you always have to dig inside, and to moan because it is over-complicated for nothing. 

Don't blame friends that help you

You're conflating. Variety of build environments is not Make's fault.

Complaining like this is like blaming a friend that helps you because they don't have a solution for every problem of your life.

Different build systems for different kind of programs.

Programs with tons of dependencies on modern features often use different, higher level tools, because in those cases, pure makefile-based workflow cannot simply express the needs. Perhaps you have suffered some program where author wrote a big makefile in a situation where it was not the simplest solution.

Simple program, simple makefile.

rasm is simple to build, it uses basic file APIs along with standard input and output. It's typically a program perfectly suited for a simple makefile.

A simple makefile is where people are looking first.

When getting source code, people look at file names for hints.
Makefile is a traditional entry point.

A simple makefile is machine-executable documentation.

Programs need it too. IDE, packaging infrastructures, automated quality assurance tools like travis need machine-readable instructions. A two-line Makefile eases integration and avoids bugs due to different contexts using different build options.

No makefile feels like the author is too lazy, doesn't know how to write a two-line makefile.

Simple and convenient solution that always works

For the user, typing make is shorter than other options.

Even make -f Makefile.other is only a few more keystrokes using Tab key.

Such directory layout is very clear, shows that author is seasoned about portability, with default Makefile for gcc-compatible build environment and took care of making things easy for users of a number of platforms:

Code: [Select]

Makefile
Makefile.win-msvs
Makefile.dos-watcom
Makefile.morphos-gcc
Makefile.macos
source.c

In the case of RASM it *will* work out-of-the-box.

[pelrun]

I wasn't going to push the point quite that hard. In fact I forked RASM so I could write the Makefile myself but I was beaten to the punch. Cheers!

[reidrac]

Is not the end of the world, really.

I also write my own Makefile for rasm, for example for the rasm version I used in Kitsune's Curse:

Code: [Select]

all: rasm

rasm: rasm_v0119.c
gcc -s -O2 $< -o $@ -lm -lrt -march=native

clean:
rm -f rasm

.PHONY: all clean

I use GNU Make, but you can make it generic enough.

[cpcitor]

Is not the end of the world, really.

I also write my own Makefile for rasm, for example for the rasm version I used in Kitsune's Curse:

You makefile is nice and complete with usual patterns.

I went straight to the point when integrating RASM in cpc-dev-tool-chain: after automatically fetching and unpacking rasm source, cpc-dev-tool-chain build system copies a strictly two lines makefile into the source directory and calls it.

[roudoudou]

release v1.1 
https://github.com/EdouardBERGE/rasm/releases/tag/v1.1

[roudoudou]

https://github.com/EdouardBERGE/rasm/releases/tag/v1.2
release v1.2

• nightly bugfix
• bugfix memory leaks and error management with includes in embedded rasm
• bugfix INCLZ4 directive
• many new autotests for include and crunch
• RUN directive do not force PPI configuration to #C0 if there is no second argument
• produce zero size file when there is no breakpoint
• new command line option -amper in order to use ampersand for hex values
• new directive BREAKPOINT_Z80 to produce #ED,#FF opcode
• new directives beginings GETTICK, DURATION (only a few instructions supported)
• new ROM mode to automatically save multiple numbered ROM files
• ability to split 16 bits registers in macro declaration (example: hl.low or {register}.high )

documentation will be updated later

[roudoudou]

new release v1.3
https://github.com/EdouardBERGE/rasm/releases/tag/v1.3

• extended cartridge support
• new directive LZSA1, LZSA2 for crunched code sections
• new directives INCLZSA1 and INCLZSA2 for binary import and LZSA crunching
• new directives XORMEM and SUMMEM to generate checksum of a memory area
• new directive TIMESTAMP to output date/time
• new TAPE option for SAVE directive
• new DMA import options with INCBIN directive (new checks & warnings)
• new enhanced instructions LD IX/IY,BC/DE & LD BC/DE,IX/IY
• new tag {SLOT} for extended cartridge management
• new suffix .HIGH and .LOW to split 16bits register in macro definition
• new option -msep to specify separator for labels inside modules
• new option -amper to use ampersand for hex values
• directive BRK now generates #ED,#FF opcode
• bugfix byte order for Microsoft real format
• bugfix DSK header with nightly build
• bugfix 16bits PCM wav import
• do not warn for missing file with INCLUDE in disabled condition
• do not export struct definition with symbols
• many warnings removed, cleanup, some draft for future functionalities

[GUNHED]

Great job done!


Hint to new users: You find the documentation inside the source code.

[roudoudou]

Hint to new users: You find the documentation inside the source code.

always get the latest PDF on master branch because documentation is never up to date when i'm doing a release !

[GUNHED]

Writing documentation suxx. (I know that from own projects). But nevertheless we all need it. Thanks for this, it's made in an "easy to be understood" way. 

[roudoudou]

Writing documentation suxx. (I know that from own projects). But nevertheless we all need it. Thanks for this, it's made in an "easy to be understood" way. 

anyway i'm always ok to answer any question by mail 

[roudoudou]

FR/EN documentation updated - thanks Siko!
download on github

https://github.com/EdouardBERGE/rasm/blob/master/documentation_EN.pdf
https://github.com/EdouardBERGE/rasm/blob/master/documentation_FR.pdf

[GOB]

Ouf ^^