--- title: Blog posts tagged "snapcraft" description: Canonical makes open source secure, reliable and easy to use, providing support for Ubuntu and a portfolio of enterprise-grade technologies. Founded in 2004, Canonical operates globally with team members in over 80 countries. url: https://canonical.com/blog/tag/snapcraft?format=md --- # Blog posts tagged "snapcraft" #### [TurtleBot3 OpenCR firmware update from a snap](https://canonical.com/blog/turtlebot3-opencr-firmware-update-from-a-snap) The TurtleBot3 robot is a standard platform robot in the ROS community, and it’s a reference that Canonical knows well, since we’ve used it in our tutorials. As a matter of fact, we use it to demonstrate some of our work, such as distributing a ROS stack through snaps. This robot embeds two boards, a --- IoT #### [Snapcraft 8.0 and the respectable end of core18](https://canonical.com/blog/snapcraft-8-0-and-the-respectable-end-of-core18) ‘E’s not pinin’! ‘E’s passed on! This base is no more! He has ceased to be! ‘E’s expired and gone to meet ‘is maker! ‘E’s a stiff! Bereft of life, ‘e rests in peace! If you hadn’t nailed ‘im to the perch ‘e’d be pushing up the daisies! ‘Is software processes are now ‘istory! ‘E’s --- Company #### [ROS architectures with snaps](https://canonical.com/blog/ros-architectures-with-snaps) Choosing the right architecture can be hard, but we want to help. In this blog, we’ll look at different architectures and their pros and cons. We’ll also show you how to apply the chosen architecture to a mobile robot software stack with three essential apps. With this blogpost, we will see the different ROS architectures --- Robotics #### [Optimise your ROS snap – Part 6](https://canonical.com/blog/optimise-your-ros-snap-part-6) Welcome to Part 6 of our “Optimise your ROS snap” blog series. Make sure to check Part 5. This sixth and final part will  summarise every optimisation that we did. We will provide a critique for every optimisation that we tried along this series of blogs. Finally, we have reached the last part of this --- Robotics #### [Optimise your ROS snap – Part 5](https://canonical.com/blog/optimise-your-ros-snap-part-5) Welcome to Part 5 of our “Optimise your ROS snap” blog series. Make sure to check Part 4. This fifth part is going to cover two different optimisations. The first one, covers the compression algorithm. The second one, is about implementing extremely risky but efficient file deletion. We are going to present two completely different --- Robotics #### [Optimise your ROS snap – Part 4](https://canonical.com/blog/optimise-your-ros-snap-part-4) Welcome to Part 4 of our “optimise your ROS snap” blog series. Make sure to check Part 3 before. This fourth part is going to explain what dynamic library caching is. We will present how to use it to optimise ROS snaps, along with the different points to be careful about. Finally, we will apply --- Robotics #### [Optimise your ROS snap – Part 3](https://canonical.com/blog/optimise-your-ros-snap-part-3) Welcome to Part 3 of our “optimise your ROS snap” blog series. Make sure to check Part 2. This third part is going to present safe optimisations consisting of removing duplicates and unnecessary files. We will present three different methods as well as their cumulative benefits for the performance of ROS snaps. When snaps are --- Robotics #### [Optimise your ROS snap – Part 2](https://canonical.com/blog/optimise-your-ros-snap-part-2) Welcome to Part 2 of the “optimise your ROS snap” blog series. Make sure to check Part 1 before reading this blog post. This second part is going to present initial optimisations already used in the Gazebo snap. We will present the benefit that they could bring to our ROS snaps as well as the --- Robotics #### [Optimise your ROS snap – Part 1](https://canonical.com/blog/optimise-your-ros-snap-part-1) Do you want to optimise the performance of your ROS snap? We reduced the size of the installed Gazebo snap by 95%! This is how you can do it for your snap. Welcome to Part 1 of the “optimise your ROS snap” blog series. This series of 6 blogs will show the tools and methodologies --- Robotics #### [Craft team welcomes you to another episode of its adventures](https://canonical.com/blog/craft-team-welcomes-you-to-another-episode-of-its-adventures) Welcome to the second article in the Craft team saga. Previously, on Craft Team, we gave you a brief introduction into the team’s function, we announced our desire to share the ins and outs of our day-to-day work with the community, and gave you an overview of roughly two weeks of coding and fun. Today, --- Company #### [Snapcrafters: 2022 wrap-up](https://canonical.com/blog/snapcrafters-2022-wrap-up) This article was written by Merlijn Sebrechts and Dani Llewellyn from the Snapcrafters community. ===== Last year, we officially re-launched the “Snapcrafters” initiative. We’re a community of volunteers who build and maintain unofficial snap packages. Although snaps make it easy for developers to publish their software directly to users, --- Community #### [The long ARM of KDE](https://canonical.com/blog/the-long-arm-of-kde) With over 100 applications available in the Snap Store, KDE is by far the biggest publisher of snaps around. What unifies this impressive portfolio is the fact that all of these snaps are made for the x86 platform. Not anymore. Now, don’t panic! The x86 snaps are not going anywhere. But ARM-supported KDE snaps are --- Desktop #### [How to build a snap using ROS 2 Humble](https://canonical.com/blog/how-to-build-a-snap-using-ros-2-humble) We’ve recently celebrated the release of ROS 2 Humble Hawksbill with a post detailing how to get started developing for the new release in containers. In addition, we shared an overview of the new features included with this new release, particularly its enhanced security features. This week we are tackling the logical next step in --- Robotics #### [The new classic confinement in snaps – Even the classics need a change](https://canonical.com/blog/the-new-classic-confinement-in-snaps-even-the-classics-need-a-change) As part of their fundamental, security-driven design, snaps are meant to run isolated from the underlying system. In most cases, the idea works well, and granular access to system resources using the mechanism of interfaces allows snap developers to ship their applications packaged with strict confinement. However, there are some scenario --- Company #### [Three ways to package your Electron apps as snaps](https://canonical.com/blog/three-ways-to-package-your-electron-apps-as-snaps) Software comes in many shapes and forms. One of the popular cross-platform, cross-architecture frameworks for building and distributing applications in Electron, which combines the Chromium rendering engine and the Node.js runtime. This makes Electron-based applications relatively easy to create. If you want to deploy Electron apps in Lin --- Company #### [How Snapcraft helps developers map out their application dependencies and efficiently build snaps](https://canonical.com/blog/how-snapcraft-helps-developers-map-out-their-application-dependencies-and-efficiently-build-snaps) One of the core concepts of snaps is cross-distro compatibility. Developers can build their snaps once, and they should run well on more than 40 different Linux distros. But how does one take care of all the required runtime dependencies? By providing them inside the snap, as part of the bundle. In the snap ecosystem, --- Company 1. *Previous page* 2. [1](https://canonical.com/blog/tag/snapcraft?format=md&page=1) 3. [2](https://canonical.com/blog/tag/snapcraft?format=md&page=2) 4. [3](https://canonical.com/blog/tag/snapcraft?format=md&page=3) 5. [4](https://canonical.com/blog/tag/snapcraft?format=md&page=4) 6. [5](https://canonical.com/blog/tag/snapcraft?format=md&page=5) 7. [*Next page*](https://canonical.com/blog/tag/snapcraft?format=md&page=2)