Compilation Error

[tao28005]

Hello,

Compilation in release mode stopped with the following error messages:

codes/GEOS/examples/functions/function_examples/function_examples.xml:11: element SymbolicFunction: Schemas validity error : Element 'SymbolicFunction': This element is not expected. Expected is one of ( MultivariableTableFunction, TableFunction ).

Thanks

[rnelias]

Same problem here...

[guydriesen]

Also facing exact the same problem...

[rrsettgast]

@tao28005 @rnelias @guydriesen

This is a validation step, and the code should have already been built. Can you confirm this?

To work around this, I think you can install mathpresso in your TPL's if it already isn't there, and then turn it on inside your hostconfig. I believe the option is:

set( ENABLE_MATHPRESSO ON CACHE BOOL "" FORCE )

@CusiniM We either need to modify the quick-start-template.cmake file to turn this on, or remove the use from the xml file.

[guydriesen]

@rrsettgast Thanks a lot!
Yes, I started from the quick-start-template.cmake file and after enabling the mathpresso tpl compilation was successful.
Removing the offending lines from the xml file also caused the src/coreComponents/schema/schema.xsd and src/coreComponents/schema/schema.xsd.other files to change during the compile process, so I was not sure if this was ok.

[CusiniM]

@tao28005 @rnelias @guydriesen

This is a validation step, and the code should have already been built. Can you confirm this?

To work around this, I think you can install mathpresso in your TPL's if it already isn't there, and then turn it on inside your hostconfig. I believe the option is:

set( ENABLE_MATHPRESSO ON CACHE BOOL "" FORCE )

@CusiniM We either need to modify the quick-start-template.cmake file to turn this on, or remove the use from the xml file.

Mathpresso used not to work on MacOs which is why I had it off but we could turn it on now. Alternatively we could:

• have an exclusions list when validating xmls with mathpresso off.
• reorganize the cmake targets and avoid validating xml as part of the build but have it as a separate independent targe.
• modify the error messages of that xml validation step. For the version of geos that was built (without mathpresso) that's indeed an invalid xml. The error could clarify why instead of resulting in an error that looks like a build failure.