[z88dk-dev] New Release for 2016?

Bridge to the z88dk-developers mailing list
Post Reply
alvin
Well known member
Posts: 1872
Joined: Mon Jul 16, 2007 7:39 pm

[z88dk-dev] New Release for 2016?

Post by alvin »

It's been a year again and I think we should do a release at least once a year.

I've still not got done several things I wanted in there for the next release but the reality is there isn't enough time to do everything as fast as you'd want for a hobby unfortunately.

Is everyone ok for a 1.99B release? Do you have some things you'd like in there before a proposed release?



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
stefano
Well known member
Posts: 2137
Joined: Mon Jul 16, 2007 7:39 pm

Post by stefano »

I'm back on the basck tool, its relevance for a new version is low.
I'd like to fix the file and directory support for cp/m but I don't remember exactly the environment I used to test them, so I'm afraid to try to fix something already working..



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
pscust
Well known member
Posts: 194
Joined: Thu Jun 23, 2011 3:34 pm

Post by pscust »

I agree with a new version now. z80asm is stable and my work on z80asm2 is
progressing slowly.

On Fri, Dec 30, 2016 at 6:14 PM, Stefano Bodrato (
stefano_bodrato@...) <lists@...> wrote:
I'm back on the basck tool, its relevance for a new version is low.
I'd like to fix the file and directory support for cp/m but I don't
remember exactly the environment I used to test them, so I'm afraid to try
to fix something already working..



------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
alvin
Well known member
Posts: 1872
Joined: Mon Jul 16, 2007 7:39 pm

Post by alvin »

dom must still be sleeping it off, haven't heard from him yet :)

I froze the sdcc build at 3.6.5 #9824, windows binaries here:
http://z88dk.cvs.sourceforge.net/viewvc ... ision=1.78

I'll try to see if I can tie up a couple of easy loose ends before I stop committing.

Maybe we can work on a list of changes then?



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
pscust
Well known member
Posts: 194
Joined: Thu Jun 23, 2011 3:34 pm

Post by pscust »

Summary of z80asm changes:

[z80asm] Handle input files more predictably: link .o files; assemble any
other extension; append a .asm or .o option to the file name to allow just
the basename
[z80asm] Make a consolidated object file with -o and not -b: all the object
modules are merged, the module local symbols are renamed <module>_<symbol>
[z80asm] Link the library modules in the command line sequence (it was
depth-first)
[z80asm] Add directory of assembled file to the end the include path to
allow includes relative to source location
[z80asm] Remove all generated files at start fo assembly to remove files
from previous runs
[z80asm] Remove deprecated directives: XREF and LIB (replaced by EXTERN),
XDEF and XLIB (replaced by PUBLIC), OZ (keep CALL_OZ)
[z80asm] Rename DEFL to DEFQ to reserve DEFL for macro variables; rename
DS.L by DS.Q
[z80asm] Constants for section sizes: prune empty sections, rename ASMHEAD,
ASMTAIL and ASMSIZE to __head, __tail and __size respectively, rename
ASM<HEAD|TAIL|SIZE>_<section_name> to __<section_name>_<head|tail|size>
[z80asm] Environment variables no longer used: Z80_OZFILES, Z80_STDLIB
[z80asm] Command line option -r, --origin: accept origin in decimal or
hexadecimal with '0x' or '$' prefix
[z80asm] Command line options: -i, -x: require a library name
[z80asm] Command line options: remove -RCMX000, keep only --RCMX000
[z80asm] Command line options: remove -plus, keep only --ti83plus
[z80asm] Command line options: remove -IXIY and --swap-ix-iy, keep --IXIY
[z80asm] Command line options: remove --sdcc, -nm, --no-map, -ng,
--no-globaldef, -ns, --no-symtable, -nv, --no-verbose, -nl, --no-list, -nb,
--no-make-bin, -nd, --no-date-stamp, -a, --make-updated-bin, -e, --asm-ext,
-M, --obj-ext, -t
[z80asm] Make symbol files, map files and reloc files optional; do not
merge symbols in the list file; do not paginate and cross-reference symbols
in list file; rename list file to file.lis (@file.lst is used as project
list)
[z80asm] Unify format used in map files, symbol files and global define
files, output list of symbols only once
[z80asm] Include symbols computed at link time in the global define file
[z80asm] Simplify output of --verbose


