[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to: organize application files and get GNU make to put theoutpu

From: Ted Byers
Subject: Re: How to: organize application files and get GNU make to put theoutput files into the right place.
Date: Mon, 25 Jan 2010 13:14:06 -0500

Hi, and thanks.

I have managed to get it all working adequately.

I am not yet entirely happy as, for my QA, I need both all my tests to compile and all of them to execute and give expected (correct) results.  In time, these tests will include both unit and integration tests (looking at interaction among different parts of the codebase).  And the objective is to get something similar to what the test suite for gcc does (give stats on the number of tests that passed and some output identifying what failed and how).  And given the amount of test code I expect, I need this to be as automated as practicable.

One last question.  Right now, I have:

CPPFLAGS = -Wall -pedantic -I ../include

I haven't set a variable for linking, so I suppose I am using whatever default value there may be (if there is one).

What would be the procedure to extend the CPPFLAGS (and whatever the corresponding link variable) so that if I invoke it in one way, the executable has all the debug info and no optimization, and if invoked in another way, without debug info and full optimization?  Ideally, if I specify either 'make debug' or 'make production', all the code, whether for a library or for the executable, would be compiled with either the debug info and no optimization or no debug info and full optimization.  Is there a standard way to do this?



On Sun, Jan 24, 2010 at 8:52 AM, James McElhannon <address@hidden> wrote:
I'm still relatively new to make, so sorry if any of this is obvious or not helpful.
I would try something like this:
app1: $(app1_src) $(app1_include) $(libs)
    cc $(whatever cc flags you need) test
    # if you should build the library before tests, then reverse the order of these steps.
  # to use 'test', if the test fails, will the compile of test fail, or do you have to run test?
    # if you have to run test, then run it now with its parameters
    # if you run test, and you want make to stop, in test use exit(n) where n != 0.
    test $(whatever params you need)
    cc ... whatever is left of the compile for app1
If all of this is standard for each step, you could try to wildcard the rule with app% or %.exe or whatever the naming convention is.
If you want make in the app folders to invoke make for the test, you want to look up 'recursive' make.  There are some strong thoughts out there as to whether or not recursive make is a good idea, but to me, it makes some things simpler.  If you want to do that, then you would have something like the following:
    make some_other_target
If you want the make of target to continue no matter what, then do "make -c some_other_target" do change to its directory first.
To automate what the building of the dependencies, there is a flag to the compiler, "cc -M" will go through the files and find all of the includes for you.
I'm sure there is a cool way to do all of this using autoconf et al but those are still magical to me.
Hope that helps,

From: Ted Byers
Sent: Thursday, January 21, 2010 5:16 PM
To: address@hidden
Subject: How to: organize application files and get GNU make to put theoutput files into the right place.

I managed to get GNU make to find the source files and headers from the right paths, but I am having trouble to get it to put gcc's output into the right place.

I made the following directory structure:


If I go into a given objs subdirectory, I can get the object files put into it.  So far, so good.
I could not get the same result from a given application's directory

app1 and app2 both use/ depend on, my library lib.

I was hoping it was possible to run make from an application's directory and put the main executable there.  And I wanted it to have each source file in each test directory be compiled to an executable in the same directory.  I am not sure I can automate inference of what cpp files in src a given  exe file in test would depend on (is there a way?).  But I want to prevent the production of the application exe or the library, if any of the tests fail.

Can I do this entirely from a single makefile in each application's directory, or do I have to put a makefile into the lib and each objs and test directory and somehow have the makefile in each application's directory invoke make on the makefiles in the corresponding objs and test subdirectories?  If so, how?  If this is in the manual, I seem to have somehow missed it.

Thanks for any help you can provide.


Help-make mailing list

R.E.(Ted) Byers, Ph.D.,Ed.D.
Merchant Services Corp.
350 Harry Walker Parkway North, Suite 8
Newmarket, Ontario
L3Y 8L3

reply via email to

[Prev in Thread] Current Thread [Next in Thread]