Wiki feedback

If you have any questions on programming, this is the place to ask them, whether you're a newbie or an experienced programmer. Discussion on programming in general is also welcome. We will help you with programming homework, but we will not do your work for you! Any porting requests must be made in Developmental Ideas.
User avatar
bogglez
Moderator
Moderator
Posts: 575
Joined: Sun Apr 20, 2014 9:45 am

Re: Wiki feedback

Post by bogglez » Sat Jun 10, 2017 9:20 am

Added the guide "Romdisk Swapping" in the "General" section: http://dcemulation.org/?title=Romdisk_Swapping
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
AtariOwl
DCEmu Freak
DCEmu Freak
Posts: 91
Joined: Fri May 23, 2008 5:57 am

Re: Wiki feedback

Post by AtariOwl » Wed May 16, 2018 5:08 am

Hi

Trying to install it all again after my HD crash.

Ran through the script, but the kos make is not happening

Code: Select all

jve MINGW32 /opt/toolchains/dc/kos
$ make
for i in utils kernel addons ; do make -C $i || exit -1; done
make[1]: Entering directory '/opt/toolchains/dc/kos/utils'
for i in genromfs wav2adpcm vqenc scramble dcbumpgen; do make -C $i; done
make[2]: Entering directory '/opt/toolchains/dc/kos/utils/genromfs'
cc -O2 -Wall    -c -o genromfs.o genromfs.c
genromfs.c:83:10: fatal error: netinet/in.h: No such file or directory
 #include <netinet/in.h> /* Consts & structs defined by the internet system */
          ^~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [<builtin>: genromfs.o] Error 1
make[2]: Leaving directory '/opt/toolchains/dc/kos/utils/genromfs'
make[2]: Entering directory '/opt/toolchains/dc/kos/utils/wav2adpcm'
cc -O2 -Wall     wav2adpcm.c   -o wav2adpcm
make[2]: Leaving directory '/opt/toolchains/dc/kos/utils/wav2adpcm'
make[2]: Entering directory '/opt/toolchains/dc/kos/utils/vqenc'
cc -O2 -Wall -DINLINE=inline -I/usr/local/include    -c -o vqenc.o vqenc.c
vqenc.c: In function 'create_downscaled_map':
vqenc.c:575:44: warning: format '%lx' expects argument of type 'long unsigned int', but argument 3 has type 'unsigned int' [-Wformat=]
         printf("create_downscaled_map(%d %lx)\n", res, (uintptr_t)oneup);
                                          ~~^           ~~~~~~~~~~~~~~~~
                                          %x
vqenc.c:575:44: warning: format '%lx' expects argument of type 'long unsigned int', but argument 3 has type 'unsigned int' [-Wformat=]
         printf("create_downscaled_map(%d %lx)\n", res, (uintptr_t)oneup);
                                          ~~^           ~~~~~~~~~~~~~~~~
                                          %x
