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
CMake usage in recommended project structure #1098
Comments
One problem while trying to fix/improve cmake: But I am not a python or lbuild expert. I then try to use the override option of cortex-m If I use a real relative path it works |
It's intended to compile the projects separately. I'm not a CMake expert, there's too much conflicting advice online about how to do things in CMake that I never got how it's supposed to work, so I don't really know how good our solution is. Thank you for improving it! What you're looking for is this The linkerscript flags gets added here. You can see that the So you should get this behavior by replacing |
Did you find a solution to your problem? |
If I read https://modm.io/guide/custom-project/ correct it is intended to maintain multiple binaries in one repo (in example a dual core processor)
Therefor for each project lbuild must be run and each got an
modm
folder.Is this the intended way for modm?
In this configuration I normally have a CMakeLists.txt which includes "everything" and can build everything in
root/build/
(root/build/app/nice_project_1
,root/build/app/nice_project_2
and so on). With only to commands I can build every target. No directory switching needed.If I try to do it with an modm_project, I got some errors because the pathes doesn't match because wrong variables are used at some places.
I could fix it easily and can create an PR.
Maybe https://github.com/modm-ext/modm_starter_project should be updated to match the recommended file structure of https://modm.io/guide/custom-project/
The text was updated successfully, but these errors were encountered: