| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes: #21068, #21582
|
| |
|
|
|
|
| |
Issue: #19715
|
|\
| |
| |
| |
| |
| |
| | |
4d292aecb6 FindMatlab: add R2020b => 9.9
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5233
|
| | |
|
|/
|
|
|
|
|
| |
An "unknown" version does not always mean an old version. Setting this
macro by mistake does not result in a compilation error, but not setting
it does. I had this error when compiling from a user that does not have
a matlab license.
|
|
|
|
| |
This allows Matlab R2020a to be recognized as a valid Matlab version.
|
|\
| |
| |
| |
| |
| |
| | |
edb6fe3b6a FindMatlab: add R2019a and R2019b MATLAB_VERSIONS_MAPPING
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4207
|
| |
| |
| |
| |
| |
| | |
Reference for versions: https://www.mathworks.com/products/compiler/matlab-runtime.html
Fixes: #20087
|
|/
|
|
|
|
|
|
|
|
|
| |
Before this modification, the c_mexapi_version.c file was added to
all mex libraries. However, if the C language was not enabled
in the CMake project configuration, the c_mexapi_version.c file
was ignored, creating linking errors in Windows and macOS.
This commit ensures that in the case only the CXX languages is enabled,
the correct version is passed.
Fixes: #19382
|
| |
|
|
|
|
|
| |
If the environment variable MATLAB_ARCH is set prior to the call, the
called scripts do not return an error message.
|
| |
|
|
|
|
| |
Enabling a mex target to be excluded from the `all` target.
|
|\
| |
| |
| |
| |
| |
| | |
c2595a4958 FindMatlab: removing spaces in compiler define
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3473
|
| |
| |
| |
| |
| |
| |
| | |
Spaces in `DLL_EXPORT_SYM=__attribute__ ((visibility (\"default\")))`
are causing a compilation error.
Fixes: #19279
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
56e89e50d3 FindMatlab: simplify several if()-constructs
51bcdeb17f Tests: simplify checks for Matlab variables being set
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3472
|
| |/ |
|
|/
|
|
|
|
|
| |
If an exact version is requested, don't pick the latest matlab version but the one matching
the requested version.
Fixes: #19155
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
- These options are equivalent to `mex` command options `-R2017b` and `-R2018a`.
- `R2017b` is the default, and selects the compatability API.
- `R2018a` is the alternative, and selects the new complex-interleaved API.
- For versions of MATLAB before R2018a, these options are ignored.
- `matlab_add_mex` now works correctly with newer MATLABs.
|
|
|
|
|
| |
- `MX_LIBRARY`, `Matlab_ENGINE_LIBRARY` and `Matlab_DATAARRAY_LIBRARY` are always found.
- The corresponding options are now ignored.
|
| |
|
| |
|
|
|
|
| |
Fixes: #18391
|
|
|
|
| |
Fixes: #17971
|
|\
| |
| |
| |
| |
| |
| | |
bfe883af60 FindMatlab: Remove erroneous duplicate code
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2354
|
| |
| |
| |
| |
| |
| |
| | |
This was left accidentally when resolving merge conflicts between
previous changes.
Fixes: #18221
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
f34f6eb3d1 FindMatlab: Add component to find MCC, the Matlab compiler
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2233
|
| |/
| |
| |
| |
| |
| |
| | |
Add component `MCC_COMPILER` to request searching for the Matlab
compiler. Report it in `Matlab_MCC_COMPILER` if it is found.
Issue: #18183
|
|/
|
| |
From Linux, it fails when cross-compiling
|
|
|
|
| |
Found via `codespell` and `grep`
|
|
|
|
|
|
|
|
|
|
| |
* Determining automatically the MCR version on OSX and Windows
* Distinguishing between MCR and Matlab
* Specific tests for the MCR
* mexext on windows does not work properly: the mexext is hardcoded
* Doc updates for the MCR
Fixes: #16487
|
| |
|
|
|
|
| |
Some are user-facing. Others are source comments.
|
|
|
|
|
|
|
|
|
| |
If the value of `CMAKE_HOST_SYSTEM_PROCESSOR` also happens to be set as
a variable by a project (e.g. `AMD64`), allowing `if()` to
auto-dereference is unlikely to produce a value that matches "64".
Instead let `if()` auto-dereference `CMAKE_HOST_SYSTEM_PROCESSOR`.
Fixes: #17460
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some are user facing.
Found using
codespell -q 3 --skip="./Utilities" -I .cmake-whitelist.txt`
whereby the whitelist contained:
ans
dum
helpfull
emmited
emmitted
buil
iff
isnt
nto
ot
pathes
substract
te
todays
upto
whitespaces
|
| |
|
|
|
|
|
|
|
|
| |
The version string in recent Matlab versions has changed.
Now the version number is inside two `'`.
Patch-by: nama on gitlab.kitware.com
Fixes: #17308
|
|
|
|
|
| |
The variable is not defined on 64-bit MinGW, causing a 32-bit Matlab
version to be found. Check using CMAKE_SIZEOF_VOID_P instead.
|
|
|
|
|
| |
Documentation states CUSTOM_MATLAB_COMMAND, while code uses CUSTOM_TEST_COMMAND.
Addresses issue #17107
|
| |
|
|\
| |
| |
| |
| | |
f2de7079 FindMatlab: Fix typo in matlab_add_unit_test implementation
|
| |
| |
| |
| |
| |
| |
| | |
Fix typo in variable used to communicate between matlab_add_unit_test
and its helper script MatlabTestsRedirect.cmake that was introduced in
commit v3.7.0-rc1~116^2 (FindMatlab: Extend matlab_add_unit_test to run
arbitrary test code, 2016-08-30).
|
|/ |
|
|\ |
|
| | |
|
|/ |
|