Thread: uniting all .h files in an include folder

Hi guys

I have the following makefile, where I am building a library out of some code that used to build 3 unit tests. The problem is, if I want to use it as a library I will need the Header files with which to compile my application. I just want to know what statement I could put, so that all header files that are used to build the library, are copied into an include folder, I don't know if they need to keep the same file structure inside this include folder.

Thanks in advance,
Ed.

Code:

CXX=g++
CC=gcc

CXXFLAGS=-gstabs -I../../.. -Wall -D_REENTRANT
LDFLAGS=-lpthread

OBJ_DIR=.
BIN_DIR=.

THREAD_SRC=linux_thread.cc
SHARE_SRC=../../minidump_file_writer.cc\
	  ../../../common/string_conversion.cc\
	  ../../../common/linux/file_id.cc\
	  minidump_generator.cc
HANDLER_SRC=exception_handler.cc\
	    ../../../common/linux/guid_creator.cc
SHARE_C_SRC=../../../common/convert_UTF.c

THREAD_TEST_SRC=linux_thread_test.cc
MINIDUMP_TEST_SRC=minidump_test.cc
EXCEPTION_TEST_SRC=exception_handler_test.cc

THREAD_OBJ=$(patsubst %.cc,$(OBJ_DIR)/%.o,$(THREAD_SRC))
SHARE_OBJ=$(patsubst %.cc,$(OBJ_DIR)/%.o,$(SHARE_SRC))
HANDLER_OBJ=$(patsubst %.cc,$(OBJ_DIR)/%.o,$(HANDLER_SRC))
SHARE_C_OBJ=$(patsubst %.c,$(OBJ_DIR)/%.o,$(SHARE_C_SRC)) md5.o
THREAD_TEST_OBJ=$(patsubst %.cc,$(OBJ_DIR)/%.o, $(THREAD_TEST_SRC))\
		$(THREAD_OBJ)
MINIDUMP_TEST_OBJ=$(patsubst %.cc,$(OBJ_DIR)/%.o, $(MINIDUMP_TEST_SRC))\
		  $(THREAD_OBJ) $(SHARE_OBJ) $(SHARE_C_OBJ)
EXCEPTION_TEST_OBJ=$(patsubst %.cc,$(OBJ_DIR)/%.o, $(EXCEPTION_TEST_SRC))\
		   $(THREAD_OBJ) $(SHARE_OBJ) $(SHARE_C_OBJ) $(HANDLER_OBJ)

BIN=$(BIN_DIR)/minidump_test\
    $(BIN_DIR)/linux_thread_test\
    $(BIN_DIR)/exception_handler_test

BIN=$(BIN_DIR)/libexception_handler.a

LIB_OBJS= $(THREAD_OBJ) $(SHARE_OBJ) $(HANDLER_OBJ) $(SHARE_C_OBJ)

.PHONY:all clean

all:$(BIN)

$(BIN): $(LIB_OBJS)
	ar rcs $(BIN) $(LIB_OBJS)

#$(BIN_DIR)/linux_thread_test:$(THREAD_TEST_OBJ)
#	$(CXX) $(CXXFLAGS) $(LDFLAGS) $^ -o $@

#$(BIN_DIR)/minidump_test:$(MINIDUMP_TEST_OBJ)
#	$(CXX) $(CXXFLAGS) $(LDFLAGS) $^ -o $@

#$(BIN_DIR)/exception_handler_test:$(EXCEPTION_TEST_OBJ)
#	$(CXX) $(CXXFLAGS) $(LDFLAGS) $^ -o $@


# Rule for object files
%.o: %.cc
	$(CXX) $(CXXFLAGS) -c $<

md5.o:../../../common/md5.c
	$(CC) $(CXXFLAGS) -c $^

clean:
	rm -f $(BIN) *.o *.dmp

What statement you could put where, exactly?

I guess if you really mean that you're making a library, then your header files should be in the include path (/usr/local/include or whatever it is). But that would happen at install/copy time, not compile time.

What I mean, is that I know that the makefile will use a bunch of header files that come from different subdirectories.. and I find it annoying to build the library and do a trial and error search for this files, so that I can copy them and make an include with all of them in it.

You see, the makefile at first was meant for building unit-tests.. and I am modifying it so that all the object files used in those unit tests are archived in a single library that I can use with my own application.


Thanks,

Ed.

Well, wait. You're compiling three C++ files, right? You can't look at the source of those three files and see what .h files they use (or have grep look at the source for you)? Or are these somebody else's headers? I'm confused.

most compilers already put all the .h files in a single directory. Your project should as well. If you mean it shoudl put all your custom .h files from yoru projects in with all teh other .h files that are part of the compiler, then trust that is a bad idea. What if you accidentalyl write a custom math.h, ir woudl overwrite the base package math.h and break yoru other projects.

most compilers already put all the .h files in a single directory. Your project should as well. If you mean it shoudl put all your custom .h files from yoru projects in with all teh other .h files that are part of the compiler, then trust that is a bad idea. What if you accidentalyl write a custom math.h, ir woudl overwrite the base package math.h and break yoru other projects.

No.. but they are not in the same directory... that's what is painful about this project.. the header files are all in different subdirectories, it just looks for them there.

Well, wait. You're compiling three C++ files, right? You can't look at the source of those three files and see what .h files they use (or have grep look at the source for you)? Or are these somebody else's headers? I'm confused.

Well, I mean it was compiling 3 programs but , I'm trying to use those 3 programs's objects.. and compile them in a single library. So my output is a libexception_handler.a
but I need to obtain all the headers that were used to create this libexception_handler.a

Originally Posted by afflictedd2

Well, I mean it was compiling 3 programs but , I'm trying to use those 3 programs's objects.. and compile them in a single library. So my output is a libexception_handler.a
but I need to obtain all the headers that were used to create this libexception_handler.a

So if you have .o files, you don't need .h files (unless you're compiling extra code with those object files). If the .o files come from elsewhere, and you are supposed to be using them with your own code, then the .h files should come with; if people are giving you .o files without the corresponding .h files, then you need to hit them with a hammer until they stop. If you are making your .o files from .cc files, then the .cc files tell you what .h files you will need to compile them (probably -- some of the .h files may include other .h files).

On the other hand, reading your makefile, I don't see where you are using anybody else's .o files, except md5.o.