Cross compiler overwrites files with different case on Windows. about fastbasic

[dmsc]

Hi!

About your first question, yes, you need to add a new section to the config file if you want data placed at specific (or aligned) locations; then you can place data in your basic program using:

    DATA font() BYTEFILE [ALIGNFONT] "myfont.fnt"

This will include the contents of the file into the ALIGNFONT segment, note the section name limited by [ and ].

For your second question, can you paste the command line you are using?

Have Fun!

[PJM-NCC-70511]

fb TGAtari\tg_edit.bas TGAtari\xmove.asm

I figured out what was going on, Originally, I had "XMOVE.ASM" and the file name having caps in the filename caused it to be treated as an output file for the compiler. May need to correct this because I had to rewrite my custom assembly code after the compiler overwrote the file.

[dmsc]

Ok, that is actually two bugs - or at least a missed feature and a bug:

• Bug 1: filename extensions are only checked at lowercase, so your ".ASM" file is interpreted as a BASIC source.
• Bug 2: The logic for selecting the output filename does not check for collisions between lower and upper case - so the file "XMOVE.ASM" is set to input and "XMOVE.asm" is set to output. But in Windows those two are the same file, so it get overwritten.

Will try to fix...

[dmsc]

Fixed on repository. You can try with attached compiled version. fastbasic-v4.6-fixed.57-win32.zip