Hi Olof, > So it is at least it is not as simple as defining Init##num components for ARM > since currently only one VM component is allowed in the macros. > > Do you have a recommended way that could achieve a CAmkES structure that > allows for multiple differently configured VMs for ARM without altering the > macros? > If it is not possible at the time I assume that switching to x86 is the > easiest alternative to achive this? >
The macros are there for convenience's sake and also to generalise things. Most of the VM applications that we have generally repeat the same things as there are specific attributes and interfaces that the (Arm) VMs require. However, it is definitely possible to have multiple differently configured VMs in the sense that each VM may have different extensions added but they each share the same subset of attributes and interfaces that are necessary. This will probably require more work in terms of build system hackery to direct specific files and libraries to the separate VM components as we don't have that sort of distinction at the moment in our sample VM applications. It may make sense to have each VM be a separate CAmkES component like the components in the 'global- components' folder/repository and then include them altogether in the final .camkes file like the vm_multi application. For your application's .camkes file, you can choose to use a subset of the macros and then handwrite the rest of the configuration needed for your purposes. Hope this helps, and feel free to shoot more questions. Also sorry it took so long. Regards, Damon _______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
