Right. The whole directory business is the only real deficiency of QDOS based systems, as it was an afterthought implemented with backwards compatibility in mind Also, the maximum path length is severely limited for the same reason.Chain-Q wrote:They're pretty much ANSI C with POSIX. So a sufficiently advanced libc and GCC 2.95.3 should be enough for it. Maybe. The only problem I see maybe is path handling differences, the QL seems to use the "_" character for paths, and I'm not sure if vlink has expectations about which character is the path separator or so.mk79 wrote:In any case, if it ever comes to that point I volunteer to have a look at porting vasm/vlink.
Ah, I see. How is the relocation handled, is that in some startup code that is just linked in?I'm sure Frank Wille, the author of vlink would be open to add a Sinclair QL target if it really comes to that. I'm in regular contact with him, and he's generally very open and helpful, and the QL binary format seems reasonably simple. In fact I already talked with him about this. But for now it wasn't needed. I use a custom linker script with vlink's "rawseg" mode, which combines .text (code) and .data and .bss sections into one using that linker script, then just writes two separate files with the the combined raw .text/.data (while omitting the zeroes for the .bss), and the relocation table for them.
Cheers, Marcel