Reference

Some references to read and to figure out what we're going to use:

For the GUI: GTK+ cross-platform GUI toolkit
What about Nuklear thing for the UI? We could write it in Lua! A lot of people use Lua to script out debugging operations on emulators. Might be a good idea at some point
Minimalist C Libraries. Examples of low footprint libraries.
Suckless. Old school libraries and tools, with good practices in mind. Good for references.
Single-file public-domain/open source libraries with minimal dependencies More minimalist or single file libs with a low footprint. Some of them are for 2D graphics.
For logging and debug: Log4C? Or should we write our own super-simple logging (To file and console) library?
Good old SDL. Even if it's in C++ we can split UI/Input/Audio in this layer and make the emulator go wild in C?
For unit testing. CTest Really nice idea, given the fact that we're using CMake already. Just select a different configuration and run those tests! Here's another tutorial, I found it easier to understand.

Nesdev has a lot of information available. A good place to start is the CPU page
A PDF with loads of good info
Found this txt Emulator development guide it has a lot of how-to's and good practices. Probably not something to begin with, but we'll use it to fine tune the emulator
More from Nesdev this is a plain text guide on how to write an emulator.
A 'recent' post on Medium, interesting read but not very technical
6502 Emulation notes
A good HOW TO on how to write emulation programs. Not specific to NES but it does touch topics about C performance and architecture. Might be a good read
Yet another Documentation on how to write an NES emulator.
Post about best practices and how to tackle the tasks
Visual6502 Javascript physical simulation of a 6502.
Same as above but a crazy dude wrote it in C
6502 Opcodes
Games and its mappers
Addressing modes
Moar about the addressing
Another 6502 reference
Opcodes in 'C mode'
NESTest
Invalid OPcodes
Writing a NES game

Provide feedback