#117887 - Diddl - Thu Feb 08, 2007 8:46 am
it seems with devkitARM r20 comes big changes. I've trouble to compile dsdoom now.
#117934 - wintermute - Thu Feb 08, 2007 9:01 pm
| Diddl wrote: |
| it seems with devkitARM r20 comes big changes. I've trouble to compile dsdoom now. |
Builds fine for me, did you try svn?
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog
#117946 - Diddl - Thu Feb 08, 2007 10:09 pm
no, i use this version 1.1 from Jefklak (klick) and I have some more modifications in it (Wad menu, /doom game directory, separate SAV directories for each WAD, support for R4/DSlink/Ninja ...).
with old toolkit it compiles fine. now I changed to v20 and newest libnds and newest libfat. now comes many errors ...
| Code: |
arm-eabi-gcc -MMD -MP -MF /D/Proj/NDS/dsdoom_v110_src/arm9/build/i_main.d -g -Wa
ll -O2 -march=armv5te -mtune=arm946e-s -fomit-frame-pointer -fno-strict-aliasing
-ffast-math -marm -mthumb-interwork -I/D/Proj/NDS/dsdoom_v110_src/arm9/include
-I/d/Programme/devkitPro/libnds/include -I/D/Proj/NDS/dsdoom_v110_src/arm9/build
-DARM9 -D__NDS__ -c /D/Proj/NDS/dsdoom_v110_src/arm9/source/i_main.c -o i_main.
o
d:/Proj/NDS/dsdoom_v110_src/arm9/source/i_main.c: In function 'switchConsole':
d:/Proj/NDS/dsdoom_v110_src/arm9/source/i_main.c:529: warning: implicit declarat
ion of function 'M_SizeDisplay'
d:/Proj/NDS/dsdoom_v110_src/arm9/source/i_main.c: In function 'main':
d:/Proj/NDS/dsdoom_v110_src/arm9/source/i_main.c:574: warning: assignment from i
ncompatible pointer type
d:/Proj/NDS/dsdoom_v110_src/arm9/source/i_main.c:592: error: 'VRAM_A_MAIN_BG_0x6
000000' undeclared (first use in this function)
d:/Proj/NDS/dsdoom_v110_src/arm9/source/i_main.c:592: error: (Each undeclared id
entifier is reported only once
d:/Proj/NDS/dsdoom_v110_src/arm9/source/i_main.c:592: error: for each function i
t appears in.)
d:/Proj/NDS/dsdoom_v110_src/arm9/source/i_main.c:593: error: 'VRAM_B_MAIN_BG_0x6
020000' undeclared (first use in this function)
d:/Proj/NDS/dsdoom_v110_src/arm9/source/i_main.c:638: warning: suggest explicit
braces to avoid ambiguous 'else'
d:/Proj/NDS/dsdoom_v110_src/arm9/source/i_main.c:639: warning: suggest explicit
braces to avoid ambiguous 'else'
make[2]: *** [i_main.o] Error 1
make[1]: *** [build] Error 2
make[1]: Leaving directory `/D/Proj/NDS/dsdoom_v110_src/arm9'
make: *** [arm9/dsdoom.elf] Error 2
$ |
#117952 - wintermute - Thu Feb 08, 2007 10:34 pm
Get 1.1.1 from SVN.
That includes Jefklak's updates and has been moved to libfat proper, it also builds just fine with r20.
What does support for R4/DSlink/Ninja involve?
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog
#117954 - Diddl - Thu Feb 08, 2007 10:35 pm
ok, looking exactly it is clear ...
VRAM_B_MAIN_BG_0x6000000 ==>
VRAM_B_MAIN_BG_0x06000000
#117957 - wintermute - Thu Feb 08, 2007 10:42 pm
Still, it might be interesting to see your changes and incorporate them in svn, they sound quite interesting.
What does support for R4/DSlink/Ninja involve?
Is that just moving to libfat?
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog
#118059 - Diddl - Fri Feb 09, 2007 4:10 pm
| wintermute wrote: |
| Still, it might be interesting to see your changes and incorporate them in svn, they sound quite interesting. |
is no problem. after todays work I will upload binary and source.
it's only a small beginners work for me (to learn NDS developing).
| wintermute wrote: |
| What does support for R4/DSlink/Ninja involve? |
i have changes in this io-drivers, because most of them doesn't have a timeout, so some of them 'hang' if this card isn't inserted.
currently I own a DS-Link, a M3 DS simply, a supercard lite and a M3 lite. same version of dsdoom wil work fine with all of this 4 cards.
| wintermute wrote: |
| Is that just moving to libfat? |
the day bevore yesterday I didn't know that there is a differnce between gba_nds_fat and libfat.
I have a download of Devkitpro 20, latest libnds and latest libfat and I wanted to compile dsdoom again. now I have only devkit 20 with latest libnds and old fat sources - and it works/compiles fine now!
I have implemented all my modified io-drivers in current libfat. It works fine.
###
rewrite of dsdoom to fit with libfat is a big thing. all FAT_ call to new function names ...
I think I will make a wrapper to go with new libfat.
#118066 - wintermute - Fri Feb 09, 2007 6:36 pm
| Diddl wrote: |
| wintermute wrote: | | What does support for R4/DSlink/Ninja involve? |
i have changes in this io-drivers, because most of them doesn't have a timeout, so some of them 'hang' if this card isn't inserted.
currently I own a DS-Link, a M3 DS simply, a supercard lite and a M3 lite. same version of dsdoom wil work fine with all of this 4 cards.
|
Does the new libfat also require these changes?
One big change for the latest libfat is the addition of the DLDI system which allows the binary to be patched for cards either not supported by default or not yet invented.
| Quote: |
rewrite of dsdoom to fit with libfat is a big thing. all FAT_ call to new function names ...
I think I will make a wrapper to go with new libfat. |
Well, as I said the dsdoom current SVN already has the necessary changes for libfat.
http://code.google.com/p/dsdoom/
I'm not sure why you would write a wrapper for the new libfat, the new function calls are all stdio - this was kind of the point.
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog
#118077 - Diddl - Fri Feb 09, 2007 10:01 pm
| wintermute wrote: |
Does the new libfat also require these changes?
One big change for the latest libfat is the addition of the DLDI system which allows the binary to be patched for cards either not supported by default or not yet invented. |
I offered Chishm this changes but he said io-driver are frozen since 12/2007 cause of DLDI.
DLDI is a very good idea, - for new (unknown) devices! but I prefer a simple mehtode. simple for end user ...
oh! super! I will download it.
| wintermute wrote: |
| I'm not sure why you would write a wrapper for the new libfat, the new function calls are all stdio - this was kind of the point. |
ah! I understand now, - this is the reason cause there is only one small fat.h without file and directory functions.
I was wondering about and thought anyone has forgotten to include fatfile.h and fatdir.h!
###
DsDoom binary old devkit (.nds): klick
DsDoom Src old devkit (.nds): klick
DsDoom Src new devkit (.nds): klick
my new devkit version is buggy yet. but now I take a look at your new dsdoom version!
###
I dream of a ROTT version for NDS, or a Jonof Duke3d version for NDS, or a shadow warrior ...
but it seems I'm too weak. I tried to compile a ROTT source without success. do you think it is possible?
#118261 - Diddl - Sun Feb 11, 2007 5:49 pm
sorry, dsdoom from (http://code.google.com/p/dsdoom/) doesn't run on my NDS lite. neither binary nor compiled source, both give same results.
source compiles fine with new devkitpro 20.
after starting dsdoom (tested on 4 cards patched with dldi) I choose "standard game". many console messages up to R_INIT DATA and this loading points. after that black screen (both screen) and nothing more ...
###
Jefklak (http://www.jefklak.com/Files/Doom?action=set) also has a new version with dldi running fine.
#119623 - moose - Sat Feb 24, 2007 9:15 pm
I just wanted to second the above listed version 1.1.0 working on the R4, saves also work. V111 hangs at black screens after the initial loading and ... progression at the very end before the DOOM title screen should appear.
_________________
Of all the things I have lost, I miss my mind the most.