HI,
I am trying to build a custom buildroot image for my Luckfox Pico Ultra W that includes Qt5.
I select the packages using ./build.sh buildrootconfig inside the provided SDK, I can see during the build that the Qt5 package is downloaded and extracted but everytime when I flash the output image on the Pico Ultra W, Qt5 does not seem to be installed. There are no reference to it inside the filesystem.
Is there something I'm missing in order to have my packages inside buildroot?
Buildroot image not including packages
Hello, after executing ./build.sh buildrootconfig and then executing ./build.sh rootfs may build the root file system with the latest configuration, you also need to execute ./build.sh firmware to package before burning the image to generate rootfs.img to add a new package,
An alternative method is to execute ./build.sh directly after modifying buildroot's defconfig
An alternative method is to execute ./build.sh directly after modifying buildroot's defconfig
I have ran the following:Crocodile wrote: ↑2025-03-31 2:24 Hello, after executing ./build.sh buildrootconfig and then executing ./build.sh rootfs may build the root file system with the latest configuration, you also need to execute ./build.sh firmware to package before burning the image to generate rootfs.img to add a new package,
An alternative method is to execute ./build.sh directly after modifying buildroot's defconfig
./build.sh buildrootconfig (Selected my packages and saved)
./build.sh
./build.sh firmware
I then flashed the the images found under luckfox-pico/output/image but to no avail. My selected packages are still not present on the board after flashing. When I go back to buildrootconfig I can see that my configuration is still present so I guess it's been saved properly? I have tried building the image on both WSL2 and a native Ubuntu-22.04 machine with the same results. Could a part of the ./build.sh script be overiding my configuration for buildroot?
When running ./build.sh firmware I have noticed some warnings coming from the script. Could that have something to do with my issues?Totally_Not_A_Virus wrote: ↑2025-03-31 3:41I have ran the following:Crocodile wrote: ↑2025-03-31 2:24 Hello, after executing ./build.sh buildrootconfig and then executing ./build.sh rootfs may build the root file system with the latest configuration, you also need to execute ./build.sh firmware to package before burning the image to generate rootfs.img to add a new package,
An alternative method is to execute ./build.sh directly after modifying buildroot's defconfig
./build.sh buildrootconfig (Selected my packages and saved)
./build.sh
./build.sh firmware
I then flashed the the images found under luckfox-pico/output/image but to no avail. My selected packages are still not present on the board after flashing. When I go back to buildrootconfig I can see that my configuration is still present so I guess it's been saved properly? I have tried building the image on both WSL2 and a native Ubuntu-22.04 machine with the same results. Could a part of the ./build.sh script be overiding my configuration for buildroot?
- Attachments
-
Please make sure that the package you have enabled has any libraries or binaries available, and check for files under ${SDK}/output/out/rootfs_uclibc_rv1106 before executing ./build.sh firmware
The warning content you provided has nothing to do with the package not being installed correctly and can be ignored
The warning content you provided has nothing to do with the package not being installed correctly and can be ignored
All packages I selected are available in the buildroot config after download the SDK. I can also see them under ${SDK}/output/out/rootfs_uclibc_rv1106/usr/lib (see attatchment)Crocodile wrote: ↑2025-04-01 3:04 Please make sure that the package you have enabled has any libraries or binaries available, and check for files under ${SDK}/output/out/rootfs_uclibc_rv1106 before executing ./build.sh firmware
The warning content you provided has nothing to do with the package not being installed correctly and can be ignored
But after flashing, they cannot be found in the same location on the board's filesystem
- Attachments
-
Last edited by Totally_Not_A_Virus on 2025-04-01 3:21, edited 1 time in total.
Please check whether the SDK version is the latest from the github repository.
In ${SDK}/output/out/rootfs_uclibc_rv1106, you can try to create a file in the root directory for identification, and then directly execute ./build.sh firmware and flash image, check whether the identification file appears in the root directory
In ${SDK}/output/out/rootfs_uclibc_rv1106, you can try to create a file in the root directory for identification, and then directly execute ./build.sh firmware and flash image, check whether the identification file appears in the root directory