What the different with CommonAPI-4-SOMEIP_deployment_spec and CommonAPI-SOMEIP_deployment_spec, and how to use the identifier in CommonAPI-4, it looks like the generator tools can not recognize that.

COVESA / capicxx-someip-tools

Common API C++ SOMEIP tooling

Mozilla Public License 2.0

76 stars 55 forks source link

What the different with CommonAPI-4-SOMEIP_deployment_spec and CommonAPI-SOMEIP_deployment_spec, and how to use the identifier in CommonAPI-4, it looks like the generator tools can not recognize that. #37

Closed 2stLv closed 7 months ago

2stLv commented 1 year ago

I check this two files:

and i used identifiers that are contained CommonAPI-4-SOMEIP_deployment_spec.fdepl this the result by common-someip-generator-linux-x86_64: why UNDEFIENED_EVENTGROUP_ID and static_cast< CommonAPI::SomeIP::IntegerDeployment* >(nullptr)? Obviously, the generator tool does`t recognize the identifiers,SomeIpNotifierEventGroup and SomeIpIntegerBitWidth and SomeIpIntegerInvalidValue.

Gustavo1515 commented 10 months ago

Can you check if this is still happening using the last released version? (https://github.com/COVESA/capicxx-someip-tools/releases/tag/3.2.14)

I try to reproduce this generation and I got the EVENTGROUP_ID generated correctly:

Regarding the "nullptr", this is an expected behavior. You can check how this is being done here: https://github.com/COVESA/capicxx-someip-tools/blob/master/org.genivi.commonapi.someip/src/org/genivi/commonapi/someip/generator/FrancaSomeIPGeneratorExtensions.xtend