Hi,
Is that the full error message?
Can you try to execute the cmake command manually in the generated code folder?
Please post the full error message formatted using three ``` symbols
By the way, here is the full output in the command window of Matlab (this might be useful information):
acados_install_windows()
Setting up environment PATH variable
Creating build dir in ...
Warning: Directory already exists.
> In acados_install_windows (line 48)
ACADOS_INSTALL_DIR is ...
Executing cmake configuration
cmake.exe -G "MinGW Makefiles" -DACADOS_INSTALL_DIR=%ACADOS_INSTALL_DIR% -DBUILD_SHARED_LIBS=OFF -DACADOS_WITH_OSQP=OFF -DCMAKE_POLICY_VERSION_MINIMUM=3.5 ..
CMake Deprecation Warning at CMakeLists.txt:32 (cmake_minimum_required):
Compatibility with CMake < 3.10 will be removed from a future version of
CMake.
Update the VERSION argument <min> value. Or, use the <min>...<max> syntax
to tell CMake that the project requires at least <min> but has been updated
to work with policies introduced by <max> or earlier.
-- Build type is Release
-- ACADOS_WITH_OPENMP: OFF
CMake Error at external/CMakeLists.txt:48 (add_subdirectory):
The source directory
....
does not contain a CMakeLists.txt file.
CMake Error at external/CMakeLists.txt:61 (add_subdirectory):
The source directory
....
does not contain a CMakeLists.txt file.
--
-- Target: BLASFEO is X64_AUTOMATIC, HPIPM is GENERIC
-- Linear algebra: HIGH_PERFORMANCE
-- Octave MEX (OFF)
-- System name:version Windows:10.0.19045
-- Build type is Release
-- Installation directory is ....
-- OpenMP parallelization is OFF
--
-- Configuring incomplete, errors occurred!
Error using acados_install_windows (line 69)
cmake command failed. Command was:
cmake.exe -G "MinGW Makefiles" -DACADOS_INSTALL_DIR=%ACADOS_INSTALL_DIR% -DBUILD_SHARED_LIBS=OFF -DACADOS_WITH_OSQP=OFF -DCMAKE_POLICY_VERSION_MINIMUM=3.5 ..
I don’t see a way to include the submodules when dowloading the zip.
There are many other tools to clone git repositories, I used “git bash” on Windows.
Yea, GitHub does not automatically do a full clone for the auto-generated zip files. In OSQP, we ended up making a step in our release workflow at the time that would clone and fully initialize the submodules, then zip them and upload to the release as a full source archive to reduce user confusion.