Homebrew Homebrew Development

  • Thread starter Thread starter aliak11
  • Start date Start date
  • Views Views 1,476,584
  • Replies Replies 6,048
  • Likes Likes 54
  • Like
Reactions: filfat and st4rk
Yeah, I refreshed my path variables and it worked this time. Funny, I thought I had done that earlier. Anyway, thanks for the help.

EDIT: Fixed everything, compiled multiple versions, used Neimod sources and also added Slash-moulder's new version of ctrtool. There is no support for x86 in ctrtool that I am able to find. All switches and compilers only allow x64, sorry for the inconvenience.

Link: http://www.mediafire.com/download/mgs46o4poke19b8/CTR.zip
Neimod wrote makerom? what git repo are you looking at? also the latest is 0.11

isn't this the main git repo?
https://github.com/3DSGuy/Project_CTR/tree/master/makerom
 
Neimod wrote makerom? what git repo are you looking at? also the latest is 0.11

isn't this the main git repo?
https://github.com/3DSGuy/Project_CTR/tree/master/makerom
AH, you're right, forgot to rename all the folders before zipping them. I had his build of ctrtool in there and made copies of it for the base folders. Meant to rename it to applestash but must've gotten distracted. Thanks for pointing it out.

Edit: All fixed now, let me know if I made any other mistakes.
 
I have a question to. The playcoinsetter was ported from a dev unit by known methods. Can the actuel devmenu ( released by bbb) also be converted to .3ds and install .cia files, or will it still only work on a dev unit?

Anyway i was puzzling with that today ( with ctrtool and makerom, but honestly i dont know much about it), and just know i start to read this tread.
 
I have a question to. The playcoinsetter was ported from a dev unit by known methods. Can the actuel devmenu ( released by bbb) also be converted to .3ds and install .cia files, or will it still only work on a dev unit?

Anyway i was puzzling with that today ( with ctrtool and makerom, but honestly i dont know much about it), and just know i start to read this tread.
As has already been discussed at length, only the dev tools that are completely self-contained in user-mode permissions are bootable on a gateway card. Kernel-mode requiring apps, like devmenu and netset, can be converted, but will not start. If you had kernel-mode control, you would have no issues with running them.
 
Why they wouldn't? The guy of the 3DS doesn't lie.

I downloaded it just in case someone could need them in the future.
 
why? is he a Nintendo dev or something?
idk tbh what he works for, but he is/was heavily involved in a lot of dev work for the 3ds including 3dsexplorer and other projects for making homebrew rom images
.....basically he isnt a nobody saying "i haz h4cks", plus he already shared the playcoinsetter from the SDK, so he obviously had them
 
Noob question. Will this help to improve the development of Homebrew as a whole?

Since it shows how Nintendo implements some of their functionality at a high level, sure I guess it could help. The alternative would be to look at pure assembler code and figure it out (much harder).
 
Disassembling nintendo tools from official SDK is already polemical for Wii's Libogc.
even if libogc is using open source libraries, it's not "heavily based" on Nintendo's work but "is" and acts the exact same way Nintendo tools act. not really written legally, it's only a copy of the SDK.

Don't do the same thing for 3DS.
Write your own tools based on what you learn, not just reproduce its codes which would re-create the nintendo's executables.



Edit:
I completed the wiki page with the build environment.
Someone want to check the mistakes I did? I didn't test to compile homebrew yet so maybe there are things not working.

Someone released a homebrew with libCTRU already compiled, who was it? snailface maybe?
I don't know if it's easier to provide pre-build libraries or let the user do it (and learn).

Also, shouldn't built library files go to devkitPro folder instead of staying in the homebrew project's folder?
 
Disassembling nintendo tools from official SDK is already polemical for Wii's Libogc.
even if libogc is using open source libraries, it's not "heavily based" on Nintendo's work but "is" and acts the exact same way Nintendo tools act. not really written legally, it's only a copy of the SDK.

Don't do the same thing for 3DS.
Write your own tools based on what you learn, not just reproduce its codes which would re-create the nintendo's executables.



Edit:
I completed the wiki page with the build environment.
Someone want to check the mistakes I did? I didn't test to compile homebrew yet so maybe there are things not working.

Someone released a homebrew with libCTRU already compiled, who was it? snailface maybe?
I don't know if it's easier to provide pre-build libraries or let the user do it (and learn).

Also, shouldn't built library files go to devkitPro folder instead of staying in the homebrew project's folder?

Letting the user download ctrulib and compile it themselves makes the most sense. As it's updated frequently, they really should be using the latest versions. Most homebrew makefiles expect the compiled libctru folder in the structure one back from the source code's folder. As a result, you'll usually end up putting the homebrew folder into the same directory as your compiled ctrulib.

Plus, if you're making/compiling homebrew, you're going to have to learn how to compile it anyway.
 
Also, shouldn't built library files go to devkitPro folder instead of staying in the homebrew project's folder?
I think you need to be careful about putting files in the devkitPro folders as they can get deleted during updates
 

Site & Scene News

Popular threads in this forum