From: Eldad Zack <eldad@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] CUSTOM cflags replacement snippet
Date: Sat, 20 Nov 2004 13:28:37 +0200 [thread overview]
Message-ID: <200411201328.40736.eldad@gentoo.org> (raw)
In-Reply-To: <419EE0D6.2090900@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
On Saturday 20 November 2004 08:14, Chris White wrote:
> I created this quick little function to recursively patch Makefiles
> with custom CFLAGS.
wouldn't it be simpler to do:
for dir in $(find -name "Makefile" .)
do
sed -i \
-e "s:^CFLAGS.*:CFLAGS = ${CFLAGS}:" \
-e "s:^CXXFLAGS.*:CXXFLAGS = ${CXXFLAGS}:" \
${dir} \
|| die "Could not patch $directories/Makefile for custom CFLAGS"
done
--
Eldad Zack <eldad@gentoo.org>
Key/Fingerprint at pgp.mit.edu, ID 0x96EA0A93
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-20 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 6:14 [gentoo-dev] CUSTOM cflags replacement snippet Chris White
2004-11-20 11:28 ` Eldad Zack [this message]
2004-11-20 11:31 ` Eldad Zack
2004-11-20 11:49 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2004-11-20 15:18 ` [gentoo-dev] " Georgi Georgiev
2004-11-22 5:30 ` Aron Griffis
2004-11-22 18:27 ` Aron Griffis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200411201328.40736.eldad@gentoo.org \
--to=eldad@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox