Silvio Traversaro authored Mar 09, 2021 and Brad King committed Mar 09, 2021

In commit bda5e2ac (FindMatlab: Only include engine and dataarray
libraries if they are found, 2020-12-11, v3.20.0-rc1~297^2~1) we fixed
the imported target to contain optional libraries only if they are
found.  Do the same for `Matlab_LIBRARIES`.

Nikolaj Fogh authored Dec 11, 2020 and Brad King committed Dec 11, 2020

Fixes: #21068, #21582

Issue: #19715

Alexey Kreschuk authored Jul 08, 2020 and Brad King committed Jul 08, 2020

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.

Michael Hirsch, Ph.D authored Feb 11, 2020 and Brad King committed Mar 19, 2020

This allows Matlab R2020a to be recognized as a valid Matlab version.

Silvio Traversaro authored Jan 11, 2020 and Brad King committed Jan 13, 2020

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

Silvio Traversaro authored Jan 11, 2020 and Brad King committed Jan 13, 2020

Reference for versions: https://www.mathworks.com/products/compiler/matlab-runtime.html

Fixes: #20087

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.

Raffi Enficiaud authored Jun 24, 2019 and Brad King committed Jun 25, 2019

Spaces in `DLL_EXPORT_SYM=__attribute__ ((visibility (\"default\")))`
are causing a compilation error.

Fixes: #19279

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.

Chuck Atkins authored Aug 27, 2018 and Brad King committed Oct 10, 2018

Logic added by commit v3.12.0-rc1~183^2 (FindMatlab: Matlab Runtime
Compiler support, 2017-04-29) assumes that `VersionInfo.xml` exists
in the installation.  Fix it to tolerate a missing or empty file.

This change was originally made by commit v3.13.0-rc1~173^2 (FindMatlab:
Guard against nonexistent installation, 2018-08-27).  Here we backport
it to the 3.12.x series.

Fixes: #18436

Sean Warren authored Sep 26, 2018 and Brad King committed Sep 26, 2018

Fixes: #18391

Sean Warren authored Sep 26, 2018 and Brad King committed Sep 26, 2018

Fixes: #17971

Raffi Enficiaud authored Sep 05, 2018 and Brad King committed Sep 05, 2018

This was left accidentally when resolving merge conflicts between
previous changes.

Fixes: #18221

Jason Heeris authored Jul 24, 2018 and Brad King committed Aug 01, 2018

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

luz.paz authored Jun 04, 2018 and Brad King committed Jun 04, 2018

Found via `codespell` and `grep`

Raffi Enficiaud authored Apr 29, 2017 and Brad King committed Apr 23, 2018

* 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

Luz Paz authored Jan 03, 2018 and Craig Scott committed Jan 04, 2018

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

luzpaz authored Nov 02, 2017 and Brad King committed Nov 03, 2017

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