All of lore.kernel.org
 help / color / mirror / Atom feed
From: manu f <e.fiancette@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] : How to add a path to environment variable ?
Date: Thu, 21 Jan 2021 18:02:39 +0100	[thread overview]
Message-ID: <CAGshWo2KMW3VvWSGeOvqqhvi3z-Onn_hdyA-4Yjb=YEKdUDuTw@mail.gmail.com> (raw)
In-Reply-To: <20210121174729.31850f5c@windsurf.home>

Thanks for your suggestion!
in the last buildroot version, nodejs is deprecated!
So I use my own compiled version of nodejs.

about etc/profile.d , I was just working on it, so its confirm this is the
good way.
But I was thinking there was a way to add natively the path ac buildroot
compilation time. sorry I am newby.

Regards


Le jeu. 21 janv. 2021 ? 17:47, Thomas Petazzoni <
thomas.petazzoni@bootlin.com> a ?crit :

> On Thu, 21 Jan 2021 16:32:56 +0100
> manu f <e.fiancette@gmail.com> wrote:
>
> > I create an overlay to install nodejs in usr/local/lib/nodejs
>
> Why don't you use the nodejs package that Buildroot has ?
>
> > and I need to add to the target environment varriable the path to the bin
> > contain directory.
> > How to do that ?
>
> Add an extra file in /etc/profile.d/ to expand the PATH as needed. You
> can use a root filesystem overlay to achieve this.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210121/c0968578/attachment.html>

  reply	other threads:[~2021-01-21 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 15:32 [Buildroot] : How to add a path to environment variable ? manu f
2021-01-21 16:47 ` Thomas Petazzoni
2021-01-21 17:02   ` manu f [this message]
2021-01-21 19:47     ` Thomas Petazzoni
2021-01-21 21:43       ` Yann E. MORIN
2021-01-22 10:47         ` Peter Korsgaard
2021-01-22 11:22           ` manu f
2021-01-22 15:35             ` Peter Korsgaard
2021-01-22 15:45               ` manu f

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='CAGshWo2KMW3VvWSGeOvqqhvi3z-Onn_hdyA-4Yjb=YEKdUDuTw@mail.gmail.com' \
    --to=e.fiancette@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 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.