[yocto] nodejs npm qemux86_64

Hi, I have installation problems for npm recipes. Using Yocto thud and machine=qemux86_64(wrlinux-x), but as I can see it this concerns all use of npm.bbclass for 64-bits system. The problem seems to be the use of ${libdir} in npm.bbclass, when 64 bit is used this expands to lib64. npm install

Re: [yocto] npm nodejs

s, > > Am 21.08.19 um 14:55 schrieb Jonas Andersson: > > I have used Yocto and npm/nodejs now for about 1 year and think it works > > but I not without some extra work. Are there any group working on > > npm/nodejs? As I use it quite frequent and puts some extra work every > &

[yocto] npm nodejs

Hi I have used Yocto and npm/nodejs now for about 1 year and think it works but I not without some extra work. Are there any group working on npm/nodejs? As I use it quite frequent and puts some extra work every time i create an recipe I have some interest in supporting the work on npm/nodejs to

Re: [yocto] [Yocto] RPI WiFi not loading module

the module added to /etc/modules-load.d/ but cant understand what service/script that is responsible for loading it. / Jonas Den fre 24 maj 2019 kl 02:03 skrev Khem Raj : > > > On 5/23/19 2:14 AM, Jonas Andersson wrote: > > Hi > > > > I have problem to get my WiFi workin

[yocto] [Yocto] RPI WiFi not loading module

Hi I have problem to get my WiFi working on boot on Raspberry Pi 3. The problem is that wlan0 interface not showing up, if I manually run modprobe brcmfmac it works. To try to "force" the load of brcmfmac i added it to KERNEL_MODULE_AUTOLOAD and that generated an file in /etc/modules-load.d/ ->

Re: [yocto] Best practice dynamic service file

Thanks for the tip, it is a bit sleeker than pulling in an python script. Den tis 5 mars 2019 kl 02:05 skrev ChenQi : > On 03/05/2019 05:46 AM, Jonas Andersson wrote: > > Hi, > > I have an systemd recipe to start an application as a service, i have > included an service file.

[yocto] Best practice dynamic service file

Hi, I have an systemd recipe to start an application as a service, i have included an service file. Now I am looking for an solution to be able to set settings in the service file from Yocto variables, i have found recipes that use python to build files during build. What is best practice for

Re: [yocto] npm recipe bad task order

v1] = "WTFPL" _ /Jonas Den tors 14 feb. 2019 kl 21:38 skrev Chuck Wolber : > Normally the source archive is unpacked first, which contains the license > file. Is there something different with the source pack

[yocto] npm recipe bad task order

Hi, I have some recipes created from npm packages with devtool. do_populate_lic with: WARNING: Could not copy license file and LIC_FILES_CHKSUM points to an invalid file. In my understanding the problem is that do_populate_lic task is running before do_compile: log.task_order

[yocto] do_populate_lic fail from scratch build but succed after clean

Hi I have an recipe based on serialport npm package created with devtool. I added some custom licenses in my layer with LICENSE_PATH: # Additional license directories. LICENSE_PATH += "${LAYERDIR}/files/common-licenses" After this I get some inconsistent build result (or i dont understand ).

[yocto] Add custom license to layer

Hi, I have an recipe created from npm with devtool, when i build it generates the warning: do_rootfs: The license listed Unlicense was not in the licenses collected for recipe my-recipe I have tried to include the license in my layer with "LICENSE_PATH", with no success. "Unlicense" is listed

Re: [yocto] Do rootfs fail when switch from rpm to deb

Thanks, I'll look into it. Den tis 11 dec. 2018 kl 11:55 skrev Burton, Ross : > On Tue, 11 Dec 2018 at 09:11, Jonas Andersson > wrote: > > The following packages have unmet dependencies: > > microservicebus-node : Depends: microservicebus-node-npm but it is not >

[yocto] Do rootfs fail when switch from rpm to deb

Hi We have an recipe based on microservicebus-node npm package created with devtool. When we build with PACKAGE_CLASSES = "package_rpm" it builds but when switching to package_deb do_rootfs fails. What can I do to get more information about the packages that is reported as broken, are there any