I want to convert an existing matlab function (lets call it foo.m) to a java library using the compiler toolbox. However, foo() uses multiple recursive calls to an existing java library (lets call it bar.jar) to compute its results. My questions are: Is this a use case the compiler toolbox can handle (the documentation seems to imply only a single entry point)? During compilation, would bar.jar be considered an external dependency or will it be embedded in the resulting foo.jar? Dependencies prevent me from easily translating foo.m to Java, so I would appreciate thoughts about this.

Compiling a Matlab function with a Java library dependency

2023 9 27

0 个回答

4 次查看（30 天）

0 个投票

I want to convert an existing matlab function (lets call it foo.m) to a java library using the compiler toolbox.

However, foo() uses multiple recursive calls to an existing java library (lets call it bar.jar) to compute its results.

My questions are:

Is this a use case the compiler toolbox can handle (the documentation seems to imply only a single entry point)?
During compilation, would bar.jar be considered an external dependency or will it be embedded in the resulting foo.jar?

Dependencies prevent me from easily translating foo.m to Java, so I would appreciate thoughts about this.

Tommy 2023-9-29

After a few days of tinkering, I have tentative answers to the above:

The compiler toolbox seems to have no issue with calling libraries using the standard javaaddpath() and import commands. I found that specifying a relative path to the library was the cleanest way to do this easily.
The external library does not need to be included as an explicit dependency in the compiler app, and does not seem to be included automatically in the compiled jar. You can do this and it still works, but you don't have to.

Hope this is helpful to someone other than myself.