From: Thomas Claveirole <thomas.claveirole@green-communications.fr>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/openlayers: bump to version 7.0.0
Date: Thu, 01 Sep 2022 15:51:52 +0200 [thread overview]
Message-ID: <3453234.iIbC2pHGDl@harderbit> (raw)
In-Reply-To: <20220827093603.GT37358@scaer>
[-- Attachment #1.1: Type: text/plain, Size: 2377 bytes --]
> Ah, another case [0] of building sith host-nodejs, two data-points,
> better than one! :-) And see below [1]...
Yes, I actually work with Johan and he pointed these messages to me already.
We also plan to use host-nodejs for the vuejs and vuejs-router packages when
we find time for this...
... and, at this stage, I am thinking this would probably need a dedicated
architecture. Unfortunately I am not sure I know enough about Buildroot and
npm to do this (I know next to nothing about npm, actually...)
> > Note that the v6.14.1-dist.zip archive for the previous version did
> > change, hence the hash for previous version is broken. [...]
>
> So, for master: v6.14.1 is just a fix in the package-lock?json. Since
> we were not building the package, but were relying on the pre-build
> archive, we should not be imapcted by this change, right? In that case,
> we could just revert back to using v6.14.0, so that we can have a hash
> that is correct.
I did not look into the details. If package-lock.json is the only difference
between v6.14.0 and v6.14.1, then yes, I agree.
> [1] As I said in [0], it is weird to see that we need to install before
> we can build?
npm install does **not** actually install anything into the target file
system. If I understood correctly, it just downloads the dependencies
required to build the package, and installs them in ./node_modules, which is $
(@D)/node_modules in our cases.
This is according to npm -h:
npm <command>
Usage:
npm install install all the dependencies in your project
npm install <foo> add the <foo> dependency to your project
[...]
> Why build-legacy? a small note in the comit log to explain that would be
> nice.
The default build generates a lot of JavaScript modules that clients should
load independently (if I understood correctly) and this is not what we want
here. We want a single JavaScript file to process without using modules, that
will populate a global ol object ("namespace") with the library. The other
JavaScript packages that I know of in Buildroot (e.g., jquery, vuejs) work the
same.
I need to make a new revision of this patch anyway (I will try to do it as
soon as I can, sorry if I am a bit slow these days...) So I will add a note
when I do this.
Thanks for your remarks, cheers,
--
Thomas Claveirole <thomas.claveirole@green-communications.fr>
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-01 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 15:12 [Buildroot] [PATCH 1/1] package/openlayers: bump to version 7.0.0 Thomas Claveirole
2022-08-27 9:36 ` Yann E. MORIN
2022-09-01 13:51 ` Thomas Claveirole [this message]
2022-09-01 15:56 ` [Buildroot] [PATCH v2 1/1] package/openlayers: bump to version 7.1.0 Thomas Claveirole
2022-09-06 15:05 ` Yann E. MORIN
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=3453234.iIbC2pHGDl@harderbit \
--to=thomas.claveirole@green-communications.fr \
--cc=buildroot@buildroot.org \
--cc=yann.morin.1998@free.fr \
/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.