About nickH

nickH · ‎04-20-2022

Hello, First some information regarding your first question: How to get started with SDK? The SDK itself and a documentation on the SDK can be found on GitHub. As an App Build Environment you nee a Ubuntu 20.04 Linux operating system with a special set of software packages and certain settings. There are several alternatives for such an environment. I would recommend to use the App Build Environment which is integrated in ctrlX WORKS (since V 1.14). See this documentation on how to setup this development environment. After the fist boot you can run some install scripts which are part of the virtual environment to download an unzip the SDK or to download some additional packages for a specific programming language (see screenshot). After that you can connect from Visual Studio Code (locally installed on window host) to your to your App Build Environment with ssh and the use of the "Remot SSH" extension and the connection string (eg: ssh -p 10022 boschrexroth@127.0.0.1). Then I would recommend you to take a look at the existing samples in the SDK for the programming language you want to use. Some information about the python samples can be found here. Then you can follow the How to blog you mentioned. Best regards, Nick

nickH · ‎04-14-2022

It seems like mknod tries to add folders and files to a area that it cannot access. Please keep in mind that snaps by default run in thier sandbox. Interfaces allow access to a resource outside of a snap’s confinement. You can have a look at the system files interface. Please also have a look to this thread, someone ran into a similar problem.

nickH · ‎04-11-2022

Quick update on this issue: Alternatively, you can add the following three lines to snapcraft.yaml under "parts: client: build-packages". This will be adapted for future releases. - on arm64: - libsystemd-dev:arm64 - libzmq3-dev:arm64 See screenshot: snapcraft.yaml of datalayer.client

nickH · ‎04-11-2022

See the description on ctrlX Data Layer client and provider library for golang (and look at Prerequisites). Please install the packages you can find here in your Build VM: sudo apt-get install libsystemd-dev libsystemd-dev:arm64 libzmq3-dev libzmq3-dev:arm64 This should solve your problem, so you can also build snaps in go for arm64. Thank you for reporting this issue. We try to improve the setup and build process.

nickH · ‎04-08-2022

Hello, Just to show some basics about snaps I copied out an extract from the snapcraft.yaml of the hello.world sample from the SDK and added some comments: # define how apps & services are exposed to host system apps: HelloWorld: #name of your application (binary build) command: HelloWorld #this will be the command to run the service plugs: #plugs to connect to interfaces - network daemon: simple #declares that your application gets started by the system deamon passthrough: #restarts the application if it shuts down after 10 sec restart-condition: always restart-delay: 10s #describes how the binary application (from folder ./generated/build) gets packed (dumped) into the snap parts: helloworld: plugin: dump source: ./generated/build Please a look into the snpacraft.yaml reference. It describes all the details snapcraft needs to build a snap. @schwebo wrote: So i understand, is the a .snap file which is build, contains ALL Libs which are needed, that meand the lib from the dynanamic.linker are alos copies to the snap file !?!?!?! Yes, this is true. Snaps in general are self contained and therefor have to have all needed dependencies inside. I hope I could clarify some things. You can share your snapcraft.yaml (with some comments) so we can have a look at your snap build mechanism.

About nickH

Re: How to get started with SDK?

Re: App Cabapilities in SNAP Package

Re: cannot find -lzmq

Re: cannot find -lzmq

Re: SNAP how to use dynamic linker ldconfig or LD_LIBRARY_PATH