Hi,

So I've been continuing my investigation, it seems that the problem in the
end is that node_modules from UNPACKDIR doesn't make it to S.

I've tried different method but :

S = "${WORKDIR}/npm"
UNPACKDIR = "${S}"

doesn't make it, when doing that, a repo npm/ is created, containing
nodes_module (yeah!) but another repo npm/ is created inside it, so the
problem stays the same...

npm/npm/ contains all the sources
npm/node_modules/ contains all the deps.

I've seen that behavior in other packages too, do you have any idea what
could be hapenning?

I've made a very dirty fix, that copies UNPACKDIR to S, I'd like to get rid
of it as soon as possible.

Any hints about what could be wrong? Anyone saw that already?

Bests,

Yann CARDAILLAC,


On Thu, Aug 8, 2024 at 5:12 PM Yann CARDAILLAC via lists.yoctoproject.org
<ycnakajsph=gmail....@lists.yoctoproject.org> wrote:

> Hi yall,
>
> I'm upgrading nodejs apps and dependencies to scarthgap.
>
> I've been using the devtool way to build the dependencies packages, it's
> working great when it's in the workspace generated by devtool, however as
> soon as I move the package to my meta, then it doesn't work any more, it
> seems that the dependencies of the package are not downloaded anymore.
>
> It looks like a lot to this very old issue :
> https://yocto.yoctoproject.narkive.com/UmzCI675/and-npm-issue
> <https://yocto.yoctoproject.narkive.com/UmzCI675/and-npm-issues>
>
> For instance, if we take the cors package, I can create the recipe like so
> :
>
> *devtool add "npm://registry.npmjs.org/;package=cors;version=2.8.5
> <http://registry.npmjs.org/;package=cors;version=2.8.5>"*
>
> so far so good, I can build the package by doing either:
>
> *bitbake cors*
> or
> *devtool build cors*
>
> both works perfectly. Now if I move the recipe either manually or with:
>
> *devtool finish cors*
>
> I will receive errors like :
>
> *ERROR: cors-2.8.5-r0 do_populate_lic: QA Issue: cors: LIC_FILES_CHKSUM
> points to an invalid file:
> yocto/build/tmp/work/cortexa53-crypto-poky-linux/cors/2.8.5/npm/node_modules/object-assign/license
> [license-checksum]*
>
> When I look into the build directory the node_modules directory doesn't
> even exist.
>
> When comparing the build directories between both methods I can see that
> the one created by devtool looks way more complete than the one made by my
> layer (even though it's strictly the same recipe).
>
> Here's the one from devtool :
>
> $ ls build/tmp/work/cortexa53-crypto-poky-linux/cors/2.8.5/
> deploy-source-date-epoch  npm-cache     packages-split       pseudo
>           sources-unpack
> image                     npm-package   pkgdata
>  recipe-sysroot         spdx
> license-destdir           npm-registry  pkgdata-pdata-input
>  recipe-sysroot-native  sysroot-destdir
> npm-build                 package       pkgdata-sysroot
>  source-date-epoch      temp
>
> Here's the one from my layer:
> $ ls build/tmp/work/cortexa53-crypto-poky-linux/cors/2.8.5/
> deploy-source-date-epoch  npm             recipe-sysroot-native
>  sources-unpack  temp
> license-destdir           recipe-sysroot  source-date-epoch      spdx
>
> It's possibly because we stopped at the job do_populate_lic but I don't
> think it would happen that early in the build process but I might be wrong.
>
> I might be doing something wrong or there might be a bug I don't know...
>
> Best regards,
>
> Yann CARDAILLAC,
>
> --------------------------------------------------------------------------------------------------------------------
>
>
> 
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63681): https://lists.yoctoproject.org/g/yocto/message/63681
Mute This Topic: https://lists.yoctoproject.org/mt/107791492/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to