From: Ismael Luceno <ismael.luceno@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/1] vlc: New package
Date: Mon, 12 Mar 2012 17:15:15 -0200 [thread overview]
Message-ID: <20120312171515.3eadccce@gmail.com> (raw)
In-Reply-To: <201203111408.28171.arnout@mind.be>
On Sun, 11 Mar 2012 14:08:27 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
<...>
> Is armv7-a the only architecture with Neon support?
Good question... also, I think nVidia ones don't have :/.
> More generally, maybe we should have an architecture symbol for neon
> on which this type of package can rely.
+1
<...>
> Why do the normal configure commands not work?
>
> The revision.txt could be done in POST_PATCH_HOOKS.
>
> The bootstrap can be done in PRE_CONFIGURE_HOOKS. However, isn't vlc
> distributed with a configure script? So the bootstrap will never be
> executed, right?
It's for scm versions, which I use from time to time. It doesn't hurt
to have, that's why I left it.
<...>
> The configure arguments can be added to VLC_CONF_OPTS.
>
> The vasprintf can be done in POST_CONFIGURE_HOOKS.
>
> For all of these, there should be a comment explaining why it is
> needed. This will help later for version bumpers to remove it again,
> when it is no longer needed because of upstream updates.
Thanks for the comments! :D. I'll submit another version soon.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120312/dc82713e/attachment.asc>
next prev parent reply other threads:[~2012-03-12 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 4:50 [Buildroot] [PATCHv2 0/1] vlc: New package Ismael Luceno
2012-03-05 4:50 ` [Buildroot] [PATCHv2 1/1] " Ismael Luceno
2012-03-11 13:08 ` Arnout Vandecappelle
2012-03-12 19:15 ` Ismael Luceno [this message]
2012-03-13 22:45 ` Arnout Vandecappelle
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=20120312171515.3eadccce@gmail.com \
--to=ismael.luceno@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