Hi, Thanks for your information ,I will have a try. Best Regards
Peter Chen Making Innovation Easy LeMaker Team -- The Professional Makers for Hardware and Software Customization. Address: B1002, SIAT campus, Shenzhen University Town, Shenzhen, China Post Code: 518055 Tel: 0755-36330749 Email: [email protected] (Technical Support) [email protected] (Product Distribution) http://www.lemaker.org/ From: Oliver Grawert Date: 2016-05-31 17:51 To: snapcraft Subject: Re: snappy: Command not found Am Dienstag, den 31.05.2016, 16:33 +0800 schrieb [email protected]: > Hi, All > I want to port the snappy ubuntu to the LeMaker Gutiar refer to the > project at https://github.com/xapp-le/SnappyUbuntuCore . > I have read the README from the project ,and pre-installed some > software which it mentioned on the ubuntu 16.04. However, > It failed when i run the command "make gadget", and output error info > "snappy: Command not found" . How do i install the snappy command on > the ubuntu 16.04 ? looking at your tree, there is a lot more you need to change: in the 16 series the package.yaml files are gone (and replaced by snap.yaml files with a slightly different syntax). snappy can not build any snap packages anymore (it turned into a management-only tool). for building you need to use snapcraft on a 16.04 install (can be a chroot) now ... (the direct equivalent of "snappy build" would be "snapcraft snap", specifically for the kernel you probably want to use a full snapcraft build process using the snapcraft kernel plugin though) looking at your yaml files within the kernel and gadget dirs, snappy-ab is also gone. everything is a snap now (which essentially means: a squashfs file) and all these snaps live on a single writable partition and get loop mounted on demand (this includes kernel and os snap), this made the A/B partitioning setup obsolete (make sure to use the latest ubuntu-device-flash binary from [1], it creates the right partitioning by default). at [2] you can find the code for the currently used raspberry pi2 gadget snap, it shouldnt be to hard to adapt the meta data of your gadget according to the snap.yaml there. note that some things changed, specifically for u-boot. we stopped using/supporting any txt files to manage the auto-reboot and upgrade management, all config needs to live in a uboot.env binary blob now. there is a README in the above tree that explains how to create it, as well as the uboot.env.in file that we use as input for this. a few build config changes are also required to make the uboot.env blob work, the patch we use on top of the upstream u-boot tree can be found at [3]. regarding the kernel, there is a snapcraft example for building a 96boards kernel at [4], that should get you going... i guess the above should help you to start moving forward in the right direction, don't hold back on the further questions you will surely have, just drop them here ;) ciao oli [1] http://people.canonical.com/~mvo/all-snaps/ [2] http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-systems/files/head:/pi2/ [3] http://paste.ubuntu.com/16199863/ [4] https://github.com/ubuntu-core/snapcraft/tree/master/demos/96boards-kernel -- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
-- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
