Sometimes you need to build the binaries for Atmosphère, or you want to change something on the source code, for building your starting point should be: https://github.com/Atmosphere-NX/Atmosphere/blob/master/docs/building.md
On that document you can read:

Spoiler: Atmosphère Build Document

Building Atmosphère is a very straightforward process that relies almost exclusively on tools provided by the devkitPro organization.​

Dependencies:​

• devkitA64
• devkitARM
• Python 2 (Python 3 may work as well, but this is not guaranteed)
• LZ4
• PyCryptodome (optional)
• Hactool

Setup a DevKitPro environment: (https://devkitpro.org/wiki/Getting_Started)​

Install the following packages via (dkp-)pacman:​

• switch-dev
• switch-glm
• switch-libjpeg-turbo
• devkitARM
• devkitarm-rules
• hactool

Install the following library via python's package manager pip, required by exosphere:​

• lz4

Finally, clone the Atmosphère repository and run make under its root directory.​

That instructions are a little plain for we the noobs.

First you need Install a MSYS environment:
The latest instructions for install the MSYS environment are on https://gbatemp.net/threads/install-msys-environment.652234/ if you don't have one working, use them.

After you have the MSYS environment working you need to install DevKitPro
For that you can follow the instructions on the tutorial https://gbatemp.net/threads/setup-a-devkitpro-environment-on-windows.652238/

Now you can install DevKitPro packages:

pacman -S --noconfirm switch-dev devkitA64 dkp-toolchain-vars libnx switch-tools switch-mesa switch-libdrm_nouveau switch-sdl2

And Atmosphère prerequisites

Pacman -Sy --noconfirm devkitA64 devkitARM devkitarm-rules hactool mingw-w64-x86_64-python mingw-w64-x86_64-python-lz4 mingw-w64-x86_64-python-pycryptodome switch-dev switch-glm switch-libjpeg-turbo mingw-w64-x86_64-python-pip

For me I had to add zip package because even if wasn't explicit indicated on the build page, the code needs it.

Additional you need the packages git make lz4 for all to work, use the command:

Pacman -Sy --noconfirm zip git make lz4

The package hactool need you to copy your own prod.keys file on $HOME/.switch folder. (c:\msys64\home\USERNAME\.switch if you use the default installation folder)

LibNX Dependency
Atmosphère depends heavily on LibNX, generally when a major version of firmware is released or great changes on the code are made, changes to LibNX are also made.
The Atmosphère team works on their own repo of LibNX (https://github.com/Atmosphere-NX/libnx) and forward Pull Request to official SwitchBrew LibNX repo (https://github.com/switchbrew/libnx).

So if there are changes on LibNX you need to build it and install on your setup.

Spoiler: LibNX build and Install

If you haven't done already, setup the environment variables

export DEVKITPRO=/opt/devkitpro
export DEVKITARM=${DEVKITPRO}/devkitARM
export DEVKITPPC=${DEVKITPRO}/devkitPPC
export PATH=${DEVKITPRO}/tools/bin:$PATH

Then go to the Atmosphere-NX/LibNX repo and look what is the new branch for the current firmware, by example, for Firmware 16.0.0 the branch name is "1600_Support"

Then go to your MSYS MinGW64 window and clone the Atmosphere-NX/LibNX repo

cd ~
git clone --recursive https://github.com/Atmosphere-NX/libnx.git
cd libnx

And checkout the needed branch:

git checkout 1600_support

Then build and install the new LibNX libraries

make install -j$(nproc)

Now you can build Atmosphère with latest LibNX code; remember if you update the pacman LibNX package the changes get reversed and you need to build LibNX again.

Now is time to build the binaries
Clone the repository:

cd ~
git clone --recursive https://github.com/Atmosphere-NX/Atmosphere

Go to new created Atmosphère folder

cd Atmosphere

Never forget to create the environment variables for DevKitPro

export DEVKITPRO=/opt/devkitpro
export DEVKITARM=/opt/devkitpro/devkitARM
export DEVKITPPC=/opt/devkitpro/devkitPPC

And now you are ready to start the building process:

make -j$(nproc)

I do use the "-j$(nproc)" parameter to "bleed" all the available CPU to run the compiler, without that the whole process could take up to 1 hour.

I want to thank a lot to @binkinator and @godreborn for all the help and inspiration to make this guide, and want to ask you for help improving this guide.

Also special thanks to @godreborn for been a support of the users replies and suggestions to the OP.

Remember, as you are getting a new set of binaries, you need new set of sigpatches if you use it. So the great tool from @mrdude comes in hand, the latest release can be downloaded from: https://github.com/mrdude2478/IPS_Patch_Creator/releases/; you use the program to generate a new set of patches for your recently build package3 file.


Latest IPS Patch Creator:





-Edited: add sigpatches step and clean up a little-
-Edit 2, add LibNX build-

 

[binkinator]

Very nice!

I‘m going to spin up a blank Windows VM and see if I can follow by line and get to the prize.

 

[impeeza]

Remember, as you are getting a new set of binaries, you need new set of sigpatches if you use it. so the great tool from @mrdude comes in hand: https://gbatemp.net/threads/autoips-sig-patcher.574126/ you use the script to generate a new set of patches for your recently build package3 file.

 

[binkinator]

Works a treat! Tried my best to be a mindless fool just clicking what I was told and had no issues. Nicely done!

I’m going to destroy it all and see if I can run it like this:

go to https://switchbrew.org/wiki/Setting_up_Development_Environment and hit this link to download latest Windows graphical installer.

open up MSYS2 and run these two commands (basically just combining all yours into one)

pacman -Syu

pacman -Sy --noconfirm switch-dev devkitA64 dkp-toolchain-vars libnx switch-tools switch-mesa switch-libdrm_nouveau switch-sdl2 devkitARM devkitarm-rules hactool mingw-w64-x86_64-python mingw-w64-x86_64-python-lz4 mingw-w64-x86_64-python-pycryptodome switch-glm switch-libjpeg-turbo zip

(From here everything flows the same as the rest of the tut…

 

[fvig2001]

Can you enable debug outputs? Will probably be useful if I have to debug on a 1 bit mode switch (normally does not boot atmosphere without hacks)

 

[impeeza]

Yes. You can. I think i read something about thar on the github. Goto there

 

[DerBusVomFriedhof]

Thank you for this Guide, after reading that this set of instructions worked for a "mindless fool", I was a bit dumbstruck when the "git" command would not execute. I had to use pacman -S git for it to clone the repository.

I am trying to apply the ram overclock .diff from the RetroNX discord provided by ZachyCatGames, and while patchin the .diff file seemingly works, I sadly cant compile Atmosphere. When entering make -j it returns "command not found".

Still, without your guide i would not even be at this point id wager, so thanks again.

 

[binkinator]

Thank you for this Guide, after reading that this set of instructions worked for a "mindless fool", I was a bit dumbstruck when the "git" command would not execute. I had to use pacman -S git for it to clone the repository.

I am trying to apply the ram overclock .diff from the RetroNX discord provided by ZachyCatGames, and while patchin the .diff file seemingly works, I sadly cant compile Atmosphere. When entering make -j it returns "command not found".

Still, without your guide i would not even be at this point id wager, so thanks again.

Mindless fool checking in…when you followed @impeeza‘s instructions did you see any errors with this step? (you can run it again…it won’t hurt anything)

pacman -Sy --noconfirm devkitA64 devkitARM devkitarm-rules hactool mingw-w64-x86_64-python mingw-w64-x86_64-python-lz4 mingw-w64-x86_64-python-pycryptodome switch-dev switch-glm switch-libjpeg-turbo zip

Spoiler: Alternatively

if you installed everything with the install binary make sure you did the following.

• Ensure at least "Switch Development" is ticked - you can also leave the other options ticked if you wish.

either way that should include make and git and all the other tools needed to do proper builds.

 

[duckbill007]

If you building atmosphere yourself why to bother with IPS patches? Just patch sources one time and forget about generating patches for each build.

 

[dogcsty]

I would like to also add that sometimes the official libnx is not up to date compared to the atmosphere build (it was the case when atmosphere came out as 1.3.0) you might sometimes want to build libnx (with the same dependencies as atmosphere) with this fork https://github.com/Atmosphere-NX/libnx and choose the correct branch.

 

[DerBusVomFriedhof]

Thanks for getting back to me, I shall try again later today and try your suggestions. Really appreciated. Also duckbill and dogty. I’m completely new to this and while it sucks being a fool it’s really fun to aquire new „skills“.

 

[binkinator]

If you building atmosphere yourself why to bother with IPS patches? Just patch sources one time and forget about generating patches for each build.

Wouldn’t the patches conflict with the next build from upstream? or is the thought that since you’re doing it for a particular reason you would be merging that portion anyway, you might as well make the exception for sigpatches while you’re at it.

I would like to also add that sometimes the official libnx is not up to date compared to the atmosphere build (it was the case when atmosphere came out as 1.3.0) you might sometimes want to build libnx (with the same dependencies as atmosphere) with this fork https://github.com/Atmosphere-NX/libnx and choose the correct branch.

This topic requires some thought (hadn’t done so before). If you had already updated your build environment via the package manager you’d have to go back and pull the installed version of libnx out, correct? Not sure I’m sofisticated enough (yet) t know How to cleanly do this.



these are both great thoughts…

 

[dogcsty]

Wouldn’t the patches conflict with the next build from upstream? or is the thought that since you’re doing it for a particular reason you would be merging that portion anyway, you might as well make the exception for sigpatches while you’re at it.

This topic requires some thought (hadn’t done so before). If you had already updated your build environment via the package manager you’d have to go back and pull the installed version of libnx out, correct? Not sure I’m sofisticated enough (yet) t know How to cleanly do this.



these are both great thoughts…

The patches wouldn't conflict with the next build. If you look at the official sigpatches zip files you will notice that there are a lot of .ips files. There's only one file that is being used with your current Atmosphere build, the rest of the files are for the old ones (and there are some other files for the firmware). You can add the newest sigpatches afterwards without needing to delete yours

When it comes to libnx the package will be automatically added to your Devkitpro folder once you've built it from source (you can make a backup of the original libnx folder if you want to in Devkitpro/libnx or you can just re-update it if needed, or you can just rebuild it from the master branch).

I'm glad that there are threads like this I wish I had something like this to help me out I had to figure everything out by myself (but I guess you learn better this way). I appreciate the effort.

Another thread that could be useful is how to add the atmosphere-libs to your application for developping atmsophere modules, the makefile configuration can be a little bit tricky.

 

[binkinator]

The patches wouldn't conflict with the next build. If you look at the official sigpatches zip files you will notice that there are a lot of .ips files. There's only one file that is being used with your current Atmosphere build, the rest of the files are for the old ones (and there are some other files for the firmware). You can add the newest sigpatches afterwards without needing to delete yours

*eureka moment* Thank you, that clicked for me. Ofc

When it comes to libnx the package will be automatically added to your Devkitpro folder once you've built it from source (you can make a backup of the original libnx folder if you want to in Devkitpro/libnx or you can just re-update it if needed, or you can just rebuild it from the master branch).

ahhhh. Cool. It’s in one place and easy to sub out. Sweet!

I'm glad that there are threads like this I wish I had something like this to help me out I had to figure everything out by myself (but I guess you learn better this way). I appreciate the effort.

Many thanks to @impeeza for putting it together.

It really helps to be walked through something instead of just saying “unzip X at the top of your SD Card and hope for the best!”

Also give us rubes a platform to learn a little and step off onto the next dumb question…little by little…going places.

Another thread that could be useful is how to add the atmosphere-libs to your application for developping atmsophere modules, the makefile configuration can be a little bit tricky.

I understand each word you’re saying here, I just get lost when you put them in this particular order…
(in other words hells yes it would be useful!)

 

[impeeza]

Hello there, I make a little summary of the steps needed to generate new sigpatches using the @mrdude 's scripts. You need to generate new sigpatches if you compiling your version of Atmosphère:
https://gbatemp.net/threads/how-to-create-your-own-sigpatches.616288/, all comments and feedback and improvements are welcome.

 

[godreborn]

I seem to have the latest libnx already installed:

 

[BeckysFootSlave]

Always get this!
WTF am I doing wrong???

Did everything step by step, and also deleted everything completely and installed again!

I need help please!

 

[impeeza]

View attachment 327265

Always get this!
WTF am I doing wrong???

Did everything step by step, and also deleted everything completely and installed again!

I need help please!

Hello there, Seems you are missing a file from a include path, for me is busy workday but this night will look into. regards.

 

[BeckysFootSlave]

I even found a libjpeg turbo package on the Msys2 website!

Should I install that!
Forgot also to post a image of the environmental variables to ask if everything is correct!
Will do later!

@impeeza thank you again for your time!

 

[impeeza]

you are welcome, I also use my environment for other homebrew, so could be I have packages from them. will list all my packages when on home y let you to know.