Matlab compiler shared resources and helper files

I have some matlabfiles which must be a standalone. Because I need also other files I have a description to do it: Add folder X to shared resources and helper files (this is the same as the -a option in the command line) Further, the folders Y and Z must be in the Matlab path.

I know I can use matlab compiler. But I saw that shared resources and helper files is for older versions of matlab. Can anyone tell me what I have to do with these folder X (if I use the application matlab compiler) and what they mean with adding folder Y and Z to the matlab path?

Answer 1

[Harsheel]

1. You need to add folder X in the "Files required for your application to run" section below the "Application Information" GUI. See attached image.
2. Before running deploytool, etc, add paths to Y and Z to matlab path:

addpath('C:\Documents\whatever\Y')
addpath('C:\Documents\whatever2\Z')

[Image Analyst]

Like I said above, you'll have to deploy those files yourself because deploytool cannot install files to folder C:\Documents\whatever\Y or C:\Documents\whatever2\Z. Then you specifically have to create that path name in your source code, or else add those folders to the path, which you can do in your startup.m file or your main app's m-file. You can't just call addpath in the command window before you run deploytool like you said because that path addition won't make it to the deployed executable - it will just take effect in your current session of the MATLAB development environment and be lost once you exit MATLAB.

[Diede]

Ok, thank you! So, for my folder Y and Z: If I have these on my computer, then I just have to "determine" the path in the startup.m file? How can I get these startup.m file? And what have I exactly to write down in that file such that it works?

Oh, these folders also contains .m files

[Harsheel]

If the addpath commands are only used for compilation process then we don't really need to do what you suggested.

It seems like the Y and Z folders only have .m files. In that case you don't have to create startup.m file. I'd suggest trying to run the executable without creating the startup.m file and seeing if you get any "undefined function or variable" error. Do make sure that everything works in MATLAB though.

[Image Analyst]

Harsheel, I see that you work as a developer on the compiler toolbox. When will be be able to deploy files to specific folders, like to c:\users\public\documents? Not being able to do that, and the pain of having deployed files be in secret hidden locations, is a real deal breaker for me as far as using deploytool to create a complete installation package. (I don't blame you if you don't answer since it seems the Mathworks never tips their hand on upcoming features.) Sometimes I need users to be able to find and edit some files manually and we can't do that if the file is hidden in some strange folder or in a subfolder of Program Files.

P.S. I'll be at the Mathworks the week of Sept 22-24 if you want to talk in person.

[Diede]

Ok, I checked: the .m files in the Y and Z folders are needed for the files in the X folder.

Answer 2

[Image Analyst]

You can ship other files, however the deploytool requires that they be subfolders of your application. They can't be just anywhere you want. That's why I don't use deploytool. You can use a third party installation package builder to put your files where you want and they don't have to be on the MATLAB search path. However, when you go to access them, you must use the full path where you expect them to be. If you leave off the folder in your filename when you use something like load() or xlsread(), then it will search only the search path and won't find your special folder. That's why you need to specify the full path name, which, of course, is an excellent idea in any case.

[Diede]

I don't know what you exactly mean. Some extra information: the standalone must not run just as standalone, but the standalone is used by some software (I have to upload the standalone in the software)