Discover gists
| // Quite minimal example showing how to configure MPSSE for SPI using libftdi | |
| // compile like this: g++ minimal_spi.cpp -o minimal_spi -lftdipp -lftdi | |
| #include <ftdi.hpp> | |
| #include <usb.h> | |
| #include <stdio.h> | |
| #include <iostream> | |
| #include <string.h> | |
| // UM232H development module | |
| #define VENDOR 0x0403 |
A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.
Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.
| Comandos do git | |
| git commit -m"contaúdo da mensagem de commit": Gravação de arquivo no git. Esse comando serve para commitar os arquivos no git. | |
| O "-m" é referete ao termo "mensseger". Ou seja, mensagem que será gravada no commit. | |
| ctrl + l = É o comando que limpa a tela do terminal do git. | |
| git log: Comando para visualizar os logs dos arquivos gravados no repositório. | |
| git remote add origin + endereço da pasta no github: Esse comando permite apontar para o repositório no github. |
Spotiamp features a builtin Shoutcast® server, so you can easily stream the music to any device supporting Shoutcast, such as Sonos.
I've installed version 5.8
In the last years I've been asked multiple times about the comparison between raylib and SDL libraries. Unfortunately, my experience with SDL was quite limited so I couldn't provide a good comparison. In the last two years I've learned about SDL and used it to teach at University so I feel that now I can provide a good comparison between both.
Hope it helps future users to better understand this two libraries internals and functionality.
| ;;; nano-org-wip.el --- N Λ N O org mode -*- lexical-binding: t -*- | |
| ;; Copyright (C) 2024 Nicolas P. Rougier | |
| ;; Maintainer: Nicolas P. Rougier <Nicolas.Rougier@inria.fr> | |
| ;; This file is not part of GNU Emacs. | |
| ;; This file is free software; you can redistribute it and/or modify | |
| ;; it under the terms of the GNU General Public License as published by | |
| ;; the Free Software Foundation; either version 3, or (at your option) |
For a brief user-level introduction to CMake, watch C++ Weekly, Episode 78, Intro to CMake by Jason Turner. LLVM’s CMake Primer provides a good high-level introduction to the CMake syntax. Go read it now.
After that, watch Mathieu Ropert’s CppCon 2017 talk Using Modern CMake Patterns to Enforce a Good Modular Design (slides). It provides a thorough explanation of what modern CMake is and why it is so much better than “old school” CMake. The modular design ideas in this talk are based on the book [Large-Scale C++ Software Design](https://www.amazon.de/Large-Scale-Soft