Skip to content

Instantly share code, notes, and snippets.

🎯
Focusing

Stefan Hagen sdrees

🎯
Focusing
Block or report user

Report or block sdrees

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@sdrees
sdrees / compiling_building_c_cpp_notes.md
Created Jun 22, 2019 — forked from gubatron/compiling_building_c_cpp_notes.md
Things to remember when compiling and linking C/C++ programs
View compiling_building_c_cpp_notes.md

Things to remember when compiling/linking C/C++ software

by Angel Leon. March 17, 2015.

Include Paths

On the compilation phase, you will usually need to specify the different include paths so that the interfaces (.h, .hpp) which define structs, classes, constans, and functions can be found.

With gcc and llvm include paths are passed with -I/path/to/includes, you can pass as many -I as you need.

In Windows, cl.exe takes include paths with the following syntax: /I"c:\path\to\includes\ you can also pass as many as you need.

View gist:69627043c321cbfe8bf8
### Keybase proof
I hereby claim:
* I am sdrees on github.
* I am stefanhagen (https://keybase.io/stefanhagen) on keybase.
* I have a public key whose fingerprint is 2C06 803C B4FB FE2F F7D7 CC58 7890 A9A6 BD44 04E8
To claim this, I am signing this object:
You can’t perform that action at this time.