You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cloned the repository with the command git clone --recursive -b develop https://github.com/eclipse-4diac/4diac-fbe.git
When executing the compile script using .\compile.cmd native-toolchain on Windows 11, several issues occur:
Instead of open62541 v1.4, v1.0 is used. This leads to Forte compilation errors for OPC UA related files, as it can not find specific references. Error1_native-toolchain.log CMakeOutput.log
I commented the version detection code in detect_legacy_open62541_version() and hardcoded the version to 1.4.
This lead to a successful compilation of Forte. However, I noticed that for [email protected] the `ENABLE_AMALGAMATION` flag was set to OFF.
Setting this to ON lead to an error, where it could not find a poll-release file. There was no error log, maybe because the build just failed on a
subcommand. Find a screenshot and a copy of the last output lines below.
Removing the OPC UA dependency and the OPC UA layer from the default.txt configuration did not lead to a successfull build, because there is another problem, which will be addressed in a second Issue (Edit: #28).
The text was updated successfully, but these errors were encountered:
@gravemalte
I cloned the repository with the command
git clone --recursive -b develop https://github.com/eclipse-4diac/4diac-fbe.git
When executing the compile script using
.\compile.cmd native-toolchain
on Windows 11, several issues occur:Instead of open62541 v1.4, v1.0 is used. This leads to Forte compilation errors for OPC UA related files, as it can not find specific references.
Error1_native-toolchain.log
CMakeOutput.log
I commented the version detection code in
detect_legacy_open62541_version()
and hardcoded the version to 1.4.poll-release.txt
Removing the OPC UA dependency and the OPC UA layer from the
default.txt
configuration did not lead to a successfull build, because there is another problem, which will be addressed in a second Issue (Edit: #28).The text was updated successfully, but these errors were encountered: