addpath problem when building a standalone exe

Figure shows a snapshot of my main function.

Figure shows there are five depenecy (dir) included before I build exe.

After running the bulit standalone exe, the error pops out.

Does anyone encounter the same problem?

Answer 1

[Image Analyst]

Yep. Give the full path, starting from the root folder. The reason is that the executable folder is not where you think it is (long story - just trust me).

[BY H]

I have tried but also failed.

Answer 2

[Walter Roberson]

https://www.mathworks.com/help/compiler/unsupported-functions.html

Functions Not Supported for Compilation by MATLAB Compiler and MATLAB Compiler SDK

run

[Image Analyst]

If it's an m-file you're trying to run, just give the name of the function. Do not wrap it with run().

[Walter Roberson]

The user is actively using the feature of run() of providing a path. matconvnet uses vlfeat but the version of vlfeatbbeing used for it is different than the vlfeat that the user wants to use for other purposes, so in that case, the path makes a difference: the user is deliberately selecting one particular one of the incompatible versions for one purpose, and a different one for a different purpose.

[BY H]

To add the following condition for check is feasible?

if ~(ismcc || isdeployed)
 line 3-9
end

[Walter Roberson]

No. Those functions still need to be run in order to establish proper state.

However, you did the addpath() so those functions should already be on the path, so you should not need run() unless you are trying to force it to use different vlfeat for the two different projects.

Replace the two run() with

vl_setup;
vl_setupnm;