install:macos:bundles

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
install:macos:bundles [2020/05/11 13:11] – created paffenholzinstall:macos:bundles [2021/01/23 13:52] (current) tbrysiewicz
Line 1: Line 1:
 ====== MacOS Bundles ====== ====== MacOS Bundles ======
  
-=== Installing the App Bundle ===+==== Installing the App Bundle ====
  
 Please make sure you download the correct version on the download page.  Please make sure you download the correct version on the download page. 
Line 11: Line 11:
   * Drag the ''polymake'' application to a folder of your choice on your hard disk (the common choice would be the ''/Applications'' folder).   * Drag the ''polymake'' application to a folder of your choice on your hard disk (the common choice would be the ''/Applications'' folder).
   * Start ''polymake'' by double clicking the icon.   * Start ''polymake'' by double clicking the icon.
 +
 +If you receive a pop-up when clicking the ''polymake'' icon telling you the 'developer cannot be verified', click cancel. Then open system preferences -> security + privacy and click 'open anyway'.
  
 The disk image also contains a ''README'' file with some more detailed instructions, and the corresponding sources.  The disk image also contains a ''README'' file with some more detailed instructions, and the corresponding sources. 
Line 20: Line 22:
  
  
-=== Jupyter Notebooks with the Bundle ===+==== Jupyter Notebooks with the Bundle ====
  
 The bundle comes with a still experimental support for starting polymake in a jupyter notebook. To use it you need to install python3 and jupyter yourself and make sure polymake can find both in the path (usually python is found with the default path, only jupyter needs to be added. You have two options for this: add the path to the ''$PATH'' variable in ''.bash_profile'', or add the path to the variable ''POLYMAKE_ADD_PATH'' in the file''$HOME/.polymake-macbundle/bundle.config'' created after the first start of the bundle.) To use polymake in a jupyter notebook, start the bundle at least once and exit, then set ''POLYMAKE_START_IN_JUPYTER'' to 1 in ''$HOME/.polymake-macbundle/bundle.config'', and start polymake again. It should ask your confirmation to install the kernel and then start a browser with jupyter.  The bundle comes with a still experimental support for starting polymake in a jupyter notebook. To use it you need to install python3 and jupyter yourself and make sure polymake can find both in the path (usually python is found with the default path, only jupyter needs to be added. You have two options for this: add the path to the ''$PATH'' variable in ''.bash_profile'', or add the path to the variable ''POLYMAKE_ADD_PATH'' in the file''$HOME/.polymake-macbundle/bundle.config'' created after the first start of the bundle.) To use polymake in a jupyter notebook, start the bundle at least once and exit, then set ''POLYMAKE_START_IN_JUPYTER'' to 1 in ''$HOME/.polymake-macbundle/bundle.config'', and start polymake again. It should ask your confirmation to install the kernel and then start a browser with jupyter. 
  
  
-=== Using the Bundle for Polymake.jl in Julia ===+==== Using the Bundle for Polymake.jl in Julia ====
  
 On Mac OS 10.11 you need at least clang version 8 (for Julia, and thus also for polymake in Julia).  On Mac OS 10.11 you need at least clang version 8 (for Julia, and thus also for polymake in Julia). 
Line 42: Line 44:
 Now start julia and hopefully it downloads and compiles Polymake.jl, linking it against the bundle. Now start julia and hopefully it downloads and compiles Polymake.jl, linking it against the bundle.
  
-=== Compiling your own version of the bundle ===+==== Compiling your own version of the bundle ====
  
 You can build your own version of the bundle with the following steps. The only prerequisite is ''Xcode'', which you can easily install via the app store. Then open a Terminal (in the utilities folder of Applications) and type the following commands (if you want to you can first switch into a different folder): You can build your own version of the bundle with the following steps. The only prerequisite is ''Xcode'', which you can easily install via the app store. Then open a Terminal (in the utilities folder of Applications) and type the following commands (if you want to you can first switch into a different folder):
Line 54: Line 56:
  
 The same usage hints as for the precompiled binaries above apply also to this version. The same usage hints as for the precompiled binaries above apply also to this version.
 +
 +
 +==== Packages used together with polymake (partially outdated) ====
 +
 +=== JavaView ===
 +
 +Download JavaView (you need the Unix version) from this [[http://www.javaview.de/download/|page]] and unzip it into some directory on your computer.
 +
 +If you are going to use JavaView on its own (it can much more than only serving as a showcase for polymake!), you'll have to prepare its start script ''javaview'', which is located in the sub-directory ''bin/'' . You have to make it executable with ''chmod u+x bin/javaview'' You should place the full path to this script in the ''$PATH'' variable of your terminal (and remember to change this if you move your javaview installation to a different place).  Then start polymake and execute ''%%reconfigure("javaview.rules")%%'' .  This should automatically find the script and start JavaView once for testing - just click its window away.
 +
 +If you are only interested in polymake interface to JavaView, then execute the ''reconfigure'' command right after unpacking the ZIP archive; now you will be asked to enter the location of the unpacked JavaView manually.
 +
 +=== POV-Ray ===
 +
 +''polymake'' has been tested with the povray version that comes with Fink. The Mac OS X version seems to have problems with the newer Intel Macs.
 +
 +''povray'' is quite restrictive with files it reads and writes. So before you can use ''povray'' with ''polymake'' you have to allow it to read from the ''povray'' sub-directory of your polymake-root directory, and from the temporary directory ''polymake'' places temporary files into. It should be something starting with ''/private/var/folders''. If you don't now where it is, you can call
 +<code>$c=cube(2); povray($c->VISUAL);</code>
 +in a ''polymake'' shell. It will tell you something like ''Parse Error: Reading from ... is not permitted''. Place the given directory in the ''povray.conf'' file (The error message will also tell you where you can find it). Add a line <code>read* = <dir></code> for both the temp dir and the povray dir of polymake (You might need to use ''sudo'' to be allowed to write into that file.)
 +
 +If you use the Fink version of povray and installed polymake into its standard location, then the povray.conf file should be in <code>/sw/etc/povray/3.6/povray.conf</code> and you should add the lines <code>read* = /usr/local/share/polymake/povray
 +read* = /private/var/folders
 +</code> 
 +at the end of the file.
 +
 +=== Porta ===
 +
 +Before compiling porta you should significantly increase the length of the char array fname in ''porta.c'', say from 20 to 100. The variable contains the name of the input file, which ''polymake'' places in a temporary directory. The name of the directory is significantly longer on a Mac than on a Linux system.  
 +
 +Before you install porta you should also consider the remarks about porta on the [[:external_software|external software page]]
 +
  
  • install/macos/bundles.1589202669.txt.gz
  • Last modified: 2020/05/11 13:11
  • by paffenholz