OpenTTD ported to SkyOS (native port)
Moderator: OpenTTD Developers
LOL, good point. But considering it's got journalling, memory protection, etc, it should be somewhat stable. I hope . . .Windows looks good, but it doesn't mean that it is good
"If a man does not keep pace with his companions, perhaps it is because he hears a different drummer. Let him step to the music he hears, however measured or far away" --Henry David Thoreau
weird. My email works fine
what's even more weird is the SkyOS port. it have to be made way better to be added to svn. I would like it to fit in the current makefile instead of creating a new one
mapfile should be placed in os/skyos instead of the root
I think it will be nice to support SkyOS, but not at the cost of the readability of the source tree
what's even more weird is the SkyOS port. it have to be made way better to be added to svn. I would like it to fit in the current makefile instead of creating a new one
mapfile should be placed in os/skyos instead of the root
I think it will be nice to support SkyOS, but not at the cost of the readability of the source tree
I think mapfile is dynamically generated
I also think their build system is completely wacky and can't use standard makefiles...
However, as I turned down the chance to do driver development for them (I was actually mailed about it, weird...), I didn't get a copy of the 5.0 betas so I'm not sure
I meant SF bounced me as the attachment was > 1MB
I also think their build system is completely wacky and can't use standard makefiles...
However, as I turned down the chance to do driver development for them (I was actually mailed about it, weird...), I didn't get a copy of the 5.0 betas so I'm not sure
I meant SF bounced me as the attachment was > 1MB
there are no autoconfiguration in OTTD. It's a makefile written by hand and *should* be able to handle SkyOS too if the correct few lines are added
as for SDL/native graphics, that's one of the things that should be included in the makefile
also this conversion is done against a very old version of OTTD
as for SDL/native graphics, that's one of the things that should be included in the makefile
also this conversion is done against a very old version of OTTD
Dump the makefile.sky in os/skyos, and try to check in what you can of the changes maybe? The mapfile is almost certaiinly generated on build, its a symbols reference.
It'd get the code into the SVN and dealt with - I also think that we're not going to get much demand for binaries for SkyOS, as they'll probably provide them built with the OS
It'd get the code into the SVN and dealt with - I also think that we're not going to get much demand for binaries for SkyOS, as they'll probably provide them built with the OS
by symbol's reference you mean:
those symbol references point to entries in Rules.mak which is the make rules for skyOS software.
Code: Select all
OUTPUT_FORMAT = PE
include ../rules.mak
OutputFile = $(dir_system)/myapp.app
OutputFiles = main.o
$(OutputFile) : $(OutputFiles) $(SHARED_GUILIBS)
$(ld) $(LD_FLAGS) $(OutputFiles) $(SHARED_GUILIBS) -o $(OutputFile)
I think I will try to add support for SkyOS, but I need help from somebody, who knows the system/have the system to test on
I need a way to identify if it's SkyOS. Can somebody find a way to do that. I think it can be done with
uname
uname -s
vendor ....
I just needs one of them and the output
One thing is for sure. I will add it so it will not affect other OSes so it can't break anything while trying
I need a way to identify if it's SkyOS. Can somebody find a way to do that. I think it can be done with
uname
uname -s
vendor ....
I just needs one of them and the output
One thing is for sure. I will add it so it will not affect other OSes so it can't break anything while trying
Who is online
Users browsing this forum: No registered users and 41 guests