cc -O2 -Wall -DINLINE=inline -I/usr/local/include    -c -o get_image.o get_image.c
cc -O2 -Wall -DINLINE=inline -I/usr/local/include    -c -o get_image_jpg.o get_image_jpg.c
cc -O2 -Wall -DINLINE=inline -I/usr/local/include    -c -o get_image_png.o get_image_png.c
cc -O2 -Wall -DINLINE=inline -I/usr/local/include    -c -o readpng.o readpng.c
cc -o vqenc vqenc.o get_image.o get_image_jpg.o get_image_png.o readpng.o -lpng -ljpeg -lz -lm -L/usr/local/lib
make[2]: Leaving directory '/opt/toolchains/dc/kos/utils/vqenc'
make[2]: Entering directory '/opt/toolchains/dc/kos/utils/scramble'
cc -o scramble scramble.c
make[2]: Leaving directory '/opt/toolchains/dc/kos/utils/scramble'
make[2]: Entering directory '/opt/toolchains/dc/kos/utils/dcbumpgen'
cc -O2 -Wall -DINLINE=inline -I/usr/local/include   -c -o dcbumpgen.o dcbumpgen.c
cc -O2 -Wall -DINLINE=inline -I/usr/local/include   -c -o get_image.o get_image.c
cc -O2 -Wall -DINLINE=inline -I/usr/local/include   -c -o get_image_jpg.o get_image_jpg.c
cc -O2 -Wall -DINLINE=inline -I/usr/local/include   -c -o get_image_png.o get_image_png.c
cc -O2 -Wall -DINLINE=inline -I/usr/local/include   -c -o readpng.o readpng.c
cc -o dcbumpgen dcbumpgen.o get_image.o get_image_jpg.o get_image_png.o readpng.o -s -lpng -ljpeg -lm -lz -L/usr/local/lib
make[2]: Leaving directory '/opt/toolchains/dc/kos/utils/dcbumpgen'
make[1]: Leaving directory '/opt/toolchains/dc/kos/utils'
make[1]: Entering directory '/opt/toolchains/dc/kos/kernel'
Makefile:28: warning: overriding recipe for target 'clean'
/opt/toolchains/dc/kos/Makefile.prefab:19: warning: ignoring old recipe for target 'clean'
make -C  arch
make[2]: Entering directory '/opt/toolchains/dc/kos/kernel/arch'
make -C dreamcast
make[3]: Entering directory '/opt/toolchains/dc/kos/kernel/arch/dreamcast'
make -C  fs
make[4]: Entering directory '/opt/toolchains/dc/kos/kernel/arch/dreamcast/fs'
kos-cc  -c fs_iso9660.c -o fs_iso9660.o
/opt/toolchains/dc/kos/utils/gnu_wrappers/kos-cc: line 50: /opt/toolchains/dc/sh-elf/bin/sh-elf-gcc: No such file or directory
make[4]: *** [/opt/toolchains/dc/kos/Makefile.rules:13: fs_iso9660.o] Error 127
make[4]: Leaving directory '/opt/toolchains/dc/kos/kernel/arch/dreamcast/fs'
make[3]: *** [/opt/toolchains/dc/kos/Makefile.rules:45: _dir_fs] Error 2
make[3]: Leaving directory '/opt/toolchains/dc/kos/kernel/arch/dreamcast'
make[2]: *** [Makefile:8: all] Error 2
make[2]: Leaving directory '/opt/toolchains/dc/kos/kernel/arch'
make[1]: *** [/opt/toolchains/dc/kos/Makefile.rules:45: _dir_arch] Error 2
make[1]: Leaving directory '/opt/toolchains/dc/kos/kernel'
make: *** [Makefile:27: all] Error 255

Hmm i vaguely remember this before
AtariOwl
DCEmu Freak
DCEmu Freak
Posts: 91
Joined: Fri May 23, 2008 5:57 am

Re: Wiki feedback

Post by AtariOwl » Wed May 16, 2018 10:29 am

Ahaaaa found it.. sorry to be a pest i shall push on
AtariOwl
DCEmu Freak
DCEmu Freak
Posts: 91
Joined: Fri May 23, 2008 5:57 am

Re: Wiki feedback

Post by AtariOwl » Thu May 17, 2018 4:46 am

No... i'm back where i was earlier and this time the places i found the genromfs files are missing :(

Hmmm it seems like a whole chunk is missing

Code: Select all

/opt/toolchains/dc/kos/utils/gnu_wrappers/kos-cc: line 50: /opt/toolchains/dc/sh-elf/bin/sh-elf-gcc: No such file or directory
There should be an sh-elf directory in /opt/toolchains/dc?

There's nothing there but kos and kos-ports

OK stepping through its going wrong at the sh download.sh part

OK thats done now its the make for make erase=1 that fails

Code: Select all

