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

This is a discussion on Need a good guide g++ on how to compile code within the C++ Programming forums, part of the General Programming Boards category; Actually, if you looked around the site to which I linked, you'd find... it's free to read online . You're ...

  1. #16
    a_capitalist_story
    Join Date
    Dec 2007
    Posts
    2,651
    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.

  2. #17
    Registered User
    Join Date
    May 2010
    Posts
    245
    Quote Originally Posted by rags_to_riches View Post
    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.

  3. #18
    Registered User
    Join Date
    May 2010
    Posts
    245
    Quote Originally Posted by rags_to_riches View Post
    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?

  4. #19
    and the Hat of Guessing tabstop's Avatar
    Join Date
    Nov 2007
    Posts
    14,185
    I would think (speaking as someone with publications) that more publications would be worse, not better.

  5. #20
    Registered User
    Join Date
    May 2010
    Posts
    245
    Quote Originally Posted by Salem View Post
    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!

Page 2 of 2 FirstFirst 12
Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Free Windows C Compile that give good warning?
    By stahta01 in forum C Programming
    Replies: 2
    Last Post: 11-24-2010, 08:20 PM
  2. guide me to make this code better or efficient
    By larne in forum C++ Programming
    Replies: 11
    Last Post: 01-19-2009, 04:54 AM
  3. The good wife's guide :)
    By Carlos in forum A Brief History of Cprogramming.com
    Replies: 15
    Last Post: 09-03-2003, 07:51 PM
  4. the definitive guide to code commenting
    By Aran in forum C++ Programming
    Replies: 5
    Last Post: 09-16-2002, 01:43 PM
  5. good guide on graphs please?
    By ss3x in forum C++ Programming
    Replies: 3
    Last Post: 04-13-2002, 09:19 AM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21