I've got errors (something works from terminal, but not from TeXWorks, TeXShop, TextMate, …)
Macports install package software#
On the other hand, a disadvantage is that some apps cannot find the latex software suit, as commented. With Macports on the other hand, you can consume less than 1GB or just a few GB depending on what you install. Homebrew-Cask just grabs the whole mactex distribution which can consume ~15GB on disk. Moreover, you can save a lot of disk space by having more fine-grained control over which TeX packages you install. Its latex integrates better & easier with other MacPorts packages.Įspecially, if you already use MacPorts, sticking to the MacPorts package makes it easy to maintain your ecosystem (like upgrading / uninstalling dependencies).
Macports install package update#
*note I found a issue in the brew/caskroom repo that might be related.įeel free to update this answer if it gets fixed ln -s /Library/TeX/Distributions/.DefaultTeX/Contents/Programs/texbin/pdflatex /usr/local/bin I considered disabling it with csrutil, but choose rather to try to symlink the required binaries into /usr/local/bin. Turns out that I cannot (even with root), create files in /usr on a modern Macintosh (since El Capitan), because of the System Integrity Protection. Great! I will just create a symbolic link to from that location to /usr/texbin. However, I am missing the pdflatex tool from command line, and that also produces errors in the TeXShop program:Īfter searching a little bit around, I found out that the missing utilities were actually bundled with MacTeX, and located in Library/TeX/Distributions/.DefaultTeX/Contents/Programs/texbin. That provided me with /Application/TeX, containing TeXShop program and the utilities. integration.īasically both are good solutions so it mostly depends on what else you do… I switched from macports to homebrew for reasons not at all related to TeX, hence my switch in TeX providers. Now I'm using homebrew and MacTeX, which is better integrated with MacOS X in general (fonts for instance). I used to use the macport-based texlive distribution, since it allowed me to avoid downloading stuff I didn't need (BibDesk or Excalibur for instance). However, if you need a package that is not pre-packaged by macports then you get absolutely no help (but I doubt that there are many). With macports, all the above mentioned packages can be installed/updated through the usual port install and port update commands. Macports' texlive port and MacTeX are both based on the latest TeXlive distribution, MacTeX is very complete ( ) whereas you have much more granularity with all the texlive-* ports of macports ( ). We recommend using a MacTeX distribution: Installing TeX from source is weird and gross, requires a lot of patches,Īnd only builds 32-bit (and thus can't use Homebrew deps on Snow Leopard.) Latex-mk latex2html latex2rtf pplatex rtf2latex2e BigSurError.Homebrew does not provide any version of LaTeX: $ brew search latex
Macports install package mac#
This webpage discusses issues related to installing packages on a Mac running Big Sur. This failure to see Apple's command line developer tools is a common failure for MacPorts apparently R's 'install.packages(.)' command suffers the same problem.
It downloaded and installed them (again). (I have installed these, both through Xcode's command 'Xcode-select -install' and by downloading the package for the command line tools and installing that 'by hand', so to speak), but I'm not going to argue with it, so I said yes. It still failed, but asked if I wanted to install the Command Line developer tools. I symlinked /opt/local/bin/clang-mp-13 to /usr/bin/clang and tried again. The 'system' clang is in /usr/bin/clang (installed by Xcode and its `command line' tools) is version 13, if clang -version is anything to go by. There is a /opt/local/bin/clang-12 installed by MacPorts. R C compiler used = /opt/local/bin/clang-mp-13
0 kommentar(er)
