* Using a native tool from another recipe
@ 2019-05-13 13:06 Gabriele Zampieri
2019-05-13 15:59 ` Khem Raj
0 siblings, 1 reply; 5+ messages in thread
From: Gabriele Zampieri @ 2019-05-13 13:06 UTC (permalink / raw)
To: Yocto discussion list
[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]
Hi all,
I need to add a couple of tools to my build system (build2 and odb). The
second one depends on the first. Following a snippet of the build2 recipe:
--------------------------------------------------------------------------------------------
DEPENDS = "openssl-native"
SRC_URI = "https://download.build2.org/${PV}/build2-toolchain-${PV}.tar.gz"
SRC_URI[sha256sum] =
"42a254c46b59109b764afade0d50819b3d793a9167f46759fc6aa9d6d8a6ff37"
S = "${WORKDIR}/build2-toolchain-${PV}"
# build.sh located inside the tarball cannot be used to configure, compile
and
# install in different steps. This task is misleading, but I didn't find any
# other way to make it works
do_compile_prepend() {
./build.sh --timeout 600 --sudo false \
--make ${MAKE} ${PARALLEL_MAKE} \
--trust yes \
--install-dir ${prefix} g++
}
FILES_${PN}_append_class-nativesdk = " ${SDKPATHNATIVE}"
FILES_${PN} = "${D}${prefix}/*"
BBCLASSEXTEND = "native nativesdk"
--------------------------------------------------------------------------------------------
Then the odb-compiler recipe
--------------------------------------------------------------------------------------------
SECTION = "devtools"
DEPENDS = "build2-native"
CONFIG_NAME = "odb-gcc-X"
do_configure() {
cd ${B}
bpkg create -d ${CONFIG_NAME} cc \
config.cxx=g++ \
config.cc.coptions=-O3 \
config.bin.rpath=/usr/lib \
config.install.root=/usr \
config.install.sudo=false
}
BBCLASSEXTEND = "native nativesdk"
--------------------------------------------------------------------------------------------
When I try to build odb-compiler, bitbake complete the build2-native
recipe, but fails on do_configure due to 'bpkg command not found'.
Are my recipes correct?
Thanks,
Gabriele
[-- Attachment #2: Type: text/html, Size: 2605 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Using a native tool from another recipe
2019-05-13 13:06 Using a native tool from another recipe Gabriele Zampieri
@ 2019-05-13 15:59 ` Khem Raj
2019-05-14 6:17 ` Gabriele Zampieri
0 siblings, 1 reply; 5+ messages in thread
From: Khem Raj @ 2019-05-13 15:59 UTC (permalink / raw)
To: Gabriele Zampieri; +Cc: Yocto discussion list
[-- Attachment #1: Type: text/plain, Size: 2396 bytes --]
You need to either build bpkg as a native recipe or install and make it
available as a hosttool from build machine distribution itself
On Mon, May 13, 2019 at 6:07 AM Gabriele Zampieri <gabbla.malist@gmail.com>
wrote:
> Hi all,
>
> I need to add a couple of tools to my build system (build2 and odb). The
> second one depends on the first. Following a snippet of the build2 recipe:
>
> --------------------------------------------------------------------------------------------
> DEPENDS = "openssl-native"
> SRC_URI = "https://download.build2.org/${PV}/build2-toolchain-${PV}.tar.gz
> "
> SRC_URI[sha256sum] =
> "42a254c46b59109b764afade0d50819b3d793a9167f46759fc6aa9d6d8a6ff37"
>
> S = "${WORKDIR}/build2-toolchain-${PV}"
>
> # build.sh located inside the tarball cannot be used to configure, compile
> and
> # install in different steps. This task is misleading, but I didn't find
> any
> # other way to make it works
> do_compile_prepend() {
> ./build.sh --timeout 600 --sudo false \
> --make ${MAKE} ${PARALLEL_MAKE} \
> --trust yes \
> --install-dir ${prefix} g++
> }
>
> FILES_${PN}_append_class-nativesdk = " ${SDKPATHNATIVE}"
> FILES_${PN} = "${D}${prefix}/*"
>
> BBCLASSEXTEND = "native nativesdk"
>
> --------------------------------------------------------------------------------------------
>
> Then the odb-compiler recipe
>
>
> --------------------------------------------------------------------------------------------
> SECTION = "devtools"
> DEPENDS = "build2-native"
> CONFIG_NAME = "odb-gcc-X"
> do_configure() {
> cd ${B}
> bpkg create -d ${CONFIG_NAME} cc \
> config.cxx=g++ \
> config.cc.coptions=-O3 \
> config.bin.rpath=/usr/lib \
> config.install.root=/usr \
> config.install.sudo=false
>
> }
> BBCLASSEXTEND = "native nativesdk"
>
> --------------------------------------------------------------------------------------------
>
> When I try to build odb-compiler, bitbake complete the build2-native
> recipe, but fails on do_configure due to 'bpkg command not found'.
>
> Are my recipes correct?
>
> Thanks,
> Gabriele
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
[-- Attachment #2: Type: text/html, Size: 3548 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Using a native tool from another recipe
2019-05-13 15:59 ` Khem Raj
@ 2019-05-14 6:17 ` Gabriele Zampieri
2019-05-20 21:55 ` Khem Raj
0 siblings, 1 reply; 5+ messages in thread
From: Gabriele Zampieri @ 2019-05-14 6:17 UTC (permalink / raw)
To: Khem Raj; +Cc: Yocto discussion list
[-- Attachment #1: Type: text/plain, Size: 2775 bytes --]
Hi Khem,
what do you mean with "build bpkg as a native recipe"? I though that the
DEPENDS = "build2-native" will achieve this task. Thanks to pointing out
the hosttool option.
Best regards,
Gabriele
Il giorno lun 13 mag 2019 alle ore 17:59 Khem Raj <raj.khem@gmail.com> ha
scritto:
> You need to either build bpkg as a native recipe or install and make it
> available as a hosttool from build machine distribution itself
>
> On Mon, May 13, 2019 at 6:07 AM Gabriele Zampieri <gabbla.malist@gmail.com>
> wrote:
>
>> Hi all,
>>
>> I need to add a couple of tools to my build system (build2 and odb). The
>> second one depends on the first. Following a snippet of the build2 recipe:
>>
>> --------------------------------------------------------------------------------------------
>> DEPENDS = "openssl-native"
>> SRC_URI = "
>> https://download.build2.org/${PV}/build2-toolchain-${PV}.tar.gz"
>> SRC_URI[sha256sum] =
>> "42a254c46b59109b764afade0d50819b3d793a9167f46759fc6aa9d6d8a6ff37"
>>
>> S = "${WORKDIR}/build2-toolchain-${PV}"
>>
>> # build.sh located inside the tarball cannot be used to configure,
>> compile and
>> # install in different steps. This task is misleading, but I didn't find
>> any
>> # other way to make it works
>> do_compile_prepend() {
>> ./build.sh --timeout 600 --sudo false \
>> --make ${MAKE} ${PARALLEL_MAKE} \
>> --trust yes \
>> --install-dir ${prefix} g++
>> }
>>
>> FILES_${PN}_append_class-nativesdk = " ${SDKPATHNATIVE}"
>> FILES_${PN} = "${D}${prefix}/*"
>>
>> BBCLASSEXTEND = "native nativesdk"
>>
>> --------------------------------------------------------------------------------------------
>>
>> Then the odb-compiler recipe
>>
>>
>> --------------------------------------------------------------------------------------------
>> SECTION = "devtools"
>> DEPENDS = "build2-native"
>> CONFIG_NAME = "odb-gcc-X"
>> do_configure() {
>> cd ${B}
>> bpkg create -d ${CONFIG_NAME} cc \
>> config.cxx=g++ \
>> config.cc.coptions=-O3 \
>> config.bin.rpath=/usr/lib \
>> config.install.root=/usr \
>> config.install.sudo=false
>>
>> }
>> BBCLASSEXTEND = "native nativesdk"
>>
>> --------------------------------------------------------------------------------------------
>>
>> When I try to build odb-compiler, bitbake complete the build2-native
>> recipe, but fails on do_configure due to 'bpkg command not found'.
>>
>> Are my recipes correct?
>>
>> Thanks,
>> Gabriele
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
[-- Attachment #2: Type: text/html, Size: 4240 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Using a native tool from another recipe
2019-05-14 6:17 ` Gabriele Zampieri
@ 2019-05-20 21:55 ` Khem Raj
2019-05-21 6:16 ` Gabriele Zampieri
0 siblings, 1 reply; 5+ messages in thread
From: Khem Raj @ 2019-05-20 21:55 UTC (permalink / raw)
To: Gabriele Zampieri; +Cc: Yocto discussion list
On Mon, May 13, 2019 at 11:17 PM Gabriele Zampieri
<gabbla.malist@gmail.com> wrote:
>
> Hi Khem,
>
> what do you mean with "build bpkg as a native recipe"? I though that the DEPENDS = "build2-native" will achieve this task. Thanks to pointing out the hosttool option.
yes DEPENDS = "build2-native" should have added the needed tool to build.
>
> Best regards,
> Gabriele
>
> Il giorno lun 13 mag 2019 alle ore 17:59 Khem Raj <raj.khem@gmail.com> ha scritto:
>>
>> You need to either build bpkg as a native recipe or install and make it available as a hosttool from build machine distribution itself
>>
>> On Mon, May 13, 2019 at 6:07 AM Gabriele Zampieri <gabbla.malist@gmail.com> wrote:
>>>
>>> Hi all,
>>>
>>> I need to add a couple of tools to my build system (build2 and odb). The second one depends on the first. Following a snippet of the build2 recipe:
>>> --------------------------------------------------------------------------------------------
>>> DEPENDS = "openssl-native"
>>> SRC_URI = "https://download.build2.org/${PV}/build2-toolchain-${PV}.tar.gz"
>>> SRC_URI[sha256sum] = "42a254c46b59109b764afade0d50819b3d793a9167f46759fc6aa9d6d8a6ff37"
>>>
>>> S = "${WORKDIR}/build2-toolchain-${PV}"
>>>
>>> # build.sh located inside the tarball cannot be used to configure, compile and
>>> # install in different steps. This task is misleading, but I didn't find any
>>> # other way to make it works
>>> do_compile_prepend() {
>>> ./build.sh --timeout 600 --sudo false \
>>> --make ${MAKE} ${PARALLEL_MAKE} \
>>> --trust yes \
>>> --install-dir ${prefix} g++
>>> }
>>>
>>> FILES_${PN}_append_class-nativesdk = " ${SDKPATHNATIVE}"
>>> FILES_${PN} = "${D}${prefix}/*"
>>>
>>> BBCLASSEXTEND = "native nativesdk"
>>> --------------------------------------------------------------------------------------------
>>>
>>> Then the odb-compiler recipe
>>>
>>> --------------------------------------------------------------------------------------------
>>> SECTION = "devtools"
>>> DEPENDS = "build2-native"
>>> CONFIG_NAME = "odb-gcc-X"
>>> do_configure() {
>>> cd ${B}
>>> bpkg create -d ${CONFIG_NAME} cc \
>>> config.cxx=g++ \
>>> config.cc.coptions=-O3 \
>>> config.bin.rpath=/usr/lib \
>>> config.install.root=/usr \
>>> config.install.sudo=false
>>>
>>> }
>>> BBCLASSEXTEND = "native nativesdk"
>>> --------------------------------------------------------------------------------------------
>>>
>>> When I try to build odb-compiler, bitbake complete the build2-native recipe, but fails on do_configure due to 'bpkg command not found'.
>>>
>>> Are my recipes correct?
>>>
>>> Thanks,
>>> Gabriele
>>>
>>> --
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Using a native tool from another recipe
2019-05-20 21:55 ` Khem Raj
@ 2019-05-21 6:16 ` Gabriele Zampieri
0 siblings, 0 replies; 5+ messages in thread
From: Gabriele Zampieri @ 2019-05-21 6:16 UTC (permalink / raw)
To: Khem Raj; +Cc: Yocto discussion list
[-- Attachment #1: Type: text/plain, Size: 3387 bytes --]
I found the problem, I was installing the package in the wrong location, so
it wasn't shown in the output SDK.
Thanks,
Gabriele
Il giorno lun 20 mag 2019 alle ore 23:55 Khem Raj <raj.khem@gmail.com> ha
scritto:
> On Mon, May 13, 2019 at 11:17 PM Gabriele Zampieri
> <gabbla.malist@gmail.com> wrote:
> >
> > Hi Khem,
> >
> > what do you mean with "build bpkg as a native recipe"? I though that the
> DEPENDS = "build2-native" will achieve this task. Thanks to pointing out
> the hosttool option.
>
> yes DEPENDS = "build2-native" should have added the needed tool to build.
>
> >
> > Best regards,
> > Gabriele
> >
> > Il giorno lun 13 mag 2019 alle ore 17:59 Khem Raj <raj.khem@gmail.com>
> ha scritto:
> >>
> >> You need to either build bpkg as a native recipe or install and make it
> available as a hosttool from build machine distribution itself
> >>
> >> On Mon, May 13, 2019 at 6:07 AM Gabriele Zampieri <
> gabbla.malist@gmail.com> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I need to add a couple of tools to my build system (build2 and odb).
> The second one depends on the first. Following a snippet of the build2
> recipe:
> >>>
> --------------------------------------------------------------------------------------------
> >>> DEPENDS = "openssl-native"
> >>> SRC_URI = "
> https://download.build2.org/${PV}/build2-toolchain-${PV}.tar.gz"
> >>> SRC_URI[sha256sum] =
> "42a254c46b59109b764afade0d50819b3d793a9167f46759fc6aa9d6d8a6ff37"
> >>>
> >>> S = "${WORKDIR}/build2-toolchain-${PV}"
> >>>
> >>> # build.sh located inside the tarball cannot be used to configure,
> compile and
> >>> # install in different steps. This task is misleading, but I didn't
> find any
> >>> # other way to make it works
> >>> do_compile_prepend() {
> >>> ./build.sh --timeout 600 --sudo false \
> >>> --make ${MAKE} ${PARALLEL_MAKE} \
> >>> --trust yes \
> >>> --install-dir ${prefix} g++
> >>> }
> >>>
> >>> FILES_${PN}_append_class-nativesdk = " ${SDKPATHNATIVE}"
> >>> FILES_${PN} = "${D}${prefix}/*"
> >>>
> >>> BBCLASSEXTEND = "native nativesdk"
> >>>
> --------------------------------------------------------------------------------------------
> >>>
> >>> Then the odb-compiler recipe
> >>>
> >>>
> --------------------------------------------------------------------------------------------
> >>> SECTION = "devtools"
> >>> DEPENDS = "build2-native"
> >>> CONFIG_NAME = "odb-gcc-X"
> >>> do_configure() {
> >>> cd ${B}
> >>> bpkg create -d ${CONFIG_NAME} cc \
> >>> config.cxx=g++ \
> >>> config.cc.coptions=-O3 \
> >>> config.bin.rpath=/usr/lib \
> >>> config.install.root=/usr \
> >>> config.install.sudo=false
> >>>
> >>> }
> >>> BBCLASSEXTEND = "native nativesdk"
> >>>
> --------------------------------------------------------------------------------------------
> >>>
> >>> When I try to build odb-compiler, bitbake complete the build2-native
> recipe, but fails on do_configure due to 'bpkg command not found'.
> >>>
> >>> Are my recipes correct?
> >>>
> >>> Thanks,
> >>> Gabriele
> >>>
> >>> --
> >>> _______________________________________________
> >>> yocto mailing list
> >>> yocto@yoctoproject.org
> >>> https://lists.yoctoproject.org/listinfo/yocto
>
[-- Attachment #2: Type: text/html, Size: 5063 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-05-21 6:16 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-13 13:06 Using a native tool from another recipe Gabriele Zampieri
2019-05-13 15:59 ` Khem Raj
2019-05-14 6:17 ` Gabriele Zampieri
2019-05-20 21:55 ` Khem Raj
2019-05-21 6:16 ` Gabriele Zampieri
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.