$ make erase=1
patch -N -d gcc-4.7.3 -p1 < /opt/toolchains/dc/kos/utils/dc-chain/patches/gcc-4.7.3-kos.diff
make: *** [Makefile:108: /opt/toolchains/dc/kos/utils/dc-chain/patches/gcc-4.7.3-kos.diff] Error 127

nymus
DC Developer
DC Developer
Posts: 950
Joined: Tue Feb 11, 2003 4:12 pm
Location: In a Dream

Re: Wiki feedback

Post by nymus » Sat May 19, 2018 7:53 pm

Getting errors in building genromfs means that you were already compiling kos. You would have had the tools already built to do this so are you getting errors rebuilding them?

I personally prefer to install my dc tools in my home directory for permissions and system separation. Also, what did you mean by you "found it" referring to the genromfs include error? (almost) Everyithing in the utils directory is meant to compile against your host includes (you probably know this, but I always get errors here because I'm on an OS X Lion MacBook using macports libraries)
behold the mind
inspired by Dreamcast
AtariOwl
DCEmu Freak
DCEmu Freak
Posts: 91
Joined: Fri May 23, 2008 5:57 am

Re: Wiki feedback

Post by AtariOwl » Sun May 20, 2018 6:28 pm

Sorry by found it i just mean i had found the previous time i had the same issues. It was a muc more successful effort last time

Then i started working backwards to see just how early it failed.
The answer... very early


essentially nothing built
nymus
DC Developer
DC Developer
Posts: 950
Joined: Tue Feb 11, 2003 4:12 pm
Location: In a Dream

Re: Wiki feedback

Post by nymus » Sun May 20, 2018 9:13 pm

Coincidentally, the top of page 4 in this thread shows you encountered the same genromfs error before. Assuming you resolved that one and are now having trouble building the tools, it might help to know which stage is failing and the compiler error. I'm not using Windows so I can't be as useful as others, but it just occurred to me that this could be a great way to make use of the new Linux environment built into Windows 10!

All the best getting this sorted out.
behold the mind
inspired by Dreamcast
AtariOwl
DCEmu Freak
DCEmu Freak
Posts: 91
Joined: Fri May 23, 2008 5:57 am

Re: Wiki feedback

Post by AtariOwl » Mon May 21, 2018 5:47 pm

Yes that was what i was referring to about found it

i have now started working through the installation by hand
the download.sh failed and so i had to do that individually, then run unpach.sh then the make erase=1 failed
and at that pint i had to go away

for a few days

its frustrating
User avatar
lerabot
DCEmu Freak
DCEmu Freak
Posts: 93
Joined: Sun Nov 01, 2015 8:25 pm

Re: Wiki feedback

Post by lerabot » Fri Sep 07, 2018 9:07 am

Now that I have a bit more experience with the DC, I'd love to be able to contribute more to the wiki.

I've been looking at how its organized and I wonder if it would be a good idea to streamline it. What I mean is that if you're new to DC programming and you want to make a game, the few first thing you want to look up is how to make a thing move on the screen. Then adding sound, etc.

All the more technical info could be in a different section (optimizing, hardware info, etc).

That doesn't mean everything have to be re-written, perhaps just presented differently.

1 - Dreamcast 101 (the toolchain, how to test your code, what do expect, current libs, etc)
2 - Compiling KOS DONE
3 - Drawing something on the screen DONE
4 - Basic interaction (how to use the controller)
5 - Playing sound (stream vs sfx)
6 - VMU i/o (could be work on a bit more)
7 - Asset management (conversion tool, romdisk, etc)
8 - Making CDs (cdi, iso, etc)

PM ME if you'd rather talk it over there.
User avatar
bogglez
Moderator
Moderator
Posts: 575
Joined: Sun Apr 20, 2014 9:45 am

Re: Wiki feedback

Post by bogglez » Sat Sep 08, 2018 4:17 am

Hi lerabot,

sadly I was really busy so I didn't have time to work on things here.

Would you be willing to write one of those guides? For example "How to obtain controller inputs" is still open and would be easy to write, but very useful for people.

I also put a lot of effort into helping people with the installation process, but I think the process on Windows might have changed quite a lot due to changes in msys2 and I'm not sure whether my guide is up to date there. Also not sure whether the Linux setup script still works for people (not sure how many people are using it).

EDIT:
I wasn't even aware of http://dev.dcemulation.org/tutorials ! Should we just convert those tutorials to a modern form in the new wiki?
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
User avatar
bogglez
Moderator
Moderator
Posts: 575
Joined: Sun Apr 20, 2014 9:45 am

Re: Wiki feedback

Post by bogglez » Sat Sep 08, 2018 5:18 am

Added http://dcemulation.org/?title=Efficient ... amcast_RAM to General
Removed https://www.youtube.com/watch?v=1_XhD5Msurc Video: Hardware Architecture Breakdown, guy deleted all his videos.
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
User avatar
lerabot
DCEmu Freak
DCEmu Freak
Posts: 93
Joined: Sun Nov 01, 2015 8:25 pm

Re: Wiki feedback

Post by lerabot » Sun Sep 09, 2018 11:09 am

Yes. I'll try to tackle some of them this week.

Would it be good to even host all the exemple on a github? I'll toy with some stuff and send them your way this week for doublecheck.
User avatar
bogglez
Moderator
Moderator
Posts: 575
Joined: Sun Apr 20, 2014 9:45 am

Re: Wiki feedback

Post by bogglez » Sun Sep 09, 2018 12:33 pm

You can just create a personal repository and point me to it, if you like, sure.
I'll be on a business trip until Friday, but I'll look at your results then. Maybe I'll check the forums sometimes if you have any questions, but I can't promise.
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
User avatar
lerabot
DCEmu Freak
DCEmu Freak
Posts: 93
Joined: Sun Nov 01, 2015 8:25 pm

Re: Wiki feedback

Post by lerabot » Sun Sep 09, 2018 8:42 pm

Here's a quick start. I'm still thinking how exactly to go about making the examples but I've added some references.

https://github.com/dreamcastdevs/dreamcast_tutorial
User avatar
bogglez
Moderator
Moderator
Posts: 575
Joined: Sun Apr 20, 2014 9:45 am

Re: Wiki feedback

Post by bogglez » Mon Sep 17, 2018 12:05 pm

I just had a look, great work!
I was wondering whether it would be better to not copy this over into the wiki, but instead add a little build script that calls pandoc and converts all the *.md files into one big PDF so it reads more like a book. The additional files could be bundled in an accompanying directory/tarball. That would make it easier for us to update everything and also for readers to print it out. pandoc also allows outputting an HTML file, so we can host it somewhere in that format as well. What do you think?

EDIT: apparently pandoc can also convert to the wiki markup format, so we can just copy the generated wiki markup over as well.
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
User avatar
lerabot
DCEmu Freak
DCEmu Freak
Posts: 93
Joined: Sun Nov 01, 2015 8:25 pm

Re: Wiki feedback

Post by lerabot » Mon Sep 17, 2018 3:50 pm

Sure, why not! I've dabbled with this as well -> https://github.com/dreamcastdevs/dreamc ... orial/wiki

Also, I did this in one work session last weekend. I'm gonna work on this more, but first I want to complete some stuff on my game so I can release something soon ;)

But it was suprisingly quick to make all of this. Formating and commenting it's exactly complete yet but it's a decent start.
User avatar
bogglez
Moderator
Moderator
Posts: 575
Joined: Sun Apr 20, 2014 9:45 am

Re: Wiki feedback

Post by bogglez » Mon Sep 17, 2018 4:05 pm

Yeah, the 80-20 rules applies here too.. Unfortunately many people give lose interest after finishing 90% and never release their intermediate work, which is a real shame! So I think it's great if you write this in the open.
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
Post Reply