Groups > comp.os.linux.development.apps > #217

Re: Make file question about the .c.o rule

Path	csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From	Måns Rullgård <mans@mansr.com>
Newsgroups	comp.os.linux.development.apps
Subject	Re: Make file question about the .c.o rule
Date	Sun, 24 Jul 2011 19:12:15 +0100
Lines	25
Message-ID	<yw1x8vrn8s5c.fsf@unicorn.mansr.com> (permalink)
References	<993582FjekU1@mid.individual.net>
Mime-Version	1.0
Content-Type	text/plain; charset=iso-8859-1
Content-Transfer-Encoding	8bit
X-Trace	individual.net FKik4ChhharaitlVVB9h/AkGZCS7XAWLi5wNtjNge9xlDSFCvm
Cancel-Lock	sha1:BZTND7m9gjEVnqcMux5oyqqmxsU= sha1:8z8KGGdzYznitoBYkAgvciAupDE=
User-Agent	Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
Xref	x330-a1.tempe.blueboxinc.net comp.os.linux.development.apps:217

Show key headers only | View raw

General Schvantzkoph <schvantzkoph@yahoo.com> writes:

> How do I use the .c.o rule when the sources are in subdirectories,
>
> for example
>
> foo/src2.c
>
> bar/src2.c
>
> In my Makefile I have 
>
> .c.o: $(HDL_COMMON_INCLUDES) ${HDL_INCLUDES} $(PMACS_INCLUDES)
> 	$(CC) $(CFLAGS) -c $< 
>
> This compiles the sources and puts the .o files in the top directory 
> rather that the subdirectory. The problem is that Make doesn't realize 
> that the .o files exist so every invocation of make builds everything.

Use this command:
	$(CC) $(CFLAGS) -c -o $@ $<

-- 
Måns Rullgård
mans@mansr.com

Back to comp.os.linux.development.apps | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Make file question about the .c.o rule General Schvantzkoph <schvantzkoph@yahoo.com> - 2011-07-24 18:05 +0000
  Re: Make file question about the .c.o rule Måns Rullgård <mans@mansr.com> - 2011-07-24 19:12 +0100
    Re: Make file question about the .c.o rule General Schvantzkoph <schvantzkoph@yahoo.com> - 2011-07-24 18:23 +0000

csiph-web