gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

DS development > make command giving trouble with certain makefiles...

#174733 - cyberant - Sun Jul 11, 2010 3:44 pm

I'm trying to install PAlib following stage 2 in the tutorial: http://www.palib-dev.com/wiki/doku.php?id=installation
Quote:
As of devkitARM R28, you will need to rebuild palib to compile without vrambank errors. To do so, go to /devkitPro/PAlib/source/ directory and run the clean.bat file, then the build.bat file.


When I try to run either clean.bat or build.bat it gives me the following error:
Quote:
/bin/sh: d/devkitPro/msys/bin/make.exe: No such file or directory
make: *** [all] Error 1


When I checked other makefiles (in devkitpro's examples) I noticed that "direct" makefiles for one source folders work fine - but makefiles used for a group gives the same error.

I have Devkitpro 1.5.0 and PAlib 0912XX_beta. My OS is windows XP.

Relevant enviroment variables*:
DEVKITARM | d:\devkitPro\devkitARM
DEVKITPPC | d:\devkitPro\devkitPPC
DEVKITPRO | d:\devkitPro
DEVKITPSP | d:\devkitPro\devkitPSP
Path | d:\devkitPro\msys\bin; ... etc

What's going on here?

*(Originaly, all the Devkitpro variables were in the form "\d\devkitpro\..." but I changed them hoping it would make it work. the makefiles that give me errors, don't work either way - but should I change it back to "\d\devkitpro\..." anyway?)

Edit: I tried checking variables using the set command - devkitpro variables are shown in "\d\devkitpro\..." format. even though they appear in the "Enviroment Variables" window in "d:\devkitpro\..." format . What?!

#174736 - cyberant - Sun Jul 11, 2010 8:01 pm

Okay, I did quite a mess with the enviroment variables... but the problem seems to be solved -_-;

The story is, I set "make" command manually beforehand as "/d/devkitpro/msys/bin/make.exe" (thinking it should be written like DEVKITPRO and the others; not knowing that "path" already takes care of it and other msys tools - I only had the basic understanding of enviroment variables as "system shortcuts" ).

Later, I tried removing the "make" variable, but unknowingly, a certain program (free Commander) would crazily bring it back for some reason (and so it would reset other things I tried changing).

Finally, I tried closing that program and then the "make" variable was finally removed. Later I changed the original devkitpro variables back to "/d/devkitpro/..."

After all that, "make" command finally works both with PAlib (build/clean.bat too) and with other makefiles (until the next time I mess it >.>;)

Now I just want to make sure my envioment variables are correct. So what are the Enviroment Variables set for DevKitPro ?

#174754 - ritz - Thu Jul 15, 2010 3:31 pm

According to this post it seems that PAlib development has officially stopped. You may want to learn libnds instead (it's included with your devkitPro installation) before you go too far. Lots of examples are there to look at too.

P.S. If you decide to follow my advice, I would get rid of everything to do with your current devkitPro/PAlib installation and start with a new clean install using just the devkitPro installer.

#174758 - cyberant - Fri Jul 16, 2010 12:37 am

ritz wrote:
According to this post it seems that PAlib development has officially stopped. You may want to learn libnds instead (it's included with your devkitPro installation) before you go too far. Lots of examples are there to look at too.
Thanks. I was wondering whether I should keep with PAlib or try something else (straight libnds, or maybe other options?).

(... aaand I just read devkitpro's wiki topic about PAlib ...)

Quote:
P.S. If you decide to follow my advice, I would get rid of everything to do with your current devkitPro/PAlib installation and start with a new clean install using just the devkitPro installer.
I'll consider clean installing devkitpro, but I think the only problem was with the mess I made with the enviroment variables. But now its seems to be ok (I also compared the variables with ones on another computer with devkitpro).

Also, PALib just interacts with devkitarm, it doesn't really change how devkitarm works, does it? Is there really any harm in keeping it ? (likely for its source code)

I'll probably check the available links for a good tutorial but if you have ones you recommend I'd be glad to hear it. (So far I made a quick follow through dev-scene's incomplete tutorial. patater's seems over comprehensive for me right now)

#174759 - ritz - Fri Jul 16, 2010 5:19 am

cyberant wrote:
Also, PALib just interacts with devkitarm, it doesn't really change how devkitarm works, does it? Is there really any harm in keeping it ? (likely for its source code)

I don't see any harm in keeping it. It's just a library as far as I know (I've never used it so don't quote me on that). Others might chime in with a better answer on this.

cyberant wrote:
I'll probably check the available links for a good tutorial but if you have ones you recommend I'd be glad to hear it. (So far I made a quick follow through dev-scene's incomplete tutorial. patater's seems over comprehensive for me right now)

You got me there. I'm not sure of a complete, high level tutorial for the DS. I just learned stuff by poking around libnds examples, library source code, reading GBATEK, and a bunch of trial & error.

This seems to come up a bit: Is there a decent, recent, complete tutorial for the DS? I was somewhat excited to accidently find a paper some guy wrote for his master's degree that looked like a pretty good and complete write-up on the DS. My smile went upside down when I was told it was out-of-date.

Here's the post about it: http://forum.gbadev.org/viewtopic.php?t=17068

Maybe someone could contact the writer and ask for permission to use the DS part of his paper. If allowed, we could begin bringing it up to date. At the very least it would be a good base to start with. Maybe even wiki it. I dunno, I'm just talking out my ass.

#174760 - fincs - Fri Jul 16, 2010 10:40 am

It is best for newcomers to skip PAlib because in the end you would have to port your PAlib project to libnds (which is painful if you don't know how the DS works).

Starting with plain libnds means you will be able to access official devkitPro support & you won't rely on third-party tools that might get outdated.

#174782 - wintermute - Mon Jul 19, 2010 11:53 am

cyberant wrote:


Also, PALib just interacts with devkitarm, it doesn't really change how devkitarm works, does it? Is there really any harm in keeping it ? (likely for its source code)


The reason devkitPro doesn't support PAlib is basically due to the damage their installer caused to a devkitARM installation. At one point, rather than fix their library to work with the latest tools they chose to overwrite tools and libraries with older and/or modified versions. This resulted in a situation where none of the libnds examples would compile.

Please don't read the PAlib source code, follow PAlib tutorials or listen to anything PAlib fans tell you, you'll regret it later.

Probably the best resources right now are Patater's guide, Tonc and the dev channels on IRC ( link in sig).
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog

#174783 - vuurrobin - Mon Jul 19, 2010 12:09 pm

wintermute wrote:
Probably the best resources right now are Patater's guide, Tonc and the dev channels on IRC ( link in sig).


don't forget the libnds examples.
_________________
my blog:
http://vuurrobin.100webcustomers.com/

#174788 - wintermute - Mon Jul 19, 2010 10:55 pm

hehe, bizarrely I did mean to mention them & somehow didn't
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog