Building a custom app into Legato

Legato Application Framework
1

Hi, Currently I upload my application to the WP76xx via app update custom.app.wp76xx.update 192.168.2.2

Now I want include my application into Legato and build it all together as a single legato.cwe.
I’ve created a folder in LegatoAF/Apps/ with all the files copied over from my custom application e.g. customapp.sdef, apps, components and interfaces. and also modified default.sdef to include $LEGATO_ROOT/apps/customapp.sdef but make build wp76xx fail.

Is there something I’m missing with including my application to Legato?
Do I need to make my own cmake and makefile for the application as well?

2

you can see here to modify wifi.sdef:

3

I made a mistake in the original post and got mixed up with defining what I have, it is a custom system and not a custom app.
So what I really want to do is to include my custom system into the legato and NOT an application.

Would modifying wifi.sdef to include customsystem.sdef work?

4

Then why don’t you copy the content of your custom sdef to wifi.sdef?

5

I put the custom system folder into /modules/wifi and replaced the contents of wifi.sdef with customsystem.sdef, and modified the paths in the .sdef

This got my system to build. :smile:

Why does it build when wifi.sdef it is used but not customsystem.sdef?
Are there any other methods (aside from using .update) of embedding my system into legato without having to renaming it to wifi.sdef?

6

I don’t know, not sure if you can modify default.sdef, you can give a try

7

My workaround to not use wifi module is to modify the makefile and kconfig in LegatoAF.

In makefile and kconfig, add an instance of your ‘custom system’ at every location where wifi is called.

It’s not the best solution but it works for me. It seems like WiFi module is added to .config.wp76xx (the config file to assisting building) then overwritten by the custom system.

To answer a previous question I asked, Makefile and Kconfig do not need to be present in the custom system.