Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 1/2] meson: add per package optional compiler/linker flags
Date: Sat, 22 Jun 2019 21:22:27 +0200	[thread overview]
Message-ID: <20190622192227.GF13664@scaer> (raw)
In-Reply-To: <20190622211330.10b68b47@windsurf>

Thomas, All,

On 2019-06-22 21:13 +0200, Thomas Petazzoni spake thusly:
> On Wed, 12 Jun 2019 18:37:10 +0200
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> 
> > > diff --git a/package/meson/meson.mk b/package/meson/meson.mk
> > > index 49e27f5527..70128f6bad 100644
> > > --- a/package/meson/meson.mk
> > > +++ b/package/meson/meson.mk
> > > @@ -60,6 +60,9 @@ define HOST_MESON_INSTALL_CROSS_CONF
> > >  	    -e "s%@TARGET_CFLAGS@%$(HOST_MESON_SED_CFLAGS)%g" \
> > >  	    -e "s%@TARGET_LDFLAGS@%$(HOST_MESON_SED_LDFLAGS)%g" \
> > >  	    -e "s%@TARGET_CXXFLAGS@%$(HOST_MESON_SED_CXXFLAGS)%g" \
> > > +	    -e "s%@PKG_TARGET_CFLAGS@%%g" \
> > > +	    -e "s%@PKG_TARGET_LDFLAGS@%%g" \
> > > +	    -e "s%@PKG_TARGET_CXXFLAGS@%%g" \  
> > 
> > Actually, if someone wants to use that file outside of Buildroot, and
> > also happend to need to pass special C/LD/CXXFLAGS for their package,
> > how are they expected to do so? Can't we just install it as a template
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > too?
    ^^^^
> 
> If we keep @PKG_TARGET_CFLAGS@, @PKG_TARGET_LDFLAGS@, etc. in the
> cross-compilation.conf, then it is no longer usable as-is: users will
> _have_ to fixup those @PKG_TARGET_foo@, even if they don't need to pass
> additional CFLAGS to their package.
> 
> I think what Peter S. did here is the best we can do. A better solution
> would be for Meson to support command line provided cflags/ldflags, but
> that's not supported, and if it was supported, this whole patch
> wouldn't be necessary.

As I explained on IRC: we would install the file like Peter does, but
also install the template as well, so that:

  - packages that don't need extra flags can be built as-is

  - while for packages that do require extra flag, the user can use the
    template to generate a custom file

and thus we have the best of both worlds.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2019-06-22 19:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 20:53 [Buildroot] [PATCH v6 1/2] meson: add per package optional compiler/linker flags Peter Seiderer
2019-04-23 20:53 ` [Buildroot] [PATCH v6 2/2] libdrm: change to meson build system Peter Seiderer
2019-06-22 20:29   ` Yann E. MORIN
2019-06-25 20:02     ` Peter Seiderer
2019-06-12 16:37 ` [Buildroot] [PATCH v6 1/2] meson: add per package optional compiler/linker flags Yann E. MORIN
2019-06-18 15:02   ` Adam Duskett
2019-06-22 19:13   ` Thomas Petazzoni
2019-06-22 19:22     ` Yann E. MORIN [this message]

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=20190622192227.GF13664@scaer \
    --to=yann.morin.1998@free.fr \
    --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