#159818 - Alphanoob - Mon Jul 07, 2008 5:58 am
I am just wondering if there is a way to set some sort of home file on the Msys so that I don't have to navigate to devkitPro every time I want to compile something. I forgot to save it to the C drive and put it on the desktop instead, so it is now a hassle to navigate to. I tried to move the folder, but I think that made my new vista mad at me, lol. (Or, in the words of silent_code: "a sad panda")
_________________
w00
#159819 - Dwedit - Mon Jul 07, 2008 6:24 am
Never store your own projects in the devkitpro folder, because sometimes it gets wiped clean during an update.
_________________
"We are merely sprites that dance at the beck and call of our button pressing overlord."
#159838 - silent_code - Mon Jul 07, 2008 11:15 am
Don't use paths with spaces (desktop = bad idea) and don't use Msys. :^)
All you have to do is run make in the standard cmd, if everyting is set up correctly. ;^)
_________________
July 5th 08: "Volumetric Shadow Demo" 1.6.0 (final) source released
June 5th 08: "Zombie NDS" WIP released!
It's all on my page, just click WWW below.
#159881 - Alphanoob - Mon Jul 07, 2008 10:13 pm
alright, so you guys are saying that:
1. I should use the regular command prompt (which didn't work on my old computer, as I had 2 compilers, it should work on this one now that I think of it...)
2. Save my projects to the C drive and *not* in the DevkitPRO folder.
thanks guys, will do. Makes sense now that I think of it, lol.
_________________
w00
#159886 - gauauu - Mon Jul 07, 2008 10:20 pm
| Alphanoob wrote: |
alright, so you guys are saying that:
1. I should use the regular command prompt (which didn't work on my old computer, as I had 2 compilers, it should work on this one now that I think of it...) |
I think* that the "proper" configuration would be to put the the msys binaries in your path, but not the devkitARM binary folder, then you have access to all the "standard" tools like make from your regular command prompt.
Then, make sure you have the devkitPro environment variable set correctly, and in your gba or ds project makefiles, use this variable to call the devkitARM binaries when building your projects.
If you do it this way, having 2 compilers shouldn't cause any problems.
* I'm no expert, so take this with a grain of salt, and ignore me when someone smarter comes along and corrects me.
#159894 - silent_code - Mon Jul 07, 2008 11:33 pm
I have devkitPro installed on C:\ and my projects are all on another drive.
It's just important that the paths don't include spaces (but depending on your configuration it might work.)
devkitPro's updater aready does quite a good job setting up your environment. :^)
All I then do, is set up a compiler setting for devkitARM in Code::Blocks, which tells the IDE where to find each program (gcc, make [which should be in Msys\bin, iIrc] etc.) and then I can just provide a standard libnds example makefile, press "compile" and "It works! (tm)" ;^)
_________________
July 5th 08: "Volumetric Shadow Demo" 1.6.0 (final) source released
June 5th 08: "Zombie NDS" WIP released!
It's all on my page, just click WWW below.