On Sun, Jan 1, 2017 at 6:05 PM, alvin (alvin_albrecht@...) <
lists@...> wrote:
dom must still be sleeping it off, haven't heard from him yet :)

I froze the sdcc build at 3.6.5 #9824, windows binaries here:
http://z88dk.cvs.sourceforge.net/viewvc ... dk/libsrc/
_DEVELOPMENT/sdcc_z88dk_patch.zip?revision=1.78

I'll try to see if I can tie up a couple of easy loose ends before I stop
committing.

Maybe we can work on a list of changes then?



------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
User avatar
dom
Well known member
Posts: 2072
Joined: Sun Jul 15, 2007 10:01 pm

Post by dom »

Give me about 20 years and I might have slept it off! :)

Anyhow, I've got nothing outstanding apart from rebuilding the mac sdcc
of course.

Let's also take this opportunity after the release to migrate across to
GitHub as we discussed earlier last year.



On Sun, 1 Jan 2017, at 06:05 PM, alvin (alvin_albrecht@...)
wrote:
dom must still be sleeping it off, haven't heard from him yet :)

I froze the sdcc build at 3.6.5 #9824, windows binaries here:
http://z88dk.cvs.sourceforge.net/viewvc ... ision=1.78

I'll try to see if I can tie up a couple of easy loose ends before I stop
committing.

Maybe we can work on a list of changes then?



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
stefano
Well known member
Posts: 2137
Joined: Mon Jul 16, 2007 7:39 pm

Post by stefano »

>Maybe we can work on a list of changes then?


New features, right ?
I'll gladly help, it is always nice listing the achievements, they are usually lots of news when grouped together!



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
alvin
Well known member
Posts: 1872
Joined: Mon Jul 16, 2007 7:39 pm

Post by alvin »

========================
ZCC - Compiler Front End
========================

* M4 has been added as an optional macro pre-processor. Any filename ending with extension ".m4" will automatically be passed through M4 and its output written to the original source directory with the ".m4" extension stripped prior to further processing. The intention is to allow source files like "foo.c.m4", "foo.asm.m4", "foo.h.m4" and so on to be processed by M4 and then that result to be processed further according to the remaining file extension.

* In conjunction with the above, a collection of useful M4 macros has been started in "z88dk.m4" that can be included in any ".m4" file processed by zcc. Currently macros implementing for-loops and foreach-loops are defined.

* List files ending with extension ".lst" can be used to specify a list of source files for the current compile, one filename per line. The list file is specified on the compile line with prefix @ as in "@foo.lst". List files can contain any source files of any type understood by zcc and individual lines can be commented out with a leading semicolon. Paths of files listed in list files can be made relative to the list file itself (default) or relative to the directory where zcc was invoked (--listcwd). List files can list other list files, identified with leading '@'.

* zcc now processes all files it is given to the final output file type specified. For example, with "-E" specified, all listed .c files will be run through the C pre-processor individually and all output copied to the output directory. Previous to this, only the first file listed was processed unless a binary was being built.

* -v gives more information on what steps zcc takes to process each source file.

* -x now builds a library out of the source files listed.

* -c by itself will generate individual object files for each input source file. However, if -c is coupled with an output filename as in "-o name", a single consolidate object file will now be built instead of individual ones. The intention is to provide a means to generate identical code in separate compiles to a binary by allowing this single object file to be specified on different compile lines.

* Better error reporting for source files with unrecognized types.

* Better parsing for compile line pragmas; pragma integer parameters can now be in decimal, hexadecimal or octal.

* -pragma-include added to allow a list of compile time pragmas to be read from a file as in "-pragma-include:zpragma.inc". This way projects can consolidate pragmas in one location; this is especially important for the new c library which uses pragmas extensively to customize the crt.

* -pragma-export added as an analog to -pragma-redirect that allows a symbol to be defined equal to a label rather than a value. With -pragma-export, the symbol is made public so that it is visible across all source files.

* --list will generate ".lis" files for each source file in a compile to a binary. The ".lis" file is the assembly listing of source prior to input to the assembler.

* --c-code-in-asm causes C code to be interspersed as comments in any generated assembly listing associated with C source files.

* ".s" files are now understood by zcc to be asz80-syntax assembly language source files. asz80 is the assembler used by sdcc and by adding this to zcc, sdcc project files written in assembly language can be assembled by z88dk. asz80 mnemonics are non-standard so zcc attempts to translate to standard zilog mnemonics before assembling. This is a work-in-progress feature. You can see the translation to standard zilog form by using "-a" on a compile line.

* --no-crt allows compiles to proceed without using the library's supplied crt for a target. The first file listed on a compile line will stand in as the crt and will be responsible for initialization and setting up the memory map.

* Temporary files are always created in the temp directory. The option "-notemp" has been removed.

* Library and include search paths have been fixed to honour the order specified on the compile line. This allows the user to override library functions when desired.

* Source files are now processed from their original location so that includes can be properly resolved. Previously this was only done for .c files but this now applies to other file types.

* clang/llvm compilation is in an experimental state.

Known issues:

* Spaces in paths or filenames can be a problem.

* When --c-code-in-asm is active, unicode characters from .c source files appearing as comments may cause the tools to crash.



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
alvin
Well known member
Posts: 1872
Joined: Mon Jul 16, 2007 7:39 pm

Post by alvin »

========================================
ZSDCC - Customization of SDCC C Compiler
========================================

* Updated to SDCC 3.6.5 #9824.

* SDCC's native C pre-processor is now used so that line numbers corresponding to reported errors are accurate.

* Peephole-z80 fixed to accurately report registers affected by instructions, allowing accurate application of peephole rules.

* inSequence('stride' %1 %2 %3 ...) added as peephole rule qualifier to allow testing whether consecutive bytes in memory are being accessed.

* Peephole-z80 made aware of z88dk special functions which represent code inlined by the library.

* Approximately 300 new peephole rules added to the aggressive peephole set (-SO3).

* Peephole rules added to fix some known code generation bugs and to fix SDCC's critical sections for nmos processors.

* --opt-code-size now significantly reduces code size for programs using 32-bit longs, 64-bit longlongs and floats.

* chars have been made unsigned by default. Use --fsigned-char to change to signed.

* For loops can now declare variables in the initializer statement.

* An rodata section has been properly implemented so that all constant data generated by sdcc is assigned there.



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
stefano
Well known member
Posts: 2137
Joined: Mon Jul 16, 2007 7:39 pm

Post by stefano »

New target: Microbee, support for various GFX modes and 1 bit sound
Same for Robotron kc, z1013 and z9001 families, also in cp/m
CP/M PLUS on SPECTRUM, send and graphics.
CP/M extensions improved on Aussie Byte, trs80, Epson PX
GFX library: improved the vector rendering functions, now bigger pictures can be drawn and higher resolutions are supported. Various fixes.
Custom text configuration (font, resolution) at compile time for all those targets with ansi VT support on graphics display.
Appmake improvements, headerless spectrum, cp/m extensions forced to uppercase..
Interrupt driver music player?



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
User avatar
dom
Well known member
Posts: 2072
Joined: Sun Jul 15, 2007 10:01 pm

Post by dom »

I rebuilt sdcc last week and so both Mac and Windows kits should have the right version of sdcc in them.

In terms of what I was up to:

* [classic] SDCC can now be used to compile using the classic library
* [classic] Rewritten and modular printf core, added (v)snprintf
* [classic] Rewritten and modular scarf core
* [classic] Ports are now section aware
* [classic] Support for compressed data section model
* [classic] Support for copied data section model
* [classic] User overridable fputc_cons
* [sccz80] Correct floating point constant handling
* [sccz80] New __SAVEFRAME__ function decorator to allow saving of ix during a function call
* [sccz80] -standard-escape-chars to make \n and \r output standard character codes
* [zpragma] New tool to extract pragma definitions for both sccz80 and ddcc



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
alvin
Well known member
Posts: 1872
Joined: Mon Jul 16, 2007 7:39 pm

Post by alvin »

The proposed list of changes ditty is below. I'm sure there is stuff missing there - let me know if things should be added or changed.

I'll put together some release packages after tomorrow night's build.




==========================
Z88DK - v1.99B 10 Jan 2016
==========================

