It is not possible to remove file from Compiler Project in 2016b

After deleting a file in the deploy tool, along with documentation, the file is automatically inserted back within a few seconds. Then it is included in compiled binary. Rel. R2016b.

Is it possible to remove the file permanently?

[Kojiro Saito]

I cannot reproduce the issue. After deleting required files, they don't appear again.

Could you tell me the reproduction steps? If possible, screenshots are welcome.

[Adam]

I assume it is one of the main file's dependencies so that the auto dependency-checker sees it is missing and adds it back in.

[Carbol]

I have exactly the same problem: I'm using a mat-file to dynamically change calibration data for a compiled GUI - and this compiler change, obviously introduced with 2016b, is really annoying!

I just filed a support case regarding this problem...

[Kaixiang Wang]

@Carsten I have the same problem here. I am using 2017a. I've been searching for the solution everywhere but just couldn't find it. Have you solved your problem?

[Kaixiang Wang]

I ended up manually deleting the depended mat-files from my disk, and restore them after compilation. Then it works.

WTF MATLAB!

[Adam]

I still don't get what the issue is here. I have never seen files added automatically that are not dependencies of your code. If it is a dependency then why shouldn't it be added and, conversely, if you don't want it why is it a dependency of the code? Or am I missing something? No-one has given any meaningful details despite 3 people saying they have the same problem!

[Christoph Kern]

I have this problem too. It's true that the program does rely on the file in question. However, this is a configuration file that I would like the user to be able to edit manually. Therefore, rather than including it in the compiled software package, I would like it to show up in the list of 'Files installed for your end user'.

[Adam]

I just tested this out actually and was surprised that a .mat file gets picked up as a dependency so I guess this was a change from years ago.

If you refer to the file you are loading via a relative path formed from e.g. a function then it does not get picked up as a dependency and you can add it where you wish.

I have a few files that I ship for end users though they vary in how I choose to do them. At last one I actually have a class whose function creates the file at the user end if it doesn't exist, thus eliminating the need to include an actual .mat or .txt file.

Others though I include in code with something like:

configFilename = fullfile( getMatlabHomeDir( ), 'config.txt' );

where getMatlabHomeDir( ) returns a folder that, in my case is defined in an environment variable that my end users must set, but equally I have other functions that make use of

doc ctfroot

with an isdeployed flag to return me a directory that I can use for a relative path depending whether I am in a deployed application or in Matlab itself.

doc mfilename

is also useful for this kind of thing to give relative paths. In a few places I have a function in a folder whose only purpose is to return me the address of the folder it sits in for me to use as a relative path whether my code is deployed or not.

[Kaixiang Wang]

@Adam Thanks for the reply. My understanding of your approach is, basically, to fool the dependency analyzer so it does not know the path to the data files? Quite a smart idea. I will give it a try.

Answer 1

[Soma Ardhanareeswaran]

I agree with Adam, the Dependency Analysis step would pick up the dependent files that are found in the current directory or from the MATLAB path and get included into the compiler project.

[Jan]

My compiled application read a parameter file from its current directory at its startup. Time to time I needed to change the parameter file so I just simply replaced the parameter file. It was working until 2016b. With the 2016b the parameter file is included in the compiled exe file and application is insensitive to any change of the parameter file in application current directory :(

[Kaixiang Wang]

@Jan I have the same problem here. I am using 2017a. I've been searching for the solution everywhere but just couldn't find it. Have you solved your problem?

[Kaixiang Wang]

I ended up manually deleting the depended mat-files from my disk, and restore them after compilation. Then it works.

WTF MATLAB!

[Jan]

Dear Kaixiang, there was no response from MathWorks or a solution for the problem. To work around I have added a possibility to load a new parameter file by a user.

The parameter file read by the program during its startup is located in a temporary directory of the user. There it is unpacked during the first program run. If you will replace the parameter file in this temporary dir it will be read correctly.

[Kaixiang Wang]

@Jan Hi Jan, thanks for replying! Eventually I managed to find a few ways, and yes, asking the user for an input location is one of them.

The other approach you mentioned could be a good idea too, but unfortunately not practical for my case. My .mat file is generated by another program which would not know the temp directory (across different machines).

Anyway, it is nice to discuss with you! Cheers!

Answer 2

[Mike Smith]

Hello,

I know it'a been a while since this question was posted but I thought I'd comment on my experience with this to keep it all in the same thread. I am using Matlab 2018a with deploytool to make a standalone application. I have a few lines in the app startup function that look for a file "locationOfConfig.m" that represents a Matlab variable (string) that is the absolute path to the actual configuration file. It uses this path to check for the file and if its not there the app launches a little configuration window where the user can make/edit the config file. Once the configuration window is filled out, the configuration file location ("locationOfConfig.m") file and the actual configuration file ("config.txt") are written.

Anyway, during compiling, it was annoying because my "locationOfConfig.m" file kept being automatically incorporated into the "Files required for your application to run" section. But I need the user to be able to generate their own unique file upon installation...not use my absolute path! To work around this, I simply save my local "locationOfConfig.m" in a location that is not set in the official Matlab path (Set Path) and then Matlab doesn't see it upon searching for dependencies. This allows me to compile without the Matlab-declared "dependent" file.

Hope that helps somebody out there.