@jebej I’m trying to get it to work on Linux on 1.0, and it looks like mexjulia never got full Linux functionality working.
The ideal solution would be to write a mex file that can call an arbitrary Julia code like @mbauman suggests. This is what mexjulia attempted to do, but there’s so much work to be done to bring that project back up to speed that it would probably be best to write a whole new piece of software to handle calling Julia.
There are two problems that I see complicating this task:
- The mex file will have to be able to call arbitrary Julia code and return useful data. Calling it isn’t the hard part, returning data is. You either have to detect the outputs of the function and account for that within one mex file, or you have to have multiple mex files for each type of data that can be returned.
- You need to have a Julia process running in the background that can be called by several Matlab calls successively. If Julia has to start and stop on each function call, you lose any performance gains that you would expect from using Julia.
I may have this wrong since I’m not very experienced in C (or Julia), but that was the conclusion I came to when I first looked at this problem a couple of months ago.