Question about error message while command line execution

Joung — Wed, 22 Nov 2023 16:21:32 GMT

Hello, I'm trying to set-up a CI/CD environment using command line execution. (with S32K344 project)

I've followed the manual in S32 Design studio (In Help menu), and as a result, output files came out binary same (using command line execution & GUI build).

But my question is, when I build my project with command line execution, some of error messages showed up.

First, when i generate code using the command below,

< command : (Import configuration from existing .mex file and generatecode)>

eclipsec.exe -noSplash \
-application com.nxp.swtools.framework.application \
--launcher.ini /path/to/S32DS/installation/eclipse/s32ds.ini \
-HeadlessTool Peripherals \
-Load /path/to/mex/file \
-ExportSrc /path/where/to/export/generated/files

below errors showed up.

- Severe : Cannot get container for IPath D:/temp/231122/mcu-s32k3/mcu_s32k3.mex

- Severe : [DATA] Error resolving: ((($configSet.SpiGeneral.SpiEnableLargeFrameSize.getValue() == false) && ($this.getValue() <= 64)) || (($configSet.SpiGeneral.SpiEnableLargeFrameSize.getValue() == true) && ($this.getValue() <= 4096))), class java.lang.String cannot be cast to class java.lang.Long (java.lang.String and java.lang.Long are in module java.base of loader 'bootstrap')

- Severe : [DATA] Setting value to a variable/info setting with id: Lpuart_Uart.UartGlobalConfig.UartChannel.0.DetailModuleConfiguration.lpuartClockValue

- Severe : [SDK/Data] Code generation failed for Peripherals: Script codegenerator.js finished with exception on line 552: ReferenceError: "mexPath" is not defined

And when I import project into Eclipse workspace, below errors showed up.

< command >

eclipsec.exe -noSplash\
-application org.eclipse.cdt.managedbuilder.core.headlessbuild \
--launcher.ini /path/to/S32DS/installation/eclipse/s32ds.ini \
-data /path/to/workspace \
-import /path/to/project

< error messages >

Managed Build system manifest file error: Duplicate identifier gnu.c.compiler.option.debugging.sanitaddress for element type Option.

Managed Build system manifest file error: Duplicate identifier gnu.c.compiler.option.debugging.sanitpointers for element type Option.

Managed Build system manifest file error: Duplicate identifier gnu.c.compiler.option.debugging.sanitaddress for element type Option.

Managed Build system manifest file error: Duplicate identifier gnu.c.compiler.option.debugging.sanitpointers for element type Option.

Managed Build system manifest file error: Duplicate identifier gnu.c.compiler.option.debugging.sanitaddress for element type Option.

Managed Build system manifest file error: Duplicate identifier gnu.c.compiler.option.debugging.sanitpointers for element type Option.

Managed Build system manifest file error: Duplicate identifier gnu.c.compiler.option.debugging.sanitaddress for element type Option.

Managed Build system manifest file error: Duplicate identifier gnu.c.compiler.option.debugging.sanitpointers for element type Option.

Managed Build system manifest file error: Unable to resolve the category identifier gnu.c.compiler.category.debug in the option gnu.c.compiler.option.debugging.sanitaddress.

Managed Build system manifest file error: Unable to resolve the category identifier gnu.c.compiler.category.debug in the option gnu.c.compiler.option.debugging.sanitpointers.

Managed Build system manifest file error: Unable to resolve the superClass identifier ghs.managedmake.arm64.executable.toolchain in the toolChain com.nxp.s32ds.cle.arm.mbs.arm64.ghs.toolchain.debug.

Managed Build system manifest file error: Unable to resolve the superClass identifier ghs.managedmake.arm64.executable.toolchain in the toolChain com.nxp.s32ds.cle.arm.mbs.arm64.ghs.toolchain.release.

Managed Build system manifest file error: Unable to resolve the superClass identifier ghs.managedmake.arm64.static_library.toolchain in the toolChain com.nxp.s32ds.cle.arm.mbs.arm64.ghs.toolchain.debug.lib.

Managed Build system manifest file error: Unable to resolve the superClass identifier ghs.managedmake.arm.executable.toolchain in the toolChain com.nxp.s32ds.cle.arm.mbs.ghs.toolchain.debug.

Managed Build system manifest file error: Unable to resolve the superClass identifier ghs.managedmake.arm.executable.toolchain in the toolChain com.nxp.s32ds.cle.arm.mbs.ghs.toolchain.release.

Managed Build system manifest file error: Unable to resolve the superClass identifier ghs.managedmake.arm.executable.toolchain in the toolChain com.nxp.s32ds.cle.arm.mbs.ghs.toolchain.debug.ram.

Managed Build system manifest file error: Unable to resolve the superClass identifier ghs.managedmake.arm.executable.toolchain in the toolChain com.nxp.s32ds.cle.arm.mbs.ghs.toolchain.release.ram.

Managed Build system manifest file error: Unable to resolve the superClass identifier ghs.managedmake.arm.static_library.toolchain in the toolChain com.nxp.s32ds.cle.arm.mbs.ghs.toolchain.debug.lib.

Managed Build system manifest file error: Unable to resolve the superClass identifier ghs.managedmake.arm.static_library.toolchain in the toolChain com.nxp.s32ds.cle.arm.mbs.ghs.toolchain.release.lib.

Managed Build system manifest file error: Unable to resolve the category identifier gnu.c.compiler.category.debug in the option gnu.c.compiler.option.debugging.sanitaddress.

Managed Build system manifest file error: Unable to resolve the category identifier gnu.c.compiler.category.debug in the option gnu.c.compiler.option.debugging.sanitpointers.

Since the build result seems to be OK, but i wonder if I'm OK to ignore these error messages.

(I've used the tool version 3.5 (S32 Design Studio))

Re: Question about error message while command line execution

nancb — Wed, 28 Feb 2024 02:03:54 GMT

Hello,

I have the same problem here. Do you have a solution?

S32K中的主题 Question about error message while command line execution

Question about error message while command line execution

Re: Question about error message while command line execution