The low-level functionality simply draws to a block of memory. Usually, you'd want to provide the buffer as a pointer to wherever you want text to be drawn. In my font example that I gave you on IRC, I have it draw to a buffer in the PVR's memory pool. What the buffer width is is up to how you allo...

I'm certainly not the only person who has ever drawn text using the BIOS font. I simply provided you with a nice easy-to-use piece of code to do so. If you want to go at it yourself, look at the documentation for the low-level biosfont functionality in KOS. Thanks, question what does the buffer and...

I would like to know how the home brewers out there are drawing text on the screen. BlueCrab has pointed me to some code for drawing text using the bios font, but i noticed no one is crediting his awesome work which leads me to believe that this is another way. Any assistance in this matter would be...

Hi, guys

Thanks for all the feedback. Here is a very small sample of what I've been working on so far. It's just some skeleton files, but it will lay the groundwork for a state based game.

Link: https://www.dropbox.com/s/gt0ama6n0aytvge/Source.zip

Sincerely,

Vectrix Quest

Hi, Just got my development environment setup AGAIN and now I'm ready to code. I was thinking of creating a vector(shape) based shoot-em-up for the dreamcast using the basic 2d drawing commands. You and the enemies could be squares while the bullets could be circle or something. It would be a single...

I had to remove the development environment and now am having problems trying to get it resetup. $ make patch -d gcc-4.8.2 -p1 < /home/User/kallistios/utils/dc-chain/patches/gcc-4.8.2-kos.diff patching file gcc/configure patching file libgcc/config/sh/crt1.S patching file libgcc/config/sh/fake-kos.S...

Is there any difference between coding a Dreamcast game in SDL and Kallistios in terms of memory footprint, speed, graphics display or are they both equal? Any assistance in this matter would be greatly appreciated.

Sincerely,

Vectrix Quest

BlueCrab wrote:It built fine, with the exception of one utility that you're not likely to need anyway. You should be good to go.

Awsome, i hope to show you some of my talent soon.

Sincerely,

Vectrix Quest

You need to source the environ script, not run it. Like this (mind the dot and the space at the front): . ./environ.sh Here is the latest output. If everything went fine we should be in business. :) User@Mothra-PC ~ $ . ./environ.sh User@Mothra-PC ~ $ cd $KOS_BASE User@Mothra-PC ~/kallistios $ make...

Wordpad probably did break the file. You'll need to re-create it and edit it in a text editor that supports Unix-style line endings. Notepad++ was a popular choice, last I heard. I replaced the file and edited it using Notepad++. Now i get a new error: User@Mothra-PC ~ $ cd kallistios User@Mothra-P...

Yes, it appears to have worked correctly. It still doesn't seem to work. When i try to run the last part i get the error: User@Mothra-PC ~ $ cd kallistios User@Mothra-PC ~/kallistios $ . ./environ.sh -bash: ./environ.sh: No such file or directory User@Mothra-PC ~/kallistios $ Furthermore: When i ge...

So... I took a Windows machine and tried to set up a toolchain with Cygwin, and I think there's actually a bug with the 64-bit version of Cygwin. I ran into a similar problem you did with an internal compiler error when using the x86-64 version of Cygwin, but the process completed successfully on t...

No... Not the GCC Makefile, the dc-chain one. Nope: unsigned thread_local : 1; ^ gcc -c -DIN_GCC_FRONTEND -DIN_GCC_FRONTEND -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -...

Open up the Makefile in a text editor. Find the line that says "makejobs=-j4" and change it to "makejobs=" (just remove the -j4 part). Here is my copy of the build-gcc-sh-elf-4.7.3 makefile. # Makefile.in is generated from Makefile.tpl by 'autogen Makefile.def'. # # Makefile for...

I don't know what is actually wrong with that one, to be honest especially with how late it happened in the build (since it's happening on the -m4 build, which is the last part of building libstdc++). Try deleting the build-gcc-sh-elf-4.7.3 directory and running "make build-sh4-gcc-pass2"...

That's a bug in the binutils texinfo files. I never build them with my builds, so I had never noticed that issue... Re-run the unpack.sh script, then run the following two commands before doing the make: sed -e 's/ @colophon/ @@colophon/' -e 's/doc@cygnus.com/doc@@cygnus.com/' binutils-2.23.2/bfd/d...

Well I see the first error happened here rm -rf $backupdir; exit $rc ../../../binutils-2.23.2/bfd/doc/bfd.texinfo:325: unknown command `colophon' ../../../binutils-2.23.2/bfd/doc/bfd.texinfo:336: unknown command `cygnus' Makefile:421: recipe for target 'bfd.info' failed make[4]: *** [bfd.info] Erro...

well I noticed in the original error post that the 'port' url got that error, but the 'ports' url downloaded just find. I thought they would be 2 seperate packages. But you did get farther this time right? I just kinda chimed in, BlueCrab is the real master of this stuff. Yes i did get to the part ...

looks good until this part User@Mothra-PC ~ $ git clone git://git.code.sf.net/p/cadcdev/kos-port Cloning into 'kos-port'... fatal: The remote end hung up unexpectedly Since the remote server lost connection, maybe try running it again and see if the connection stays constant and thus finishes downl...

Even that is pretty old, as KOS isn't in SVN anymore anyway... Unfortunately, there is no automated way of getting things to work, but it isn't all that hard to get things going as long as you're willing to do a little bit of work (which, if you're planning on programming anyway, you should be will...