Z88dk is a development kit for z80 computers that contains the tools and assembly language libraries necessary to develop code in either C or assembly language for z80-based machines.

Over 50 different z80 machines have CRTs in the toolkit, allowing C programs to be compiled for them out-of-the-box.

There are two C compilers supported (sccz80 and sdcc), two independent C libraries included (the classic and new), an assembler/linker/librarian (z80asm), and a data compression tool (zx7).

This is the second transition release in anticipation of v2.0.

Install Instructions:
https://www.z88dk.org/wiki/doku.php?id= ... stallation

Home Page:
https://www.z88dk.org/forum/

Forum:
https://www.z88dk.org/forum/forums.php

Introduction to Compiling Using the Classic C Library:
https://www.z88dk.org/wiki/doku.php

Introduction to Compiling Using the New C Library:
https://www.z88dk.org/wiki/doku.php?id=temp:front

Compiling for Generic z80 Embedded Systems Using the New C Library:
(The information here is detailed and applies to compilation using the new c library generally)
https://www.z88dk.org/wiki/doku.php?id= ... t_embedded


--8<-- list of changes below -----------------------


=======
PACKAGE
=======

* The win32 and osx packages now include the zsdcc & zsdcpp binaries. zsdcc is z88dk's customization of the sdcc compiler. Other users can compile zsdcc from source.

* A VS2015 solution file is now available in z88dk/win32 for building all z88dk binaries except zsdcc & zsdcpp. Instructions for building zsdcc & zsdcpp can be found in the installation instructions link above.


========================
ZCC - Compiler Front End
========================

* M4 has been added as an optional macro pre-processor. Any filename ending with extension ".m4" will automatically be passed through M4 and its output written to the original source directory with the ".m4" extension stripped prior to further processing. The intention is to allow source files like "foo.c.m4", "foo.asm.m4", "foo.h.m4" and so on to be processed by M4 and then that result to be processed further according to the remaining file extension.

* In conjunction with the above, a collection of useful M4 macros has been started in "z88dk.m4" that can be included in any ".m4" file processed by zcc. Currently macros implementing for-loops and foreach-loops are defined.

* List files ending with extension ".lst" can be used to specify a list of source files for the current compile, one filename per line. The list file is specified on the compile line with prefix @ as in "@foo.lst". List files can contain any source files of any type understood by zcc and individual lines can be commented out with a leading semicolon. Paths of files listed in list files can be made relative to the list file itself (default) or relative to the directory where zcc was invoked (--listcwd). List files can list other list files, identified with leading '@'.

* zcc now processes all files it is given to the final output file type specified. For example, with "-E" specified, all listed .c files will be run through the C pre-processor individually and all output copied to the output directory. Previous to this, only the first file listed was processed unless a binary was being built.

* -v gives more information on what steps zcc takes to process each source file.

* -x now builds a library out of the source files listed.

* -c by itself will generate individual object files for each input source file. However, if -c is coupled with an output filename as in "-o name", a single consolidate object file will now be built instead of individual ones. The intention is to provide a means to generate identical code in separate compiles to a binary by allowing this single object file to be specified on different compile lines.

* Better error reporting for source files with unrecognized types.

* Better parsing for compile line pragmas; pragma integer parameters can now be in decimal, hexadecimal or octal.

* -pragma-include added to allow a list of compile time pragmas to be read from a file as in "-pragma-include:zpragma.inc". This way projects can consolidate pragmas in one location; this is especially important for the new c library which uses pragmas extensively to customize the crt.

* -pragma-export added, is similar to -pragma-define but the assembly label defined as a constant on the compile line is made public so that its value is visible across all source files.

* --list will generate ".lis" files for each source file in a compile to a binary. The ".lis" file is an assembly listing of source prior to input to the linker.

* --c-code-in-asm causes C code to be interspersed as comments in any generated assembly listing associated with C source files.

* ".s" files are now understood by zcc to be asz80-syntax assembly language source files. asz80 is the assembler used by sdcc and by adding this to zcc, sdcc project files written in assembly language can be assembled by z88dk. asz80 mnemonics are non-standard so zcc attempts to translate to standard zilog mnemonics before assembling. This is a work-in-progress feature. You can see the translation to standard zilog form by using "-a" on a compile line.

