On 16/03/2020 13:51, Hesham Almatary wrote:
Thanks Sebastian!
I tried to follow your instructions for adding this as a new option,
but unfortunately, XLEN didn't evaluate for
RTEMS-BUILD-CPUKIT-OPTCLANG to use. Here's the diff:
diff --git a/spec/build/cpukit/RTEMS-BUILD-CPUKIT-OPTXLEN.yml
b/spec/build/cpukit/RTEMS-BUILD-CPUKIT-OPTXLEN.yml
new file mode 100644
index 0000000000..840a8ecc2c
--- /dev/null
+++ b/spec/build/cpukit/RTEMS-BUILD-CPUKIT-OPTXLEN.yml
@@ -0,0 +1,19 @@
+active: true
+build-type: option
+default: ''
+default-by-variant:
+- value: '64'
+ variants:
+ - riscv/rv64.*
+derived: false
+enabled-by: []
+header: ''
+level: '1.110'
+links: []
+name: XLEN
+normative: true
+order: -1000
+ref: ''
+reviewed: ChapNb5NSPl062d5CnU251RB5J6TljFz_mLkmFdgwVY=
+text: ''
+type: build
grepping for XLEN only gets me:
c4che/spec_build.pickle:133389:ssS'RTEMS-BUILD-CPUKIT-OPTXLEN'
c4che/spec_build.pickle:133433:S'XLEN'
c4che/spec_build.pickle:154984:S'--target=${ARCH}${XLEN}-unknown-rtems${__RTEMS_MAJOR__}'
Am I missing something?
Did you link the new item to
spec/build/cpukit/RTEMS-BUILD-CPUKIT-CPUOPTS.yml
?
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
