Hacking New Theme for EZ-Flash Omega!

  • Thread starter Thread starter Sterophonick
  • Start date Start date
  • Views Views 630,777
  • Replies Replies 1,506
  • Likes Likes 52
So I'm trying to make a custom theme for this but I keep hitting this error. I just installed DevkitPro and I don't know what would cause this to happen. Any ideas?

View attachment 437721
You would need to scroll up further to find the actual root problem. GCC is dumb like that.
 
Then I'm not really sure what's going on, can you capture the GCC output as a .txt?
There wouldn't be any point because what I've shown is what would be on the txt.

This is the very first time I've ever even touched devkit pro, I have no clue what is going on, except for the fact that I'm getting a vague error.
 
There wouldn't be any point because what I've shown is what would be on the txt.

This is the very first time I've ever even touched devkit pro, I have no clue what is going on, except for the fact that I'm getting a vague error.
zip up your folder that you are working from so i can test it
 
It's basically the same as the source code since I haven't even managed to get started, no point in sending it
did you install devkitpro? https://github.com/devkitPro/installer/releases
did you set it up it for gba?
1716063032373.png

not sure? follow this guide -> https://sterophonick.github.io/pages/projects/howtoskinsimple.html
 
I wouldn't have gotten to this point if I hadn't done that. In fact I'm pretty sure it would have thrown a "program not found" error instead of the error I'm having.

So I'm trying to make a custom theme for this but I keep hitting this error. I just installed DevkitPro and I don't know what would cause this to happen. Any ideas?

View attachment 437721
I'm getting the same error myself now! no idea what happened. I'm guessing something with the devkitpro installs. something got changed and now it broken.
 
I don't know when, but recent devkitpro has become strict about definitions and pointer types.
Many warnings have been changed to errors, so you can build after fixing them.
 
I don't know when, but recent devkitpro has become strict about definitions and pointer types.
Many warnings have been changed to errors, so you can build after fixing them.
lovely, they need to change it back. my stuff built fine before! :/
 
Not really a problem devkitPro introduced but rather gcc 14.1.0 is more strict. These errors are luckily easy to fix. Just include the missing headers.
 
Confirming the errors are from the update to GCC 14.1.1. Will get around to updating both kernels eventually.
Post automatically merged:

Compilation for both kernels has been fixed. No update issued as functionality was not changed. Re-clone your code and try again to be sure.
 
Last edited by Sterophonick,
Well I've hit another problem, this time in regards to converting the primary assets. When I go to build the skin files, the bat file doesn't see the skin files
1716759170691.png

Now it says the files aren't there which I know can't be right because, well, they are.

1716759242948.png


Any ideas on what would cause the script to just flat out ignore the bmps?
 
Well I've hit another problem, this time in regards to converting the primary assets. When I go to build the skin files, the bat file doesn't see the skin files
View attachment 439266
Now it says the files aren't there which I know can't be right because, well, they are.

View attachment 439267

Any ideas on what would cause the script to just flat out ignore the bmps?
did you change the code to point to "imagename" .bmp? as you have to convert the image files to a .h file with the same name as the .gmp file. the grit program converts the files to a .h file for building.
 
did you change the code to point to "imagename" .bmp? as you have to convert the image files to a .h file with the same name as the .gmp file. the grit program converts the files to a .h file for building.
Actually figured it out a minute ago, turns out I was being a moron and forgetting the fact that Gimp has massive disrespect for BMP files, so i just re-saved the images in mspaint (the XP one for those wondering) and it just worked lol. Will post final results soon!
 
  • Like
Reactions: f3bandit

Site & Scene News

Popular threads in this forum