I would like to ask you this: how can i compile a program that includes a header that i make?
Example: we have test.c and we need for the compile the header that is in another folder.How can i tell to gcc to search for the header in the correct folder?
Another question:
I found on the web a project in C.In the folder except the source code ,there are also some files with names makefile.inc and makefile.What exactly are these? How can i produce for my code these files?
Thanks!!!
You just need to include the header, not compile it.
Look up a C++ Reference and learn How To Ask Questions The Smart WayOriginally Posted by Bjarne Stroustrup (2000-10-14)
@laserlight
yes, i know this , but i am asking you how the compiler see the header file.(the header file is in another folder)
give the compiler the explicit path liek this -
Code:#include "c:\somefolder\header.h"
Thanks abachler. It works the way you suggested me.
Is there any other way?
also anyone for my second question?
Absolute paths are dumb. You can't move the project around at all with absolute paths.
Use the -I option to tell the compiler where to look.
Eg.
gcc -I/path/to/header prog.c
> I found on the web a project in C.In the folder except the source code ,there are also
> some files with names makefile.inc and makefile.What exactly are these?
> How can i produce for my code these files?
Which OS?
Which Compiler?
Which IDE?
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
OS is linux
compiler is gcc
there is no IDE
Do you have a script called "configure" ?
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
no . But i can tell what the makefile.inc tells if i open it with word:
Code:CC = g++ # this line gives compiler optimizations that are geared towards g++ and Pentium4 # computers. Comment it out if you don't have a Pentium 4 (or Athlon XP) or up #CFLAGS = -O3 -mcpu=pentium4 -mtune=pentium4 \ # -mfpmath=sse -msse -mmmx -msse2 -pipe -fomit-frame-pointer -s LFLAGS = -lm -lpthread # Uncomment these two lines to use with any Pentium with MMX or up. # CFLAGS = -Wno-deprecated -mcpu=pentium -march=pentium -pipe \ # -fomit-frame-pointer -mmmx -funroll-all-loops -s # Uncomment these lines for some "safe" optimization flags #CFLAGS = -O3 -pipe -fomit-frame-pointer -funroll-all-loops -s
I guess you just type
make
at the command line.
Makefiles are just text files. It's definitely worth looking on the web for some tutorials on the subject. You'll see a lot of them in Unix/Linux developments.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
So, you could add -I path-to-your-header-file in the CFLAGS (if you always want the same one regardless of what option you choose, do:
at the end of makefile.inc.Code:CFLAGS += -I somepath
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
to compile multiple files you can write a shell script which includes complation statements for all files...
Or use makefiles, whcih is a much more intelligent way to solve the problem as:
1. It allows you to only recompile parts that actually have changes (or code that is dependent on the changes).
2. The makefile can use "templates", so you don't have to specify every step for every file, just what they depend on and a generic way to produce the expected output (for example "To make a .o file from a .cpp file you do ... ", although the syntax is of course not English)
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
