From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] ushare: new package
Date: Wed, 21 Mar 2012 14:44:52 +0100 [thread overview]
Message-ID: <20120321144452.68029160@skate> (raw)
In-Reply-To: <5f0396764c1dc201f01ae3853a534d33@zacarias.com.ar>
Le Wed, 21 Mar 2012 10:39:35 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :
> > With GENTARGETS, xxx_BUILD_CMDS is empty by default. Are you sure
> > this
> > builds?
>
> Yes, install triggers build.
But still, build should be done in the xxx_BUILD_CMDS so that it works
like all other packages, IMO.
> > Also, can you add a comment just before USHARE_CONFIGURE_CMDS saying
> > that despite the appearance, autotools are not used. However, I am
> > sure
> > in the future many people will wonder why AUTOTARGETS was not used.
>
> Sure, but should it be for other packages as well?
Yes, I think we should mention explicitly why GENTARGETS is used even
though the package has a ./configure script.
> Same things applies to ffmpeg and probably others (the ushare configure
> is an old/strip version from ffmpeg).
> Though ffmpeg is using AUTOTARGETS and overriding CONFIGURE_CMDS...
And it is wrong. Not your fault, of course, but I don't think it is an
argument to make it wrong in other places as well.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-03-21 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 13:12 [Buildroot] [PATCH v2] ushare: new package Gustavo Zacarias
2012-03-21 13:21 ` Thomas Petazzoni
2012-03-21 13:39 ` Gustavo Zacarias
2012-03-21 13:44 ` Thomas Petazzoni [this message]
2012-03-21 14:15 ` Gustavo Zacarias
2012-03-21 22:02 ` Peter Korsgaard
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=20120321144452.68029160@skate \
--to=thomas.petazzoni@free-electrons.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