All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14656] Adding dependencies from an external tree does not work
Date: Wed, 09 Mar 2022 20:14:16 +0000	[thread overview]
Message-ID: <bug-14656-163-rupLOBRfNE@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14656-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=14656

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |yann.morin.1998@free.fr
         Resolution|---                         |WONTFIX

--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Simon, All,

As I explained on the list [0], it is not possible to use a br2-external
tree to modify the dependencies of a package.


[0]
https://lore.kernel.org/buildroot/20220309201030.GA23050@scaer/T/#m4bacf3a6047b2da82554d088f2afd805bef5a312

There is for now no way to achieve what you need without directly modifying
the original package's .mk file.

(note: there have been a few ideas floated around in the past, but they are
far from trivial to apply, if at all.)

Regards,
Yann E. MORIN.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-03-09 20:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 10:22 [Buildroot] [Bug 14656] New: Adding dependencies from an external tree does not work bugzilla
2022-03-09 10:25 ` [Buildroot] [Bug 14656] " bugzilla
2022-03-09 20:14 ` bugzilla [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=bug-14656-163-rupLOBRfNE@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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.