It is extremely difficult to be productive with C/C++. Build systems and development workflows are hard to get right, and getting them wrong has huge cost.
I implemented yet-another-meta-build-system as an attempt to make recurring build-system interactions a bug rather than a feature.
Anothing missing piece is code generation, such as for network protocol definitions or HAL interfaces for firmware. I use ifgen for all code-generation needs.
In the end my entire Python ecosystem exists mainly to support mission-critical application development done in C/C++.
I use the following projects to test the build system, which supports nested dependencies:
Real projects:
Current projects:
What's Python?
Check out the YouTube series I'm working on where I go over my workflow and document notable feature developments.
Packages I've created are derived from
python-package-template,
a custom cookiecutter template.
A project template (that leverages a
config repository to keep templates
synchronized in the long-term) makes it easier to start writing code as a next
step immediately after justifying a new project.
See also: generated documentation
(created with pydoc).
Information about each project can be found on that project's README.md
linked below.
- datazen
- setuptools-wrapper
- svgen
- vcorelib
- vmklib
- vtelem
- runtimepy
- rcmpy
- userfs
- yambs
- ifgen
- conntextual
- quasimoto
What's TypeScript?
I got typescript-package-template into a usable state (similar to the one I'm using for Python projects) and spent time on console, but building an application for a browser is too labor-intensive to be practical for the kind of user-interface application(s) I'm looking to build.
It would be faster to implement a TUI graphics library from scratch in C++ than it would be to use TypeScript and web technologies to build even a single application, so that's my current plan.