-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LFC federated RIOT fixes #192
Conversation
But invoking CMake correctly to generate two binaries and a shell script in `bin` is not working
@@ -0,0 +1,3 @@ | |||
#!/bin/bash | |||
REMOTE_ADDRESS=fe80::8cc3:33ff:febb:1b3 make all -C ./sender | |||
REMOTE_ADDRESS=fe80::8cc3:33ff:febb:1b3 make all -C ./receiver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I decided to add build.sh
files to all riot examples, because a simple make all
does not always work. Especially if you also want to build both federations.
Instead of making the runAll.sh
file complicated with different commands per project I let it run build.sh in each folder it can find. This will also prevent the bug that the coap_federated
example wasn't build in the CI because I forgot to add it to buildAll.sh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds reasonable. We must find a good way to build federated programs. Your current proposal, with a single Makefile, works now. But I think in the future we want independent projects for each federate because there might several difference between the boards, and their configuration.
Two questions:
- Are you now able to pick a IP6 address from the tap interface?
- Why do they both specify the same remote?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah sorry github showed me this comment at the bottom and I replied in the main thread and not directly to this comment
@@ -242,17 +242,24 @@ class UcTcpIpChannel( | |||
class UcCoapUdpIpChannel( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this homogeneous enough that one code-generator class works potentially for all platforms?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will find out when we add support for native and Zephyr
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but I wasnt able to run the coap_federated_lf on my end
@@ -0,0 +1,3 @@ | |||
#!/bin/bash | |||
REMOTE_ADDRESS=fe80::8cc3:33ff:febb:1b3 make all -C ./sender | |||
REMOTE_ADDRESS=fe80::8cc3:33ff:febb:1b3 make all -C ./receiver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds reasonable. We must find a good way to build federated programs. Your current proposal, with a single Makefile, works now. But I think in the future we want independent projects for each federate because there might several difference between the boards, and their configuration.
Two questions:
- Are you now able to pick a IP6 address from the tap interface?
- Why do they both specify the same remote?
Not yet. That will come later the |
Because the remote doesn't matter just for building the project, but I have updated the This all will be better when I have a reliable way to extract the IP addresses, but my focus was on getting the tests run reliably right now, so I couldn't look into it yet |
This PR is only about fixing the riot makefile integration to be able to build. The structure of the example is without any indication or proposal in that regard :) This is just the bare minimal that is needed to let it compile and find the makefiles in the correct Once we have agreed on a solution how to structure it, I can align it :) |
OK, thanks for the explanations! Lets go! |
Build:
or
Or directly Build and Run:
or