-
Notifications
You must be signed in to change notification settings - Fork 10
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
cpackget dependency question #2
Comments
In my opinion, OpenCMSIS tools must remain "atomic" and independent. Or shall we consider that cbuildgen is the atomic service and that cbuild is already an higher level service ? The README states: ==> cpackget is indeed listed. But to me cbuilgen+cmake+ninja make sense it has a consistency. |
|
@brondani : but how did you manage to pass the csolution step if the packs are missing ? |
@jeromecoutant yes I understand you don't need
I see the potential of having a front-end with a wider scope including project management (csolution) capabilities, I believe it's worth to be discussed. |
@brondani : I do not think it is the role of OpenCMSIS to provide front-end tools. I am interested in having cbuild "wrapping" the build so abstracting cmake+ninja+compiler I am not interested in having cbuild doing more than this. I think that it is at the cprj generation stage that packs can be checked. To me the OpenCMSIS tools are here to be a "reference" to check that our implementations are respecting the spec.
So let's say I provide a cprj with missing packs in the environment:
|
@fred-r While keeping the separation of concerns among the atomic services, I don't see why a reference front-end cannot use all available tools to provide the best possible user experience. Anyway as I said currently |
Just clarifying my position before we discuss it: I do not want to prevent you from doing whatever can be helpful in a front-end, I agree with you on that.
So, my point is more to say:
|
@jeromecoutant Please check if the CMSIS-Toolbox 0.10.1 works as you expect: |
Yes, issue can be closed |
Hi
My CMSIS_PACK_ROOT is well specified, but I couldn't use cbuild and cbuildgen in standalone:
Can we consider that cpackget is not "mandatory" to call cbuild application ?
The text was updated successfully, but these errors were encountered: