FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
09-08-2023 12:04 PM
I installed V2.02 of the ctrlX SDK in my App Build Environment and I'm able to build the snaps for all C++ samples but the datalayer.register.node sample. When I execute the build script (does not matter if amd or arm) I get the following error message during the compilation with cmake:
CMake Error at /home/boschrexroth/ctrlx-automation-sdk/cmake/BuildMDDB.cmake:35 (add_custom_command):
Error evaluating generator expression:
$<TARGET_FILE:mddb_compiler>
No target "mddb_compiler"
Call Stack (most recent call first):
CMakeLists.txt:29 (build_mddb)
CMake Error at /home/boschrexroth/ctrlx-automation-sdk/cmake/BuildMDDB.cmake:35 (add_custom_command):
Error evaluating generator expression:
$<TARGET_FILE:mddb_compiler>
No target "mddb_compiler"
Call Stack (most recent call first):
CMakeLists.txt:29 (build_mddb)
CMake Error at /home/boschrexroth/ctrlx-automation-sdk/cmake/BuildMDDB.cmake:35 (add_custom_command):
Error evaluating generator expression:
$<TARGET_FILE:mddb_compiler>
No target "mddb_compiler"
Call Stack (most recent call first):
CMakeLists.txt:29 (build_mddb)
CMake Error at /home/boschrexroth/ctrlx-automation-sdk/cmake/BuildMDDB.cmake:35 (add_custom_command):
Error evaluating generator expression:
$<TARGET_FILE:mddb_compiler>
No target "mddb_compiler"
Call Stack (most recent call first):
CMakeLists.txt:29 (build_mddb)
-- Generating done
CMake Generate step failed. Build files cannot be regenerated correctly.
Solved! Go to Solution.
09-08-2023 12:24 PM
This is a known bug in the V0202 of the SDK. And will be fixed with the next upload there.
In the meanwhile you can fix the problem with some changes in the CMakeLists.txt.
I added the updated CMakeLists.txt here, you can replace your CMakeLists.txt in the datalayer.register.node with this fixed one and you are good to go.
Best regards,
Nick
09-13-2023 11:14 AM
Update!
This bug got fixed with Version 2.2.3 of the SDK, which is available on GitHub.