TC-1/2 Goals

Things to learn during this stage that you should remember:

Basic use of the GNU Build System

Libtool, Autoconf, Automake. The initial set up of the project will best be done via libtoolize and bootstrap. Both facilitate the project setup done via autoreconf. However, once the project initiated (i.e., configure and the Makefile.in exist) you should depend on make only. See The GNU Build System.

Integration Into An Existing Framework

Putting your own code into the provided code base.

Strict Coding Style

Following a strict coding style is an essential part of collaborative work. Understanding the rationales behind rules is even better. See Coding Style.

Memory Leak Trackers

Using tools such as Valgrind (see Valgrind, The Ultimate Memory Debugger) to track memory leaks.

Using STL containers

The AST uses std::vector, misc::symbol uses std::set.

Version Control System

Using the Git version control system is mandatory. Learn to use its powers carefully to handle working in group and merge from a different upstream remote.

Workflow & Continuous Integrations

Using tools such as GitLab or GitHub are recommended to have a better visualization and organization of your TC. You should not only work on the Forge repository.

Take advantage of issues, merge requests and document your progress throughout the project. You should consider setting up a CI/CD (continuous integration/continuous development). In association to GitLab/GitHub, it can be used to trigger some checks (build, clang-format, your testsuite, etc.) after each operation you choose to handle (e.g. pushing, tagging, etc.).

Do not underestimate the power of such tools, they require a small setup, but can be of great convenience and effectiveness for such a long project.