key9 wrote:
Hi all
look at the organize tree
main.c
------
#include lib_adapter.c
Although omitting <or "" may work on your compiler, it is not conforming.
main()
{
foo();
}
lib_adapter.c
-------------
#include "foo_liba.c"
#include "foo_libb.c"
void foo(){
#ifdef USING_LIBA
foo_liba()
#endif
#ifdef USING_LIBB
foo_libb()
#endif
}
void need();
lib_a.c
=======
void foo_liba()
{
need();
}
lib_b.c
-------
void foo_libb()
{
need()
}
gcc -o main main.c lib_adapter.c lib_a.c lib_b.c
the code can not be complained , what I want to know is
I can not put need() out side of the lib_adapter.c
Do you mean that gcc does not give error messages or warnings? If not,
I can't interpret your comment.
1.how to write include structure
Questions should have a subject, verb, and end in a question mark, as
well as ask a question: "How can I include a structure in my program?"
That might not be the question you intended to ask. I think you are
asking about how to use #include statements in a program.
By convention, C programs are separated into code files and declaration
files. The code files contain function definitions and normally have an
extension of .c. The declaration files have declarations normally used
by multiple code files and have an extension of .h. These naming and
organizational conventions are not requirements of the language, though,
and compilers don't care what extensions are used on the files.
Normally .c files are each compiled into a separate object file, then
the object file are linked into a single executable file. In contrast,
I have used a C dialect compiler (for small microprocessors) that
requires all code files to be compiled together -- it cannot compile to
object files and link. For that compiler, it is typical to have a main
file include other code files. This is not recommended for normal use,
though.
2.need I have to write .h file instead of include c file?
No. In general you should compile code files separately and link them.
I recommend writing a header file for each code and placing the
prototypes (and other definitions required to use the code module) in
the associated header file. Then include the header file in both the
code file defining the functions and code files using the defined functions.
I suggest finding a good text book on C.
--
Thad