From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thierry Bultel <thierry.bultel@linatsea.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/3] fs/dracut: new fs type
Date: Sun, 19 Dec 2021 09:23:25 +0100 [thread overview]
Message-ID: <20211219082325.GB2603@scaer> (raw)
In-Reply-To: <7aa7dc74-284a-3c33-defa-aef4d6e11799@linatsea.fr>
Thierry, All,
On 2021-12-19 07:55 +0100, Thierry Bultel spake thusly:
> >>> You should also check then if it gets properly updated by
> >>>support/misc/relocate-sdk.sh (I think yes).
> >>I am sorry, but I do not see the point here, would you mind explain
> >>please ?
> >
> > If there's such a wrapper script that sets the environment variables
> >correctly, the idea is to be able to use that as part of the SDK. That
> >also means it must be possible to move it to a different place. Since it
> >contains hardcoded paths to HOST_DIR, these need to be change when the SDK
> >is relocated. The relocate-sdk.sh script should do that, but it's
> >important to check that indeed it does.
>
> I probably miss something here. Is it a bad idea to -not- use hardcoded
> paths in the wrapper script, but environment variables instead ?
> It should be something like:
>
> -------------
> #!/bin/bash
> set -e
>
> if [ -z "$*" ]; then
> echo "No argument supplied"
> exit
> fi
>
> DRACUT_LDD=${TARGET_CROSS}ldd \
> DRACUT_INSTALL="${HOST_DIR}/lib/dracut/dracut-install" \
> dracutbasedir=${HOST_DIR}/usr/lib/dracut \
> dracutsysrootdir=${TARGET_DIR} \
> ${HOST_DIR}/bin/dracut "$@"
> ----------
The thing is, with the SDK, those variables are not set.
- HOST_DIR can be easily derived; it is: $(dirname $(dirname "${0}"))
or a little be simpler: $(dirname "${0%/*}")
- TARGET_CROSS can probably be derived somehow, but not even sure...
- TAGET_DIR has to be specified explicitly.
So, I think for now it would be over-engineering to try and catter for
the SDK; this can be acted upon later...
Regards,
Yann E. MORIN.
> So that should not impact the relocation ...
>
> By the way, in cpio.mk, I also had to
>
> export TARGET_CROSS
>
>
> Regards
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-19 8:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 18:00 [Buildroot] [PATCH 1/3] package/cross-ldd: new package Thierry Bultel
2021-12-15 18:00 ` [Buildroot] [PATCH 2/3] package/dracut: new host package Thierry Bultel
2021-12-16 20:35 ` Arnout Vandecappelle
2021-12-15 18:00 ` [Buildroot] [PATCH 3/3] fs/dracut: new fs type Thierry Bultel
2021-12-16 20:49 ` Arnout Vandecappelle
2021-12-17 11:04 ` Thierry Bultel
2021-12-17 18:05 ` Arnout Vandecappelle
2021-12-17 21:50 ` Thierry Bultel
2021-12-18 13:22 ` Yann E. MORIN
2021-12-18 16:07 ` Thierry Bultel
2021-12-18 13:16 ` Yann E. MORIN
2021-12-19 6:55 ` Thierry Bultel
2021-12-19 8:23 ` Yann E. MORIN [this message]
2021-12-20 22:02 ` Arnout Vandecappelle
2021-12-20 22:10 ` Thierry Bultel
2021-12-16 20:31 ` [Buildroot] [PATCH 1/3] package/cross-ldd: new package Arnout Vandecappelle
2021-12-17 10:10 ` Thierry Bultel
2021-12-17 17:54 ` Arnout Vandecappelle
[not found] <20211215173411.274024-1-thierry.bultel@linatsea.fr>
2021-12-15 17:34 ` [Buildroot] [PATCH 3/3] fs/dracut: new fs type Thierry Bultel
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=20211219082325.GB2603@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=thierry.bultel@linatsea.fr \
--cc=thomas.petazzoni@bootlin.com \
/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.