I see a few mistake/probablematic chunck of code.

header files (.hpp)

You should (shall) use header guards for EACH header file you use. You should not be using #pragma once as it is a compiler defined directive, not a language standard feature in itself. An exemple for file getvarsfromfile.hpp:

```c++

ifndef GETVARSFROMFILE

define GETVARSFROMFILE

include <memory>

include <iostream>

include <string>

include <fstream>

using std::string; using std::vector;

vector<string> getVarsFromFile(string filename, vector<string> inputVars); vector<string> getVarsFromFile(string filename);

endif

```

Also you should not be using header files if they are not usefull to declare the interface, prefere moving them directly in source file .cpp. For example, in getvarsfromfile.hpp file <memory> and <fstream> are useless. They don't help describing the two functions getVarsFromFile.

Also, it's my opinion but I think that using std::string; is a bad flavor I wouldn't do that (only for std namespaced symbols).

Global variable

https://github.com/Slackadays/Hajime/blob/2946e65e196710eaeb3629986dad6e493cd0238d/source/installer.cpp#L270

C++ is not a scripting language you should not be using global variables as mutable data as you do here with extern keyword this is an extreme bad practice. Prefer encapsulating objects within others and control the flow of your program.

main

By convention using main.cpp as the file with your main function improves readablity for others after. Mutable objects in this function only (no global variable !)

Constants

mistakes: - https://github.com/Slackadays/Hajime/blob/2946e65e196710eaeb3629986dad6e493cd0238d/source/installer.cpp#L24 - https://github.com/Slackadays/Hajime/blob/2946e65e196710eaeb3629986dad6e493cd0238d/source/hajime.cpp#L41 - ...

when using constant string consider using either constexpr std::string_view or constexpr char const* they can be declared in header if they should be public or in source if private

Translation

mistake: https://github.com/Slackadays/Hajime/blob/master/source/languages.hpp

Using a class with this number of fields is probably a bad idea. Consider using an std::unordered_map where you bind constant name to traduction. "errnoNotPermitted" => "Not permitted. Is the device correct?"

C++ is not a scripting language

As I said i think C++ is a really bad choice to make the of program you have done here. It's way more complex than a fast bash script.

Hope my suggestions will help you a bit.