Thread: Need a good guide g++ on how to compile code

Actually, if you looked around the site to which I linked, you'd find...it's free to read online. You're not very resourceful for a developer.

Originally Posted by rags_to_riches

Actually, if you looked around the site to which I linked, you'd find...it's free to read online. You're not very resourceful for a developer.

Ha, funnily enough, that was already in my history. That's the -Wall example I was talking about

An Introduction to GCC - Linking with external libraries

Anyways, the people here were pretty helpful. Thanks for the link. It's definitely useful.

Originally Posted by rags_to_riches

Actually, if you looked around the site to which I linked, you'd find...it's free to read online. You're not very resourceful for a developer.

Tell you what, since you insist on using ad-hominem comments for the 2nd time in a row, let's post our CV's. Whoever has more publications, gets to keep their account. The loser has to delete their account. Deal?

I would think (speaking as someone with publications) that more publications would be worse, not better.

Originally Posted by Salem

There are only three relevant options you need worry about for additional libraries

-I for specifying where the pre-processor should look for .h files.
-L for specifying where the linker should look for .a files.
-l for specifying which .a files (the linker) should search in.

As for the names of .h files to #include in the source, and the names of the .a files to pass to the linker, well that's just down to reading the manual for each library you want to use.

After doing a small bit of reading, this makes perfect sense now. Thanks so much for being patient with me!