Is it just to test compile a simple program, with that header file #included in it?
To better understand the compilation process I’m writing my own “configure”, which tests for the existence of a few header and library files.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it just to test compile a simple program, with that header file #included in it?
To better understand the compilation process I’m writing my own “configure”, which tests for the existence of a few header and library files.
Yes, use the compiler to compile your simple test program. That’s the best and easiest way to see if the compiler can find the header. If you hard code #include search paths you’ll always have to modify and adapt for different compilers.