MATLAB: How to compile and run a MATLAB Engine program on UNIX/Linux/Mac

compileengdemoengdemo.cengineexecutelinuxmacMATLABosxprogramrununix

I have completed the steps in the External Interfaces manual but I am having difficulty compiling and running my Engine program. I would like step-by-step instructions on how to achieve this.

Best Answer

This enhancement has been incorporated in Release 2006b (R2006b). For previous product releases, read below for any possible workarounds:

To run an Engine application, you must set the path and the dynamic library path on your machine appropriately.

Perform the following steps:

1. To add MATLAB to the path environment variable:

On a bash shell, enter

export PATH=$PATH:(<matlabroot>/bin)

On a csh / tcsh shell, enter

set path = ($path <matlabroot>/bin)

where <matlabroot> is the path where MATLAB is installed and can found by entering

matlabroot

at the MATLAB Command Prompt.

2. On MATLAB 6.5(R13) Set the runtime library path environment variable LD_LIBRARY_PATH to:

<matlabroot>/extern/lib/<arch>:<matlabroot>/sys/os/<arch>:$LD_LIBRARY_PATH

On MATLAB 7.0(R14) and later set the runtime library path environment variable LD_LIBRARY_PATH to:

<matlabroot>/bin/<arch>:<matlabroot>/sys/os/<arch>:$LD_LIBRARY_PATH

Where <matlabroot> is the path to your MATLAB installation, and <arch> is the proper architecture/OS directory such as glnx86 if you are using x86 Linux.

Some UNIX operating systems use SHLIB_PATH or DYLD_LIBRARY_PATH instead of LD_LIBRARY_PATH, and therefore you may need to set them instead of LD_LIBRARY_PATH. For more details, and to see which one you should set, see the following URL:

http://www.mathworks.com/help/releases/R13sp2/techdoc/matlab_external/ch_java9.html#20231

3. Start MATLAB.

4. Compile and link the engdemo.c example:

mex -f <matlabroot>/bin/engopts.sh <pathname>/engdemo.c

where <pathname> specifies the complete path to the specified file.

5. Exit MATLAB.

6. From your shell prompt, execute:

<pathname>/engdemo

Related Solutions

MATLAB: How to resolve ulimit related issues in R2017a on macOS Sierra

This issue has been resolved as of MATLAB R2017b.

For releases prior to MATLAB R2017b, the default ulimit is set to 256 on macOS. In previous releases of MATLAB our launch scripts would temporarily increase the ulimit for the session to prevent the MATLAB instance from encountering the low limit. In R2017a, we no longer have such a script in place when MATLAB is launched from the application bundle or the dock. To avoid these issues, you will need to set the ulimit to a higher number, for instance 1024. In order to ensure that the change in ulimit persists across reboots please attempt the following workaround:

 In Library/LaunchDaemons create a file named limit.maxfiles.plist and paste the following in:

<?xml version="1.0" encoding="UTF-8"?>  
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"  
        "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">  
  <dict>
    <key>Label</key>
    <string>limit.maxfiles</string>
    <key>ProgramArguments</key>
    <array>
      <string>launchctl</string>
      <string>limit</string>
      <string>maxfiles</string>
      <string>1024</string>
      <string>unlimited</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
    <key>ServiceIPC</key>
    <false/>
  </dict>
</plist>

*Note: 1024 was arbitrarily picked, please increase as necessary.

2. Change the owner of your new file:

sudo chown root:wheel /Library/LaunchDaemons/limit.maxfiles.plist

3. Load these new settings:

sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist

Finally reboot your machine and verify that your ulimit has increased in terminal by running the command "ulmit -Sn". Assuming it has you should be able to start MATLAB without issue.

MATLAB: How to configure the LD_LIBRARY_PATH on Linux and DYLD_LIBRARY_PATH on MAC OS X to point to MCR

To set the LD_LIBRARY_PATH on Linux follow the steps below:

1. Determine Linux shell being used. Use the following command on the Linux terminal:

echo $SHELL

For a TCSH shell this will return "/bin/tcsh"

For a BASH shell this will return "/bin/bash"

2. Check if you have a .tcshrc or .bashrc file ("the startup file") on your system. These files are run whenever a new terminal is opened.

ls -all

3. If the startup file is not present, you can create one for TCSH/BASH respectively:

touch .tcshrc
touch .bashrc

4. Check if LD_LIBRARY_PATH has been set already:

echo $LD_LIBRARY_PATH

This will either return the value for LD_LIBRARY_PATH or the following message:

LD_LIBRARY_PATH: Undefined variable

5. Open the file for editing in vi for TCSH/BASH respectively:

vi .tcshrc
vi .bashrc

6. Append the paths from the Configuration Notes dialog box ("<mypath>") obtained during MCR installation.

If LD_LIBRARY_PATH was not already set (refer to Step 4), append the variable using the first line. Otherwise, use the second.

For BASH:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<mypath>
or
export LD_LIBRARY_PATH=<mypath>

For TCSH:

setenv LD_LIBRARY_PATH {$LD_LIBRARY_PATH}:<mypath>
or
setenv LD_LIBRARY_PATH <mypath>

7. Save and exit vi using Shift + :wq

8. Confirm the LD_LIBRARY_PATH has been set correctly. Open a new terminal and execute:

echo $LD_LIBRARY_PATH

This should now reflect the paths to the MCR that you just set.

NOTE:

To set DYLD_LIBRARY_PATH on MAC OS X 10.11 and newer, you must use the following syntax when running an application ("run.app"):

DYLD_LIBRARY_PATH="/my/path/to/mcr" ./run.app

This is because dynamic library environment variables are no longer copied to child processes, due to System Integrity Protection.

Best Answer

Related Solutions

MATLAB: How to resolve ulimit related issues in R2017a on macOS Sierra

MATLAB: How to configure the LD_LIBRARY_PATH on Linux and DYLD_LIBRARY_PATH on MAC OS X to point to MCR

Related Question