• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

cnf/H03-May-2022-16,66012,432

data/H03-May-2022-21

doc/H03-May-2022-15,44714,073

extern/H03-May-2022-122,94095,356

gap/H03-May-2022-13,11811,539

m4/H03-May-2022-10,2699,302

notebooks/H03-May-2022-334333

scripts/H03-May-2022-342252

src/H03-May-2022-6,6435,114

tst/H03-May-2022-15,74515,168

.VERSIONH A D03-May-20226 21

.covignoreH A D03-May-202229 43

.gaplint.ymlH A D03-May-202231 32

.mailmapH A D03-May-2022314 65

CHANGELOG.mdH A D03-May-202236.1 KiB738604

DockerfileH A D03-May-2022591 2010

GPLH A D03-May-202234.3 KiB675553

LICENSEH A D03-May-2022744 1813

Makefile.amH A D03-May-20224 KiB144111

Makefile.inH A D03-May-202268.8 KiB1,4391,288

PackageInfo.gH A D03-May-20228.3 KiB253226

README.mdH A D03-May-20224.4 KiB10378

VERSIONSH A D03-May-20221.3 KiB4745

aclocal.m4H A D03-May-202243.4 KiB1,2121,103

autogen.shH A D03-May-202240 31

configureH A D03-May-2022643.7 KiB21,08817,709

configure.acH A D03-May-20223.7 KiB150123

init.gH A D03-May-20221.8 KiB5548

makedoc.gH A D03-May-20221.1 KiB3934

read.gH A D03-May-20221.4 KiB4135

README.md

1[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.198140.svg)](https://doi.org/10.5281/zenodo.198140)
2[![Build Status](https://travis-ci.org/gap-packages/Digraphs.svg?branch=master)](https://travis-ci.org/gap-packages/Digraphs)
3[![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/gap-packages/digraphs/master)
4
5
6## README
7
8### Digraphs package for GAP
9
10#### Copyright (C) 2014-20 by Jan De Beule, Julius Jonušas, James D. Mitchell, Michael Torpey, Wilf A. Wilson et al.
11## Getting Digraphs
12
13To get the latest version of the package, download the archive file
14`digraphs-x.x.x.tar.gz` from the [Digraphs webpage][]. Then, inside the `pkg`
15subdirectory of your GAP installation, unpack the archive
16`digraphs-x.x.x.tar.gz`, using
17
18    gunzip digraphs-x.x.x.tar.gz; tar xvf digraphs-x.x.x.tar
19
20for example.  This will create a subdirectory `digraphs-x.x.x`.
21
22## Issues
23
24For questions, remarks, suggestions, and issues please use the
25[issue tracker](https://github.com/gap-packages/Digraphs/issues).
26
27## Installation
28
29It is assumed that you have a working copy of [GAP][] with version number 4.9.0
30or higher.  The most up-to-date version of GAP, and instructions on how to
31install it, can be obtained from the
32[main GAP webpage](https://www.gap-system.org).
33
34The following is a summary of the steps that should lead to a successful
35installation of Digraphs:
36
37* get the [IO](https://gap-packages.github.io/io) package version 4.5.1 or
38  higher.
39* get the [orb](https://gap-packages.github.io/orb) package version 4.8.2 or
40  higher.
41* **this step is optional:** certain methods in Digraphs require the
42  [Grape](https://gap-packages.github.io/grape/) package to be available; a
43  full list of these functions can be found in the first chapter of the manual.
44  To use these functions make sure that the Grape package version 4.8.1 or
45  higher is available.
46* download the package archive `digraphs-x.x.x.tar.gz` from the
47  [Digraphs webpage][].
48* unzip and untar the file `digraphs-x.x.x.tar.gz` using, for example,
49  ```
50    gunzip digraphs-x.x.x.tar.gz; tar xvf digraphs-x.x.x.tar
51  ```
52  which should create a directory called `digraphs-x.x.x`.
53* locate the `pkg` directory of your GAP directory, which contains the
54  directories `lib`, `doc` and so on. Move the directory `digraphs-x.x.x` into
55  the `pkg` directory (if it is not there already).
56* compile the kernel module; more details are given below.
57* start GAP in the usual way.
58* type `LoadPackage("digraphs");`
59
60## Compiling the kernel module
61
62The Digraphs package has a GAP kernel component written in C, which has to be
63compiled in order for the package to work.  This component contains certain
64low-level functions that the package requires.
65
66It is not possible to use the Digraphs package without compiling it.
67
68To compile the kernel component inside the `digraphs-x.x.x` directory, type
69
70    ./configure
71    make
72
73If you installed the package in a `pkg` directory other than the standard `pkg`
74directory in your GAP installation, then you have to do two things. Firstly,
75during compilation you have to use the option `--with-gaproot=PATH` of the
76`configure` script where `PATH` is a path to the main GAP root directory (if
77not given, the default `../..` is assumed).
78
79If you installed GAP on several architectures, then you must execute the
80configure/make step for each of the architectures. You can either do this
81immediately after configuring and compiling GAP itself on this architecture, or
82alternatively set the environment variable `CONFIGNAME` to the name of the
83configuration you used when compiling GAPbefore running `./configure`.  Note
84however that your compiler choice and flags (environment variables `CC` and
85`CFLAGS`) need to be chosen to match the setup of the original GAP compilation.
86For example, you have to specify 32-bit or 64-bit mode correctly!
87
88Digraphs vendors `bliss` and `planarity` libraries in the `extern` directory.
89If you wish to use your system copy of `bliss` or `planarity`, please use the
90configure options `--with-external-bliss` or `--with-external-planarity`, as
91appropriate.
92
93If you wish to install a
94[development version of the Digraphs package](https://github.com/gap-packages/Digraphs),
95then you must first run the command `./autogen.sh` before compilation. However,
96development versions of the package may be unstable, and we recommend using the
97most recently released version of the package when possible.
98
99Enjoy!
100
101[Digraphs webpage]: https://gap-packages.github.io/Digraphs
102[GAP]: https://www.gap-system.org
103