Explore >> Select a destination
|
You are here 
|
kushaldas.in | ||
| | | | |
geoff.tuxpup.com
|
|
| | | | | A friend recently very generously gifted me a flipper zero, and it's been a lot of fun to kick the tires. After exploring the stock firmware for a while, I wanted to customize it more than was possible with stock firmware, play with some apps people have built, and try my hand at running my own code on there. Initial Setup First, I grabbed a microSD card, formatted it, installed qflipper on my machine, and followed the instructions here to get everything updated. | |
| | | | |
blog.jak-linux.org
|
|
| | | | | In the past weeks, I was looking at several build systems. As it turned out, there is not a single sane generic build system out there. Autotools: Autotools are ugly, slow, and require an immense amount of code copies in the source tree. WAF: WAF is not as ugly as autools and it's faster and does not generate Makefiles or stuff like this. But it has serious issues: It requires one to copy it to the source tarball, has no stable API, and requires Python for building. Furthermore, support for unit testing is broken: It runs the unit tests, but does not abort the build process if the tests fail and does not display why the tests fail. | |
| | | | |
bylr.info
|
|
| | | | | Often, technical documentations include lists or other snippets of text that are strongly related to some of the projects code. vpypes documentation is no exception to this. For instance, the Built-in symbols section lists the units available to expressions: These units are related to the following piece of code: # vpype/utils.py UNITS = { "px": 1.0, "in": 96.0, "inch": 96.0, "ft": 12.0 * 96.0, "yd": 36.0 * 96.0, "mi": 1760.0 * 36. | |
| | | | |
www.iamsim.me
|
|
| | | |||
