Arch Linux User Repository

Hi, I'm tackling the problem with the add-ons installation, where the installer can't write to /usr/local/MATLAB/R2022b. I think we should avoid manual chmods or chowns, as it would be easy to mess up with the permissions, so I created a matlab group with rwx permissions, which owns the tree starting at /usr/local/MATLAB/R2022b. The PKGBUILD sets up the correct permissions, so after installing MATLAB, you should just add yourself to that group, re-login and then you should be able to install add-ons. So far I'm able to start the installer, download the add-on archive, but when I get to Performing post-installation tasks. This may take a few minutes..., an error occurs, and the installer logs End - Unsuccessful Exception: java.lang.InterruptedException without further information.

If anyone wants to help me resolve this issue, here is the repo: https://github.com/Rubo3/matlab-aur/tree/addons.

I updated the PKGBUILD to MATLAB R2022b. Sorry it took so long. Here are the main changes:

• The dependencies have been updated according to namcap (thanks @sukanka), and are now managed via the matlab-meta meta package, now it's really easy to play around with them, as you don't have to rebuild the entire MATLAB package (thanks @bbaserdem). I still don't know the exact dependencies needed by MATLAB, as I don't use all its toolkits and whatnots. As always, please tell me if you find something.
• The MATLAB installer now outputs its logs in install.log, under the same directory of the PKGBUILD, so that you can check whether something went wrong even if it didn't fail (e.g. when you need a new license or installation key because the major version changed).
• I moved python-matlabengine to its own repo, which is built from upstream and works for the latest MATLAB versions. Currently it supports Python 3.9 and 3.10. If you have other needs, you can find the installation instructions here. Since the source files are still provided in your local MATLAB installation under $_instdir/extern/engines/python, building it and packaging it here was really just a convenience. I would like to know how many users of this PKGBUILD really need to spoof their Python version, so that we can reason about putting back that extra logic in the other PKGBUILD.
• I also removed the Mesa workaround and the optional compilers, are they still needed?

READ THE README FILE IN THE REPO. NO AUR HELPERS SUPPORTED. ONLY ARCHLINUX AS OS IS SUPPORTED. YOU SHOULD BE BUILDING THIS PACKAGE USING MAKEPKG, NOTHING ELSE WILL BE SUPPORTED. Please only post issues here AFTER you followed the README.md. located at the root of this repo: https://aur.archlinux.org/cgit/aur.git/tree/README.md?h=matlab Due to a lot of comments; my spam filter is removing AUR notifications which keeps me from responding timely to issues in packaging, please don't post if you don't do some troubleshooting yourself. If your skill level is not up to troubleshooting (or following simple instructions as laid out by the readme), just install matlab locally, without using this package.

• This PKGBUILD is NOT a minimal installation; as it has (hard) dependencies to gcc8 to force MATLAB to use system libraries. While generally not required; this PKGBUILD is trying to make MATLAB work with the system rather than with the mathworks-provided binaries. Currently it also does the python integration so that jupyter can be used with it.
• This will only work with 2020b version; and will not work with earlier (or later) versions.
• This PKGBUILD DOES NOT DOWNLOAD MATLAB FOR YOU. The EULA prevents redistribution of the software. Read the README.md file contained in the PKGBUILD repo. This is essentially a script to integrate an existing matlab installer with your archlinux system; it does NOT come with any software from Mathworks. You most likely cannot build this package using an AUR helper; you NEED to manually provide files; and to get the files you need a valid MATLAB licence. The process of fetching the files is described in detail in the README.md in the repo. (You can use any valid credentials to install the package using this PKGBUILD; including a licence file that does not match the machine; but you will need to reactivate matlab by using activate_matlab.sh with root privileges.)
• Current users; please help me test and trim the dependencies list, and submit your personal fixes for issues if you have them so they can be added to the PKGBUILD. (Cuda related contributions; if needed would be good as I don't have nvidia GPU's to test compatibility.)
• To use jupyter with matlab; you also need jupyter-matlab_kernel(-git).

I just moved all executables to /usr/local/bin, as I believe that inofficial packages shouldn't mess with /usr/bin for exactly such conflict reasons anyway. This "fixes" the conflict-problem, unless you rely on directly calling "mex" for whatever reason in your tex-workflow. (Usually, you'd use a building script for that anyway, which probably includes the full path.)

@noel: You can change the PKGBUILD link mex to /usr/bin/matlab-mex or similar. From inside MATLAB, you won't get any difference to normal usage of mex but you might have to point build tools to the right file if you build libraries using mex.

conflicts with texlive-bin -> /usr/bin/mex

For new users, notice that you have to follow the Wiki for using this pkg. right?

For Matlab 2017a, the optional dependency gcc47 can be updated to gcc49. (The corresponding AUR package also includes gfortran.)

Hi, I have minor problems installing the package with 2017a. In particular, some of the files referenced in the package() method of the PKGBUILD do not exist. Some shell output: https://pastebin.com/raw/3MN1p7iW The original content of my installer_input.txt: https://pastebin.com/raw/YNnjs3u4 The content of the installer_input.txt in the src-folder: https://pastebin.com/raw/k4SyVULs I hope you can help me out with this one, looks like a minor issue, but I don't know much about the matlab installation process... thanks. :) Edit: I finally had some time to look into it myself... solved it quite easily. I removed the "silent" option of the installer, then it told me that a license file was required. There was no license.dat available in our software repository, but a network.lic ... I renamed the file, enabled "_networkinstall" and yea, awesome.

@progwolff, I have harfbuzz 1.4.8-1 on my system and the GUI works fine

harfbuzz=1.4.6 is a runtime dependency. Without it, or with a higher version, the GUI fails to start.

I've just updated this and R2017a is working alright with this package for me now. Somehow Mathworks' hardware opengl support detection is wonky. I just run `matlab -nosoftwareopengl` to work around that.

Hey all, I've adopted this and I'll try to get it up to snuff on R2017a