#100315 - spinal_cord - Sun Aug 27, 2006 9:47 am
As the title says, im havibg a little trouble, i installed devkitpro with no errors, and the examples compile properly, it seems to be working fine.
I installed palib, and when it comes tp install.bat, i get this -
Code: |
C:\DEVKIT~1\PALIB>install
C:\DEVKIT~1\PALIB>make clean
make clean -C lib/arm7
make[1]: Entering directory `/c/DEVKIT~1/PALIB/lib/arm7'
clean ...arm7
make[1]: Leaving directory `/c/DEVKIT~1/PALIB/lib/arm7'
make clean -C lib/arm9
make[1]: Entering directory `/c/DEVKIT~1/PALIB/lib/arm9'
clean ...PA_Game
make[1]: Leaving directory `/c/DEVKIT~1/PALIB/lib/arm9'
C:\DEVKIT~1\PALIB>make
make -C lib/arm7
make[1]: Entering directory `/c/DEVKIT~1/PALIB/lib/arm7'
ModFile.c
make[2]: arm-elf-gcc: Command not found
make[2]: *** [ModFile.o] Error 127
make[1]: *** [build] Error 2
make[1]: Leaving directory `/c/DEVKIT~1/PALIB/lib/arm7'
make: *** [all] Error 2
C:\DEVKIT~1\PALIB>make archive
/c/devkitPro/devkitARM/arm-elf/bin/ar -cr lib/libpa7.a lib/arm7/build/command7.
o lib/arm7/build/microphone7.o lib/arm7/build/ModFile.o lib/arm7/build/PA.o li
b/arm7/build/Sound7.o
make: /c/devkitPro/devkitARM/arm-elf/bin/ar: Command not found
make: *** [archive] Error 127
C:\DEVKIT~1\PALIB> |
Have i missed a step?
_________________
I'm not a boring person, it's just that boring things keep happening to me.
Homepage
#100321 - josath - Sun Aug 27, 2006 10:58 am
Unfortunately, PAlib is not as well tested as devkitpro is.
It looks like you are using an old version of PAlib, as it is trying to use 'arm-elf-...' instead of the newer 'arm-eabi-...'. Try downloading the latest version of PAlib (if you can find it). You wont get much help for PAlib here, I suggest posting on their forums.
#100324 - spinal_cord - Sun Aug 27, 2006 11:15 am
I get the same thing with the lates download also.
_________________
I'm not a boring person, it's just that boring things keep happening to me.
Homepage
#100371 - gmiller - Sun Aug 27, 2006 4:22 pm
You might want to look at the makefile and see if it defines a "prefix" for the commands (somthing like):
Code: |
**********************
PREFIX=arm-elf
CC=$(PREFIX)gcc
***************
|
then you could change it to:
Of course it could also me that your PATH environment variable does not include your current ARM tool chain. To see where it points type the following at the same prompt as where you where doing the make.
Edit: Sorry I see you are starting at the windows command prompt so the appropriate command is:
#100385 - gmiller - Sun Aug 27, 2006 5:26 pm
I went to source forge and got the library and to build the libraries using the devkitPro tools you need to find the following line in the make files:
Code: |
#---------------------------------------------------------------------------------
# the prefix on the compiler executables
#---------------------------------------------------------------------------------
PREFIX := arm-elf-
#---------------------------------------------------------------------------------
# any extra libraries we wish to link with the project
|
and change the "arm-elf-" to "arm-eabi-". Of course if there are any changes in the command line syntax this will not help, but it will make it run the correct ARM tool.
#100388 - spinal_cord - Sun Aug 27, 2006 5:36 pm
it is that already
_________________
I'm not a boring person, it's just that boring things keep happening to me.
Homepage
#100390 - gmiller - Sun Aug 27, 2006 5:40 pm
Your error message:
Code: |
make[2]: arm-elf-gcc: Command not found
|
makes me think not ...
#100392 - spinal_cord - Sun Aug 27, 2006 5:52 pm
the file isnt anywhere on my drive! perhaps something didnt install properly.
_________________
I'm not a boring person, it's just that boring things keep happening to me.
Homepage
#100402 - gmiller - Sun Aug 27, 2006 6:28 pm
Are you using devkitPro, and does the file arm-eabi-gcc.exe exist? If so then you need to make the changes to the makefile as I stated. I downloaded the library and make the changes and it starts to work but there is a problem building the arm7 code PA.c. Having never looked at this code before I am not sure why it can't find the symbol DISP_SR which is defined in the ndslib/include/interrupts.h file which I believe it is including. But I did not check the other required code for PAlib so I might be missing more.
#100405 - gmiller - Sun Aug 27, 2006 6:41 pm
I guess I am just stupid and the real declaration of the DISP_SR is in registers_alt.h which you would need to include int the source file PA.c so make it work. Otherwise the new names for those registers are REG_?? so the new name should be REG_DISP_SR I guess. I am going to try that now.
#100416 - gmiller - Sun Aug 27, 2006 8:02 pm
Ok to get the library to build (this all I have done) you need to change the following files:
Code: |
./include/nds/arm9/PA_Interrupt.h
./include/nds/arm9/PA_Sprite.h
./include/nds/arm9/PA_SpriteDual.h
./lib/arm7/Makefile
./lib/arm7/PA.c
./lib/arm9/PA/PA_Mode7.c
|
in PA_Interrupt.h add the #ifdef wrapper around the REG_VCOUNT decl.
Code: |
#ifndef REG_VCOUNT^M
#define REG_VCOUNT _REG16(0x04000006)^M
#endif^M
|
In the PA_Sprite.h change the definition of OBJ_X to OBJ_X_MASK and OBJ_Y to OBJ_MASK, then change any reference to the original to the new name.
In the file PA_SpriteDual change the references to OBJ_X and OBJ_Y to OBJ_X_MASK and OBJ_Y_MASK as well.
The Makefile in arm7 needs the PREFIX changed as in the original message.
In PA.c change the line that reference DISP_SR to:
Code: |
REG_DISPSTAT = DISP_VBLANK_IRQ;
|
In PA_Mode7.c comment out the two lines:
Code: |
#define INT_MIN 0
#define INT_MAX 2147483647
|
This will get the library to build. There may be an issue with the code change in PA.c (I would have assume it would have been REG_DISPSTAT |= DISP_VBLANK_IRQ) but the original did the assignment to DISP_SR.
#100440 - spinal_cord - Sun Aug 27, 2006 11:02 pm
I got my old setup working again - devkitpro 1.2.7 with palib040306. Ill try what you said in a day or two, but im a bit tired right now. youd think when people release newer versions of thing, theyd make sure they work first. oh well.
thanks for the help.
_________________
I'm not a boring person, it's just that boring things keep happening to me.
Homepage
#100444 - gmiller - Sun Aug 27, 2006 11:16 pm
The problem is that the development kit changed and the makefile and code has not changed to keep up. Of coure the changes that I indicated are NOT backwards compatable but could be made so.