From: John Voltz <john.voltz@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] question about make
Date: Mon, 28 Apr 2008 13:05:33 -0400 [thread overview]
Message-ID: <46a136670804281005t11bcda79mb985e6b78b25e717@mail.gmail.com> (raw)
I'm hoping someone can help me figure out the best way to fix the buildroot
makefiles for the festival voices and lexicons, right now make doesn't check
to see if you have already downloaded the tarball before it does it again.
What's the easiest way to check for the existence of a file with make?
This is the very simplistic method that is currently used for grabbing the
lexicons:
$(FESTLEX_STATUS_DIR)/.downloaded:
mkdir -p $(FESTLEX_STATUS_DIR)
ifeq ($(BR2_PACKAGE_FESTLEX_CMU),y)
$(WGET) -P $(DL_DIR) $(FESTIVAL_SITE)/$(LEX1)
endif
ifeq ($(BR2_PACKAGE_FESTLEX_OALD),y)
$(WGET) -P $(DL_DIR) $(FESTIVAL_SITE)/$(LEX2)
endif
ifeq ($(BR2_PACKAGE_FESTLEX_POS),y)
$(WGET) -P $(DL_DIR) $(FESTIVAL_SITE)/$(LEX3)
endif
touch $@
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080428/53688978/attachment.htm
next reply other threads:[~2008-04-28 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 17:05 John Voltz [this message]
2008-04-29 1:04 ` [Buildroot] question about make Hamish Moffatt
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=46a136670804281005t11bcda79mb985e6b78b25e717@mail.gmail.com \
--to=john.voltz@gmail.com \
--cc=buildroot@busybox.net \
/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