Date: Sat, 12 Jun 2010 11:18:05 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: jroberson@jroberson.net Cc: arch@FreeBSD.org Subject: Re: Change to config(8) for OFED Message-ID: <20100612.111805.94843338670897167.imp@bsdimp.com> In-Reply-To: <20100612.101458.10150326125744273.imp@bsdimp.com> References: <alpine.BSF.2.00.1006111611380.1435@desktop> <20100612.101458.10150326125744273.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20100612.101458.10150326125744273.imp@bsdimp.com>
"M. Warner Losh" <imp@bsdimp.com> writes:
: In message: <alpine.BSF.2.00.1006111611380.1435@desktop>
: Jeff Roberson <jroberson@jroberson.net> writes:
: : I have a patch to permit compilation of files brought in from linux
: : that use the same name in multiple directories. I added a new
: : directive called 'obj-prefix' which expects a quoted string that will
: : be prepended to the object file name. The problem is that this breaks
: : ${.IMPSRC}
:
: So foo_bar.o depends on bar.c? And ${.IMPSRC} expands to foo_bar.c?
:
: : I could also emit the source file name for those rules which are
: : created with prefixes and then require each file that uses a prefix to
: : also use compile-with. This wouldn't be so bad since they likely are
: : already using compile-with anyway.
:
: You'll have to emit compile rules, I think.
Ideally, you'd be able to emit:
foo_bar.o: $S/path/to/file/bar.c
${NORMAL_C}
@${NORMAL_CTFCONVERT}
but NORMAL_C is
NORMAL_C= ${CC} -c ${CFLAGS} ${WERROR} ${PROF} ${.IMPSRC}
and .IMPSRC is null. That seems like a bug to me, but I'm not sure if
the bug is that .IMPSRC is computed wrong, or if it really should be
${.ALLSRC}
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100612.111805.94843338670897167.imp>