Different compilers for compiling TOS ?

[stephen_usher]

And *for the umpteenth time*, stop using LLMs to try to solve your problems! Of course it's not running TTP files. What nonsense. That's the Atari version.

Indeed, Artificial Idiots will only give a reasonable answer if they've had a lot of correct training data, and little wrong training data, to regurgitate. For Atari systems they've probably been trained on the forums and you know how well that's going to go don't you?

[Icky]

I don't like installing software suites after software suites, packages after packages on my daily driver machine (which is a Macbook) so I just have a virtual machine which I unpause when necessary.

It does my ISE dev, my 68k cross compiling dev, my CPLD flashing and if I completely screw it up: oh well, never mind. Let's spin up a new one.

It's Debian, but could as easily be one of the hand-holdy distros too.

BW

I do exactly the same @Badwolf makes things a lot easier and copying between host and VM makes getting files etc easy.

[exxos]

Start with the git version. Apply your changes.

GIT wont work.. already said a few posts back.

Anyway, I just tried downloading the zip instead (https://github.com/th-otto/tos3x/archiv ... master.zip) and, apart from cd to a different directory name, it just made first time again.

I did what you did, didnt work. Again said a few posts back.

You haven't shown us what's in your tos3x directory, BTW.

Exactly as downloaded from the master.zip from git.

Oh, it's just occurred to me perhaps cygwin has two types of make. Try running 'gmake' instead?

Command not found.

[exxos]

It might be helpful to know that the cygwin drives are also just Windows directories - you can use nano (or vim or anything else) from the cygwin shell, or you can edit the code on the disk in Windows using any editor or IDE.

Yeah the folders are all fine..

Capture.PNG (8.74 KiB) Viewed 120 times

But there are some hazards - Windows CRLF line endings sometimes can creep in from your editor/IDE and its easy to get mixed up with / posix directory separators and \ Windows separators. Cygwin will tolerate both but the programs you are running there might not. Also permissions might be an issue in some cases where they matter since Windows file operations can change them under cygwin's feet. Usually this isn't an issue for compiling source projects though.

True, that's caught me out before. But I only downloaded the GIT files as @Badwolf did and MAKE should work.. but it doesn't... Zero output, no files are created.

This is why I don't do "new stuff" as its always trouble

But like I said a few posts back, if the compiler isn't going to do anything "magical" anyway, then it's probably just not worth the hassle.

[dml]

I'm a bit late to this party and didn't read all the posts \o/ but I did download the zip and look at the Makefile...

It comes with a bin/ directory full of old 68k compiler tools for Win, Mac, Linux and ....TOS.

It's currently pointing at the TOS tools. i.e.

Code: Select all

BIN=$(top_srcdir)\bin\tos${BS}

When it will probably need to be

Code: Select all

BIN=$(top_srcdir)\bin\win32${BS}

...otherwise it will be trying to run TTPs from windows. But I think this was noted earlier.

...also Cygwin is a posix Linux-ish environment not native Windows so the TOS '\' directory separators in the paths look like they could cause problems. I bet path issues are why make just returns silently. They likely all need fixed.

Anyway the makefile as it is can't work from Linux and probably not from Cygwin either. It is set up to build under TOS with GEMDOS formatted paths. Should be fixable assuming the tools all work. ....or it could be a rabbithole best done from scratch

[dml]

...and looks like the second makefile GNUmakefile *is* set up for a posix build environment so you might get further with that. But I think you are missing that version of make, so it would need to be installed from the package manager...

[exxos]

...
Anyway the makefile as it is can't work from Linux and probably not from Cygwin either. It is set up to build under TOS with GEMDOS formatted paths. Should be fixable assuming the tools all work. ....or it could be a rabbithole best done from scratch

Isn't that what @Badwolf tried though here in Linux ?
viewtopic.php?p=135837#p135837

[exxos]

...and looks like the second makefile GNUmakefile *is* set up for a posix build environment so you might get further with that. But I think you are missing that version of make, so it would need to be installed from the package manager...

GNUmakefile.cmn does mention Linux..

But no idea what version of make I need

Capture.PNG (228.74 KiB) Viewed 98 times

[dml]

I changed the first few lines of the Makefile to be more friendly with Linux/Mac/Cygwin:

Code: Select all

# nasty workaround to avoid backslash at end-of-line
BS=/${empty}
QBS=/${empty}

BIN=$(top_srcdir)/bin/macos/
LIB=$(top_srcdir)/lib/
INC=$(top_srcdir)/common/
EXEEXT=
BUILD_EXEEXT=$(EXEEXT)

...and it is at least trying to build now with MacOS tools (fix the macos/ tool path fragment to win32/). Those binaries are not auth'd to run on a Mac of course without fixing them from the ZIP but shouldn't be an issue on Cygwin. I might look more tomorrow but need to drop it for tonight.

[exxos]

I changed the first few lines of the Makefile to be more friendly with Linux/Mac/Cygwin:

Thanks.. I'll have a go when I get home from work tomorrow. Need an early night