From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] board-specific autotools env customization
Date: Mon, 2 Feb 2015 17:54:55 +0100 [thread overview]
Message-ID: <20150202175455.5dd5c2e3@free-electrons.com> (raw)
In-Reply-To: <CAKAx1chT6Grx+oRMiQy5t29TUe=avo6v9CR2nP1GZ6Lf1-a-5A@mail.gmail.com>
Dear Lionel Orry,
On Mon, 2 Feb 2015 15:05:06 +0100, Lionel Orry wrote:
> I would like to use a specific XXX_CONF_ENV variable to send ac_cv_...
> variables to configure, but they are specific to my compiler. For my tests,
> I currently write the XXX_CONF_ENV directly into the package .mk file, but
> I would like to know if there is a better way. I already use the
> recommended board/<company>/<board>/patches/ infrastructure, but this is
> not a patch so I don't know where to put it...
>
> Any advice / best practice ?
Well, only pass this <pkg>_CONF_ENV if you're using your specific
compiler?
Maybe if you could be more specific and tell us which compiler / which
environment variable you need to pass, we could give more hints.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-02-02 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 14:05 [Buildroot] board-specific autotools env customization Lionel Orry
2015-02-02 16:54 ` Thomas Petazzoni [this message]
2015-02-02 17:19 ` Lionel Orry
2015-02-03 8:54 ` Arnout Vandecappelle
2015-02-04 7:52 ` Lionel Orry
2015-02-04 20:21 ` Arnout Vandecappelle
2015-02-06 9:31 ` Lionel Orry
2015-02-06 10:49 ` Arnout Vandecappelle
2015-02-06 14:51 ` Lionel Orry
2015-02-06 14:59 ` Thomas Petazzoni
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=20150202175455.5dd5c2e3@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.