- Joined
- Jul 7, 2010
- Messages
- 4,075
- Trophies
- 2
- Location
- /dev/random
- Website
- www.gudenau.net
- XP
- 6,346
- Country
libnds:
devkitpro-->libnds-->icon.bmp
PAlib:
PAlib-->lib-->defaultlogo.bmp
nfllib:
in same folder as any example's Makefile (icon.bmp)
This is also a very good method, as you don't have to worry about editing the MakeFile each time you want to make a new project - good thinking Rydian. I was about to recommend DSBuff, but people have very varied opinions on that software, so RomeR is just as good of a recommendation.I use RomeR to edit the info and icon after compilation.
[ft]RomeR[/ft]
In that case, you can edit it manually with ndstool (command line tool) and put whatever you want, no stupid watermark type thing. Also, editing the makefile isn't hard.RomeR adds something that shows it was modified by said program...but if you don't care about that bit, then it works just fine.
I think it only adds an entry to notify the user that the ROM image has been modified in case someone changes an icon for a commercial ROM, it's definatelly not something that would change the way a program works so I wouldn't really bother worrying about it. An icon is the least important part of a binary for the DS, some people don't even bother changing it from the default one.What does RomeR add? First I've heard of this, is it just some hex sig?
The makefile uses ndstool to gather pieces after compilation of homebrew, so why would we do the job twice?In that case, you can edit it manually with ndstool (command line tool) and put whatever you want, no stupid watermark type thing. Also, editing the makefile isn't hard.RomeR adds something that shows it was modified by said program...but if you don't care about that bit, then it works just fine.
You only have to change the string ICON at the top of the makefile@ndstool -c $@ -9 $(TARGET).bin $(ARM7BIN) $(LOGO) $(ICON) "$(TEXT1);$(TEXT2);$(TEXT3)"