* --no-crt allows compiles to proceed without using the library's supplied crt for a target. The first file listed on a compile line will stand in as the crt and will be responsible for initialization and setting up the memory map.

* Temporary files are always created in the temp directory. The option "-notemp" has been removed.

* Library and include search paths have been fixed to honour the order specified on the compile line. This allows the user to override library functions when desired.

* Source files are now processed from their original location so that includes can be properly resolved. Previously this was only done for .c files but this now applies to other file types.

* clang/llvm compilation is in an experimental state.

Known issues:

* Spaces in paths or filenames can be a problem.

* When --c-code-in-asm is active, unicode characters from .c source files appearing as comments in translated asm may cause the tools to crash.


==========================
SCCZ80 - Native C Compiler
==========================

* Correct floating point constant handling.

* New __SAVEFRAME__ function decorator to allow saving of ix during a function call.

* -standard-escape-chars to make \n and \r output standard character codes


========================================
ZSDCC - Customization of SDCC C Compiler
========================================

* Updated to SDCC 3.6.5 #9824.

* SDCC's native C pre-processor is now used so that line numbers corresponding to reported errors are accurate.

* Peephole-z80 fixed to accurately report registers affected by instructions, allowing accurate application of peephole rules.

* inSequence('stride' %1 %2 %3 ...) added as peephole rule qualifier to allow testing whether consecutive bytes in memory are being accessed.

* Peephole-z80 made aware of z88dk special functions which represent code inlined by the library.

* Approximately 300 new peephole rules added to the aggressive peephole set (-SO3).

* Peephole rules added to fix some known code generation bugs and to fix SDCC's critical sections for nmos processors.

* --opt-code-size now significantly reduces code size for programs using 32-bit longs, 64-bit longlongs and floats.

* chars have been made unsigned by default. Use --fsigned-char to change to signed.

* For loops can now declare variables in the initializer statement.

* An rodata section has been properly implemented so that all constant data generated by sdcc is assigned there.


=====================================
Z80ASM - Assembler, Linker, Librarian
=====================================

* Handle input files more predictably: link .o files; assemble any other extension; append a .asm or .o option to the file name to allow just the basename.

* Make a consolidated object file with -o and not -b: all the object modules are merged, the module local symbols are renamed <module>_<symbol>

* Link the library modules in the command line sequence (it was depth-first).

* Add directory of assembled file to the end the include path to allow includes relative to source location.

* Remove all generated files at start of assembly to remove files from previous runs.

* Remove deprecated directives: XREF and LIB (replaced by EXTERN), XDEF and XLIB (replaced by PUBLIC), OZ (keep CALL_OZ).

* Rename DEFL to DEFQ to reserve DEFL for macro variables; rename DS.L by DS.Q

* Constants for section sizes: prune empty sections, rename ASMHEAD, ASMTAIL and ASMSIZE to __head, __tail and __size respectively, rename ASM<HEAD|TAIL|SIZE>_<section_name> to __<section_name>_<head|tail|size>

* Environment variables no longer used: Z80_OZFILES, Z80_STDLIB

* Command line option -r, --origin: accept origin in decimal or hexadecimal with '0x' or '$' prefix

* Command line options: -i, -x: require a library name

* Command line options: remove -RCMX000, keep only --RCMX000

* Command line options: remove -plus, keep only --ti83plus

* Command line options: remove -IXIY and --swap-ix-iy, keep --IXIY

* Command line options: remove --sdcc, -nm, --no-map, -ng, --no-globaldef, -ns, --no-symtable, -nv, --no-verbose, -nl, --no-list, -nb, --no-make-bin, -nd, --no-date-stamp, -a, --make-updated-bin, -e, --asm-ext, -M, --obj-ext, -t

* Make symbol files, map files and reloc files optional; do not merge symbols in the list file; do not paginate and cross-reference symbols in list file; rename list file to file.lis (@file.lst is used as project list)

* Unify format used in map files, symbol files and global define files, output list of symbols only once.

* Include symbols computed at link time in the global define file.

* Simplify output of --verbose


===========================================================
APPMAKE - Processes Output Binaries to Target Suitable Form
===========================================================

* +rom can now generate binaries for ROM chips mapped into a specific address range.

* +sms now generates bankswitched .sms files as output.

