Torizon IDE Extension - Add a template for custom package (subsystem update)

Technical Support
, , , , ,
1

Torizon IDE Extension helps creating projects from templates.
Basically two kind of templates exist at the moment:

Torizon platform has another concept of subsystem updates that can handle custom packages.
And so I suggest adding a new template “Custom package project” to be able to push custom packages to Torizon Cloud so that they can be used for subsystem updates.

2

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Hello,

Thank you for your insightful suggestion regarding the Torizon IDE Extension. Currently, the Torizon platform supports subsystem updates through Torizon Cloud, which includes managing and deploying custom packages. While the IDE Extension provides templates for applications and Torizon OS, your idea of adding a “Custom Package Project” template could indeed enhance the process.

This addition would streamline the creation and deployment of custom packages, making it more accessible for developers who prefer a GUI-driven approach. It could also help maintain consistency and reduce errors during package management.

Although this feature is not available at the moment, your feedback is valuable and could be considered for future updates to the Torizon IDE Extension. In the meantime, you can continue to use the existing tools and processes to manage your custom packages effectively.

Thank you once again for your suggestion.

Best regards, Toradex AI Assistant.

Please, also check if these links can help you solve your problem:

Subsystem Updates Overview | Toradex Developer Center.

3

Greetings @vix,

Sure I can pass this feedback on to our IDE extensions team. Is there anything special you’d want with regards to this template, or you just want something more or less the same as the OSTree/docker-compose related templates, but for generic custom packages?

Best Regards,
Jeremias

4

As far as I can see at the moment, I would be satisfied with a simple template for a generic custom package.
For sure no debug is needed, but only tasks to push this package to torizon cloud.
And an action handler template too.
I haven’t tested it, but looking here I think that two different templates could be helpful:

  • a simple package that is a bundle of some files and a handler script (like qtimagedisplay
  • a package that is a docker container that does something (like node-mcu. In this case taks to build the docker container are needed too

Or, maybe, the TCB template could be extended adding two more tasks:

  • push docker-compose to cloud (canonicalized)
  • push generic package(s) to cloud

I’m open to other proposals and reviews of this idea

5

Understood, well I passed your request onto the team internally. I saw from your other post you experimented with creating a custom task to push custom packages already.

Best Regards,
Jeremias

6

Yes, at the moment I use a single TCB template with the toradex tastk to publish Torizon/OS.
I included in this project everyhing (the docker-compose and the packages too) and I added my own tasks to publish the packages to torizon cloud (publishing docker-compose canonicalized not done yet).

Not sure if this is the best approach.

7

Not sure if this is the best approach.

Well I wouldn’t really say there’s a one best approach. These things can depend on use-case case and sometimes just user preference. The most important factor of course is whether it works for your workflow or not.

Best Regards,
Jeremias