And that would mean that I had to build and include the temporary make file
like before, huh?
On 10/11/06, Lloyd Brown <[EMAIL PROTECTED]> wrote:
It's not too difficult to include *all* the header files. I do
something like this:
> HEADERFILES:=$(wildcard *.h)
and then I can just add $(HEADERFILES) as a dependency. This doesn't do
anything about determining which header files are used on a
per-source-file basis, though. To do that, I think you'll have to
either hard code, or do some preprocessing. AFAIK, make doesn't really
have any facilities for determining dependencies or how to resolve them,
unless you tell it what they are.
You might have to go back to using the "-MM" output of gcc/g++.
Lloyd Brown
Daniel Dilts wrote:
> One more problem occured to me with the rule I made:
>
> $(OBJECT_PATH)/%.o : $(SOURCE_PATH)/%.cpp
> $(CXX) -c $(CPPFLAGS) $(CXXFLAGS) -o $@ $<
>
> This does not make any of the header files a dependency. Any ideas for
how
> to add that without hardcoding each of the heading file names (and only
> have
> as dependencies the header files that are actually used)?
>
> On 10/6/06, Frank Sorenson <[EMAIL PROTECTED]> wrote:
>>
>> Daniel Dilts wrote:
>> > Given a directory ./src that has an arbitrary number of .cpp files,
and
>> a
>> > directory ./obj that will contain the object files, I am trying to
>> create a
>> > Makefile that will automatically create all of the .o files,
regardless
>> of
>> > what files are added/removed from ./src.
>> >
>> > My thought is to use an included Makefile that has the rules to
create
>> each
>> > of the .o files.
>> >
>> > To create the .o files I use g++ -MM src/*cpp > Makefile.obj to
create
>> the
>> > included file.
>> >
>> > My Makefile looks like this:
>> >
>> > target : ...
>> >
>> > Makefile.obj : dummy
>> > g++ -MM src/*cpp > Makefile.obj
>> >
>> > .PHONY : dummy
>> > dummy :
>> > -@ ls > /dev/null 2> /dev/null
>> >
>> > include Makefile.obj
>> >
>> >
>> >
>> > I'm trying to make sure that Makefile.obj is recreated each time that
>> make
>> > is run. The dummy target is the only way I can think of making sure
>> that
>> > the Makefile.obj target is always run, but this seems like a really
bad
>> way
>> > of doing this. The problem (not a big deal in this case) is that the
>> > Makefile.obj target gets run 2-3 times.
>> >
>> > Also, on a sidenote, this creates a file with the format:
>> > file.o: file.cpp ...
>> >
>> > I'm also trying to figure out how to prepend "obj/" to each line in
the
>> > file.
>>
>> I'd suggest using the wildcard patterns to simplify this whole mess.
>> Perhaps something more along the lines of this:
>>
>> Makefile:
>> cfiles:=$(wildcard src/*.cpp)
>> ofiles:=$(patsubst src/%.cpp,obj/%.o,$(cfiles))
>>
>> all: $(ofiles)
>>
>> obj/%.o: src/%.cpp
>> @echo g++ $? -o $@
>> @touch $@
>>
>> Put your files into src, and it'll compile them all for you.
>>
>> Frank
>>
>>
>> --------------------
>> BYU Unix Users Group
>> http://uug.byu.edu/
>>
>> The opinions expressed in this message are the responsibility of their
>> author. They are not endorsed by BYU, the BYU CS Department or
BYU-UUG.
>> ___________________________________________________________________
>> List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
>>
> --------------------
> BYU Unix Users Group http://uug.byu.edu/
> The opinions expressed in this message are the responsibility of their
> author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG.
> ___________________________________________________________________
> List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
>
>
>
--------------------
BYU Unix Users Group
http://uug.byu.edu/
The opinions expressed in this message are the responsibility of their
author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG.
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
--------------------
BYU Unix Users Group
http://uug.byu.edu/
The opinions expressed in this message are the responsibility of their
author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG.
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list