Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Kenton <skenton@ou.edu>
To: buildroot@busybox.net
Subject: [Buildroot] How  automate source download from  a google drive?
Date: Wed, 18 Feb 2015 19:55:32 -0600	[thread overview]
Message-ID: <54E54294.3030702@ou.edu> (raw)

This is a bit off the wall. I'm working with a package called tovid
which you download from a google drive by clicking on a link on the wiki
Darn if I can figure out how to put that into the .mk file to automate it.
Look through packages directory and did not see anything obviously like it

Any thoughts would be appreciated

Steve Kenton

################################################################################
#
# tovid
#
################################################################################

TOVID_VERSION = 0.35
# I don't see how to automate downloads from a google drive http://goo.gl/o8IWR7
# The file which is downloaded has the expected name tovid-0.35.tar.gz
TOVID_SITE = http://tovid.wikia.com/wiki/Installing_tovid
TOVID_LICENSE = GPLv2.0
TOVID_LICENSE_FILES = COPYING

# Must be run in source directory to avoid "error: package directory 'libtovid' does not exist"
define TOVID_INSTALL_TARGET_CMDS
	bash -c "cd $(@D); ./setup.py install --root=$(TARGET_DIR) --prefix=/usr"
endef

$(eval $(generic-package))

             reply	other threads:[~2015-02-19  1:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19  1:55 Steve Kenton [this message]
2015-02-19 22:12 ` [Buildroot] How automate source download from a google drive? Bryce Schober
2015-02-19 22:55   ` Steve Kenton
2015-02-20  6:33   ` Baruch Siach

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=54E54294.3030702@ou.edu \
    --to=skenton@ou.edu \
    --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