* +zx now has option to generate headerless .tap files.

* Appmake now understands three compile models -- ram (destined for ram, no stored data section), rom (destined for rom, stored data section is a copy) and compressed rom (destined from rom, stored data section is compressed) -- and will form output files accordingly.


=================
CLASSIC C LIBRARY
=================

* SDCC can now be used to compile using the classic library.

* Rewritten and modular printf core, added (v)snprintf.

* Rewritten and modular scanf core.

* Ports are now section aware.

* Support for compressed data section model.

* Support for copied data section model.

* User overridable fputc_cons.

* New target: Microbee. Support for various GFX modes and 1 bit sound.

* New target: Robotron kc. Support for various GFX modes and 1 bit sound.

* New target: z1013. Support for various GFX modes and 1 bit sound.

* New target: z9001. Support for various GFX modes and 1 bit sound.

* CP/M Plus on Spectrum.

* CP/M extenstions forced to upper case.

* CP/M extensions improved on Aussie Byte, trs-80 and Epson PX.

* GFX Library: improved the vector rendering functions, now bigger pictures can be drawn and higher resolutions are supported. Various fixes.

* Custom text configuration (font, resolution) can be done at compile time for targets with ansi VT support on graphics display.


=============
NEW C LIBRARY
=============

* 64-bit integers are now fully supported in the library.

* The fprintf/fscanf cores can now have conversion specifiers individually enabled or disabled at compile time. This allows the printf/scanf cores to be customized such that they will be the minimum size needed by the program.

* fprintf %aefg precision formatting corrected.

* Intrinsics have been introduced as a method to inline assembly code without disturbing optimization. This provides a means to insert assembly labels (whose addresses will appear in map files), simple assembly instructions such as "di" and "ei", and atomic loads/stores into C code without affecting the compiler's optimizer. See https://www.z88dk.org/wiki/doku.php?id=libnew:intrinsic

* The library has had a preserves_registers attribute attached to every function which informs sdcc which registers will not be affected by a library call and allows sdcc to generate better code around library calls.

* aplib added as another data decompression utility.

* setjmp/longjmp state increased to include the value of IY for sdcc compiles. This was necessary as sdcc sometimes requires the value of IY to be preserved at points in the program.

* New target: rc2014 (preliminary). This target is still being developed by rc2014 users.

* New target: Sega Master System. The target is able to automatically create bankswitched rom cartridges with signatures.

* The CRT startup code has been made much more flexible, allowing a wide range of features to be selected via pragmas at compile time. See https://www.z88dk.org/wiki/doku.php?id= ... figuration



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
alvin
Well known member
Posts: 1872
Joined: Mon Jul 16, 2007 7:39 pm

Post by alvin »

Three packages for 1.99B:

z88dk-osx-1.99B.zip
https://drive.google.com/file/d/0B6XhJJ ... sp=sharing

z88dk-win32-1.99B.zip
https://drive.google.com/file/d/0B6XhJJ ... sp=sharing

z88dk-src-1.99B.zip
https://drive.google.com/file/d/0B6XhJJ ... sp=sharing


Give them a try and see if everything is ok.

If all is good, maybe post at sf after the next build? We tried a candidate release last time but the bug reports didn't begin until after the upload to sf anyway.



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
berk
Member
Posts: 37
Joined: Wed Dec 24, 2014 9:46 am

Post by berk »

Hello,

I have tested couple of my projects for ZX Spectrum and ZX81 and all works well for me. I have tested win32 build.

Thank you for your effort!



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
alvin
Well known member
Posts: 1872
Joined: Mon Jul 16, 2007 7:39 pm

Post by alvin »

Hello,

I have tested couple of my projects for ZX Spectrum and ZX81 and all works well for me. I have tested win32 build.

Thank you for your effort!
Thank you for testing Berk. I have also done some testing on linux and win64.

I can't be home tonight so I've just uploaded to sourceforge a few hours early. If any problems are found we can update those downloads like we did last year.

That's 1.99B in the bag.. if we are moving to git soon, maybe start with that package? There are a lot of dead files in cvs that I had to spend time removing for this release.



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
stefano
Well known member
Posts: 2137
Joined: Mon Jul 16, 2007 7:39 pm

