Build machineless libmetal v2025.10 #354
Conversation
libmetal can be build without any machine support. It is possible that vendors implement machine specific interfaces outside of libmetal and link it with demos during build time. Hence, remove requirement to have MACHINE and PROJECT_MACHINE variables from the build system. If vendor prefer to choose 'template' machine, they can pass such option during cmake configuration. Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
This directory was removed and re-inroduced by mistake, and should not exists in the libmetal. Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
Declare sys_irq_enable() and sys_irq_enable() directly in lib/system/@PROJECT_SYSTEM@/sys.h. This allows to declare the machine out of tree of the libmetal but also to support the in-tree template. [minor style related fix by tanmay] Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com> Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
tnmysh
force-pushed
the
build_machineless_libmetal_v2025.10
branch
from
796911b to
243877d
Compare
|
@arnopo Hi just checking in - will this be merged soon? As we have a few openamp-sys-ref PRs dependent on this :) |
I understood from @tnmysh that this was only needed to ensure compatibility with the openamp-system-reference v2025.10, as specified here: Do you mean that you also need a v2025.10.1 release for the openamp-system-reference repository? Regarding this PR: Alternatively, libmetal PR #350, which is the mirror for the main branch, should allow you to move forward on the openamp-system-reference |
|
I plan to perform few non regression tests on this one before merging and add the v2025.10.1 tag, i target this for beginning of next week |
5 participants
libmetal doesn't need MACHINE variable to be defined. Without MACHINE defined, it relies on external vendor extension for machine related interface implementation and link with demos during build time.