> On Jun 21, 2016, at 9:08 AM, Kucharczyk, Bartlomiej (Nokia - PL/Wroclaw) > <bartlomiej.kucharc...@nokia.com> wrote: > > Hello! > > I have encountered the following issue when trying to add Bash to the SDK > (meta-toolchain). > After SDK is installed, bash is not accessible in PATH.
Are you needing bash on sdkhost or on the target. If you need it on sdkhost you
have to include nativesdk-bash
into your image. From what you explain it seems you are adding bash to image,
which will add bash and its level
headers and libs to SDK target sysroot, meaning you can develop your
applications in cross environment and these
apps can use the libs and headers of bash.
>
> _Why_
> The bash binary is installed in ${base_bindir}, which is not part of PATH
> variable in SDK environment script.
>
> _Possible solution_
> I can try to send a patch for this, but would like to clarify first if that
> is a good way. Please give some thoughts.
>
> Basically my solution is to adjust "meta/recipes-extended/bash/bash.inc", and
> merge do_install_append (where /usr/bin/bash is moved to /bin/bash) into
> do_install_append_class-target. Additionally ALTERNATIVE_* variables must be
> adjusted, due to:
> WARNING: bash: NOT adding alternative provide
>
> With regards,
> Bartek
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