Post by stefano »

>That's 1.99B in the bag.. if we are moving to git soon, maybe start with that package? There are a lot of dead files >in cvs that I had to spend time removing for this release.

Thank you for having taken charge of sporting out and releasing, z88dk is still ..unique :)


I have no objection on using this snapshot as a base for git, phrase ignore my lass commit: I can recover it later



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
stefano
Well known member
Posts: 2137
Joined: Mon Jul 16, 2007 7:39 pm

Post by stefano »

..and please (not phrase) forgive my tablet's spell checker !



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
User avatar
dom
Well known member
Posts: 2072
Joined: Sun Jul 15, 2007 10:01 pm

Post by dom »

That's 1.99B in the bag.. if we are moving to git soon, maybe start with that package? There are a lot of dead files in cvs that I had to spend time removing for this release.
Well done and thank you Alvin.

The plan for git is to import CVS, fix up the errors and then make the code tree match the release by deleting the dead files. That way we keep all the history - seems a bit of a shame to throw away 16 odd years of history.

I've got the import running at the moment so I hope to push this weekend.



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
alvin
Well known member
Posts: 1872
Joined: Mon Jul 16, 2007 7:39 pm

Post by alvin »

Ok, import, trim, label sounds good.

I would like to propose rearranging the source code structure as well in future and I think moving things loses history but you can always go back before the move to find it.



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
User avatar
dom
Well known member
Posts: 2072
Joined: Sun Jul 15, 2007 10:01 pm

Post by dom »

Ok, import, trim, label sounds good.

I would like to propose rearranging the source code structure as well in future and I think moving things loses history but you can always go back before the move to find it.
I've now imported and pushed and mostly trimmed so the repo is now here: https://github.com/z88dk/z88dk unless it's totally wrong I'm not planning on doing another import from CVS.

Moving things can retain the history - just use a git gui to make it easy.

I still need to update the build to point to the repo. Hopefully I'll do that at some point this weekend.



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
pscust
Well known member
Posts: 194
Joined: Thu Jun 23, 2011 3:34 pm

Post by pscust »

Thanks! I've been looking forward to the change to git.
What's the policy we'll follow? Stable versions on the main branch with labels for releases and topic branches while developing and testing?
Regards,Paulo

-------- Mensagem original --------De: "dom (dom@...)" <lists@...> Data: 13/01/17 23:13 (GMT+00:00) Para: z88dk-developers@... Assunto: Re: [z88dk-dev] New Release for 2016?
Ok, import, trim, label sounds good.

I would like to propose rearranging the source code structure as well in future and I think moving things loses history but you can always go back before the move to find it.
I've now imported and pushed and mostly trimmed so the repo is now here: https://github.com/z88dk/z88dk unless it's totally wrong I'm not planning on doing another import from CVS.

Moving things can retain the history - just use a git gui to make it easy.

I still need to update the build to point to the repo. Hopefully I'll do that at some point this weekend.



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
User avatar
dom
Well known member
Posts: 2072
Joined: Sun Jul 15, 2007 10:01 pm

Post by dom »

Thanks! I've been looking forward to the change to git.
What's the policy we'll follow? Stable versions on the main branch with labels for releases and topic branches while developing and testing?
I have too - I think I've become too dependent on a sequential history with other source control systems. That's a sensible workflow, we can always tweak with regard to release branches later on.

nightly releases files now include the short git revision in the filename so I think the migration should now be complete.



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
pscust
Well known member
Posts: 194
Joined: Thu Jun 23, 2011 3:34 pm

Post by pscust »

I assume we are now using git issues for problem tracking. I've submitted a
first issue that seems to be caused by the C preprocessor.

https://github.com/z88dk/z88dk/issues/1

On Sat, Jan 14, 2017 at 10:36 AM, dom (dom@...) <
lists@...> wrote:
Thanks! I've been looking forward to the change to git.
What's the policy we'll follow? Stable versions on the main branch with
labels for releases and topic branches while developing and testing?
I have too - I think I've become too dependent on a sequential history
with other source control systems. That's a sensible workflow, we can
always tweak with regard to release branches later on.

nightly releases files now include the short git revision in the filename
so I think the migration should now be complete.



------------------------------------------------------------
------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
Post Reply