MATLAB Central Newsreader - Matlab Toolbox Dependencies

Matlab Toolbox Dependencies

Yoav Mor — Wed, 20 Jun 2007 11:54:54 -0400

Hi,

I'm trying to compile a list with all the toolboxes needed by my
matlab program. The command "depfun" seems to be unreliable. Is there
an easier way to compile such a list?

Thanks.
Y.

Re: Matlab Toolbox Dependencies

Erik — Wed, 20 Jun 2007 13:41:57 -0400

Hi,
open the file in the MATLAB editor and go to Tools->Show
Dependency Report. For dependency report on all files in your current
directory you can run the dependency report from the Current
Directory browser.
HTH,
Erik

Yoav Mor wrote:
>
>
> Hi,
>
> I'm trying to compile a list with all the toolboxes needed by my
> matlab program. The command "depfun" seems to be unreliable. Is
> there
> an easier way to compile such a list?
>
> Thanks.
> Y.

Re: Matlab Toolbox Dependencies

sy — Wed, 20 Jun 2007 14:32:34 -0400

Erik wrote:
>
>
> Hi,
> open the file in the MATLAB editor and go to Tools->Show
> Dependency Report. For dependency report on all files in your
> current
> directory you can run the dependency report from the Current
> Directory browser.
> HTH,
> Erik
>
> Yoav Mor wrote:
>>
>>
>> Hi,
>>
>> I'm trying to compile a list with all the toolboxes needed by
my
>> matlab program. The command "depfun" seems to be unreliable. Is
>> there
>> an easier way to compile such a list?
>>
>> Thanks.
>> Y.

Alternatively, you can do the following:
restart Matlab
run your code
type "license inuse" (but with no quotes)
this will tell you what toolboxes were used while running your code.

SY

Re: Matlab Toolbox Dependencies

Kelly — Wed, 20 Jun 2007 14:56:41 -0400

Yoav Mor wrote:
>
>
> Hi,
>
> I'm trying to compile a list with all the toolboxes needed by my
> matlab program. The command "depfun" seems to be unreliable. Is
> there
> an easier way to compile such a list?
>
> Thanks.
> Y.

You can use my depfuntoolbox function:

<http://www.mathworks.com/matlabcentral/fileexchange/loadFile.do?objectId=14176&objectType=FILE>

It basically just parses the output of depfun, but it's an easy way
to see at a glance which toolboxes are really needed to run a
function, and also whether it uses any unofficial m or p files (e.g.
ones that you wrote, or ones from the File Exchange, etc).

Disclaimer: Yes, I've seen some crazy results from depfun in R2006b
beta for Intel Macs, and depfuntoolbox shows the same problem (since
it calls depfun). But I don't think any other operating systems have
this problem, so if you aren't on an Intel Mac, my function should
work fine.