gcc flags -E stop after preprcoessor. #include literally includes header file -s output assembly (don’t assemble) -c output object file
gcc -shared foo.o -o foo.so - makes a dynamically linkable file. You actually have to make a object file first before you do this
g++ is gcc with some appropriate flags set for C++
-lgsl is the same as
-l gsl and looks in system paths for a file called
libgsl.o. It automatically appends
lib. Very odd to my sensibilities.
-I is useful to help
Header files and prototypes actually become “code” in the sense they are entries in the object file.
The C preprocessor.
It can be run on its own
#includeliterally brings that file in.
""is a difference in what search path it uses an prioritizes.
#definemcpp is an alternative
It can be programmed. This is typically ill adviuced http://conal.net/blog/posts/the-c-language-is-purely-functional An amusing essay saying that cpp is a pureply function programminbg language
__COUNTER__ is an autoincrementing thing
There are things for string concatenation
An amusing essay that
make is logic programming language. It is true.
The file system is the database of sorts.
There is a default makefile that is included with every make invocation if you don’t turn it off.
Cherno Cyril Stachniss https://www.youtube.com/c/CyrillStachniss/videos
Class vs struct Smart pointers new/delete ~ malloc + constructor caling static const virtual interfaces - classes that are all virtual methods name mangling
precompiled headers (pch)
Shake https://www.microsoft.com/en-us/research/uploads/prod/2018/03/build-systems.pdf build systems a la carte