-
Notifications
You must be signed in to change notification settings - Fork 32
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
recipes-openamp: get rpmsg apps from new repo #22
Conversation
@wmamills, @edmooring, @arnopo This change resolves issue: #18 For now, only rpmsg-echo-test is moved. Once everything looks good for this example, I will replicate changes for other two examples. |
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 to me.
@edmooring Thanks for approval. One minor change, we are moving LICENSE file to root directory in openamp-system-reference repo. So, I will have to change LICENSE file location in bitabake script. |
7d0ede7
to
5d45f79
Compare
Most of this should be factored out of the individual recipes and made an inc file at the rpmsg-examples level. The other thing that is strange here is pointing the WORKDIR deep into the repo clone. I will look for a better way to do this. @mhatle may have other suggestions |
Ack.
Yes correct, we need better way to do this. I tried with making single bb file that compiles all the demos i.e. openamp-system-reference.bb, how ever it needs makefile in root dir. Which I believe wasn't good idea. I agreed with @arnopo and removed Makefile from root dir. So, I had to go all the way to example root dir where Makefile is available. One solutiont could be, If we agree to keep Makefile in root dir, then we can call different targets from that make file from different recipes. Not sure if it's good idea though. I definitely look forward to better and clean solution to this.
|
LGTM |
If we go the single makefile route, I would not delete the individual ones. Just add a new one that calls each of the sub makes. However I am OK to merge 3 recipies and look for a better way over time. |
BTW: This will need to be rebased now that I have accepted the PRs from May |
You can use WORKDIR in the LIC_FILES_CHKSUM. |
Also please change LICENSE to match the new master. "BSD" gives warnings. You need to specify which BSD. |
Sure I will do that. |
This sounds good idea. Thanks. |
Actually I see that we may not need single make file, if we can accept that S = "${WORKDIR}/git/examples/linux/rpmsg-echo-test" With this Makefile in root dir is not needed for now. We can introduce common Makefile if needed in future. |
Yes I am OK with that as long as we use ${WORKDIR} in the LIC_FILES_CHKSUM |
One more thing. I did make common .inc file which will be included in all of the three .bb files. |
This PR is already a single commit. I am OK with it staying that way. |
I am sorry I meant in https://github.com/OpenAMP/openamp-system-reference repository. |
I am sorry, I wasn't clear. I mean in openamp-system-reference repo: https://github.com/OpenAMP/openamp-system-reference |
5d45f79
to
4820a9f
Compare
remove rpmsg-echo-test, rpmsg-mat-mul and rpmsg-proxy-app source files and modify relative recipe to sync code from openamp-system-reference repo Signed-off-by: Tanmay Shah <[email protected]>
4820a9f
to
ed069e2
Compare
Discussed this with Bill offline. We don't need such sync between two different repository. So, no need to introduce all application in single commit in openamp-system-reference repository. |
I attempted to merge this request and got the following errors: WARNING: rpmsg-proxy-app-1.0-r0 do_unpack: rpmsg-proxy-app: the directory ${WORKDIR}/git/examples/linux/rpmsg-proxy-app (/scratch2/fray/git/openamp/build-honister/tmp/work/core2-64-poky-linux/rpmsg-proxy-app/1.0-r0/git/examples/linux/rpmsg-proxy-app) pointed to by the S variable doesn't exist - please set S within the recipe to point to where the source has been unpacked to WARNING: rpmsg-mat-mul-1.0-r0 do_unpack: rpmsg-mat-mul: the directory ${WORKDIR}/git/examples/linux/rpmsg-mat-mul (/scratch2/fray/git/openamp/build-honister/tmp/work/core2-64-poky-linux/rpmsg-mat-mul/1.0-r0/git/examples/linux/rpmsg-mat-mul) pointed to by the S variable doesn't exist - please set S within the recipe to point to where the source has been unpacked to WARNING: rpmsg-echo-test-1.0-r0 do_unpack: rpmsg-echo-test: the directory ${WORKDIR}/git/examples/linux/rpmsg-echo-test (/scratch2/fray/git/openamp/build-honister/tmp/work/core2-64-poky-linux/rpmsg-echo-test/1.0-r0/git/examples/linux/rpmsg-echo-test) pointed to by the S variable doesn't exist - please set S within the recipe to point to where the source has been unpacked to S is being set to: S = "${WORKDIR}/git/examples/linux/rpmsg-echo-test" The git checkout is empty, so your pull requests to git://github.com/OpenAMP/openamp-system-reference need to be approved before this can be merged. Finally the SRCREV is set to 'AUTOREV' which will cause the system to pull data from GitHub on EVERY build. Whatever the 1.0 release is, is what the SRCREV should point to. Autorev will cause problems. |
I have reworded this PR as new PR#28. |
remove rpmsg-echo-test source files and modify relative recipe to sync code from openamp-system-reference repo
Signed-off-by: Tanmay Shah [email protected]