| gfx | ||
| romfs | ||
| source | ||
| .clangd | ||
| .gitignore | ||
| .kateproject | ||
| build.sh | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| setup_distrobox.sh | ||
e6_3DS
e926/e621 image board client for the Nintendo 3DS
Development
Distrobox setup
Follow these instructions to install Distrobox on your system. You're usually gonna want to do it using your system's package manager.
Afterwards run ./setup_distrobox.sh for a quick setup.
You should now be able to log into the distrobox using distrobox enter.
Important
From now on ALL commands you run should be from within the 3ds-dev distrobox. Otherwise you'll run into problems, builds will fail, or you'll make a mess in your host system.
Integrating $CONTAINER_ID in your terminal's prompt makes it easier to tell.
IDE setup
Unfortunately for this one you'll have to mostly figure it out yourself.
I use Kate and with the provided .kateproject you can just launch an instance from the host and it should hook into the distrobox for clang integrations.
Building from source
Make sure that you followed [#distrobox-setup] and it didn't yield any errors! You should have devkitpro and all dependencies installed now.
Also ensure that you are in the distrobox environment by now - if echo ${CONTAINER_ID} returns 3ds-dev, you're all good. Otherwise enter the previously created container with distrobox enter 3ds-dev
You may build with either the build.sh script provided or with make. If you wish to edit it using an lsp-server enabled IDE, you're gonna want to use bear -- make to generate associated compilation info.
The simplest way to build it:
./build.sh
Generating/converting fonts
The 3DS doesn't read TTF fonts, so we need to convert it into bcfnt with mkbcfnt included in the tex3ds package
mkbcfnt "Roboto-Regular.ttf" -o Roboto-Regular.bcfnt
Generating/converting textures and spritesheets
Troubleshooting
If tex3ds or any other command from the devkitpro toolkit return command not found:
- Try relogging into the container with
exitanddistrobox enter 3ds-dev. - Otherwise, you may just use binary paths like
/opt/devkitpro/tools/bin/tex3ds ...