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
When compiling companion on Slackware linux got the error:
cmake ../src/
-- The C compiler identification is GNU 4.8.2
-- The CXX compiler identification is GNU 4.8.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Looking for XercesC
-- found xerces-c: /usr/lib64/libxerces-c.so
-- Looking for Xsd
-- XSDCXX_EXECUTABLE-NOTFOUND
CMake Error at CMakeLists.txt:27 (MESSAGE):
XSD not found! Please set XSD path ...
-- Configuring incomplete, errors occurred!
Thing is I have XSD "All-In-One Package" package working in a non standard directory (no easy package for slackware, and I need it only for OpenTX).
The solution is quite simple, set XSDDIR to that directory! But it still produces the same problem... The search path in FindXsd.cmake does not include the sub-directories for the "All-In-One Package"!!!
Already solved, opening issue to reference in pull request! 😉
p.s.
export XSDDIR=$DIR/xsd-3.3.0+dep/xsd
The text was updated successfully, but these errors were encountered:
When compiling companion on Slackware linux got the error:
Thing is I have XSD "All-In-One Package" package working in a non standard directory (no easy package for slackware, and I need it only for OpenTX).
The solution is quite simple, set XSDDIR to that directory! But it still produces the same problem... The search path in FindXsd.cmake does not include the sub-directories for the "All-In-One Package"!!!
Already solved, opening issue to reference in pull request! 😉
p.s.
export XSDDIR=$DIR/xsd-3.3.0+dep/xsd
The text was updated successfully, but these errors were encountered: