Skip to main content
  • Home
  • Development
  • Documentation
  • Donate
  • Operational login
  • Browse the archive

swh logo
SoftwareHeritage
Software
Heritage
Archive
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

https://github.com/epiqc/ScaffCC
13 May 2025, 12:21:09 UTC
  • Code
  • Branches (10)
  • Releases (1)
  • Visits
    • Branches
    • Releases
    • HEAD
    • refs/heads/ScaffCC_OSX
    • refs/heads/master
    • refs/tags/2.2
    • refs/tags/5.0
    • refs/tags/v1.0
    • refs/tags/v1.0-beta.2
    • refs/tags/v2.0
    • refs/tags/v2.1
    • refs/tags/v3.0
    • refs/tags/v4.0
    • v3.1
  • 6bbaf7c
  • /
  • rkqc
  • /
  • doc
  • /
  • README
Raw File Download
Take a new snapshot of a software origin

If the archived software origin currently browsed is not synchronized with its upstream version (for instance when new commits have been issued), you can explicitly request Software Heritage to take a new snapshot of it.

Use the form below to proceed. Once a request has been submitted and accepted, it will be processed as soon as possible. You can then check its processing state by visiting this dedicated page.
swh spinner

Processing "take a new snapshot" request ...

Permalinks

To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.

  • content
  • directory
  • revision
  • snapshot
origin badgecontent badge Iframe embedding
swh:1:cnt:bbcb26792455df42df7b0bcb0206a1772684fc06
origin badgedirectory badge Iframe embedding
swh:1:dir:ca1f546d9b5b985713c217ed0cffc97bf3dbcdaa
origin badgerevision badge
swh:1:rev:66a79944ee4cd116b27bc1a69137276885461db8
origin badgesnapshot badge
swh:1:snp:7eb50f12cf990a0030724453139e994df238639f
Citations

This interface enables to generate software citations, provided that the root directory of browsed objects contains a citation.cff or codemeta.json file.
Select below a type of object currently browsed in order to generate citations for them.

  • content
  • directory
  • revision
  • snapshot
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Tip revision: 66a79944ee4cd116b27bc1a69137276885461db8 authored by Andrew Litteken on 28 September 2021, 15:30:02 UTC
Merge pull request #49 from AndrewLitteken/master
Tip revision: 66a7994
README
RevKit: A Toolkit for Reversible Circuit Design
Copyright (C) 2009-2013  The RevKit Developers
www.revkit.org
revkit@informatik.uni-bremen.de

CONTENTS
  * Requirements
  * SE Linux Enforcing Setting (for Fedora users only)
  * Build
  * Start
  * Documentation

REQUIREMENTS
  You need the following packages (by distribution):

  Ubuntu, Mint Linux: (for the Python Interface Ubuntu 9.10 or higher is required)
  $ sudo apt-get install build-essential cmake python-dev ipython python-qt4 python-numpy

  openSUSE:
  $ sudo zypper install gcc-c++ cmake python-devel IPython python-qt4 python-numpy

  Fedora:
  $ sudo yum install wget gcc-c++ cmake python-devel ipython PyQt4 numpy

  Further packages which are not available in the
  distrubition's package manager (as e.g. CUDD or PUMA)
  are downloaded and installed automatically from the bootstrap script.
  Boost is also required and will be downloaded and installed by default.
  If you prefer using the distributions boost version, please have a look at the RevKit users manual.

SE LINUX ENFORCING SETTING (for Fedora users only)
  You need to disable SE Linux enforcing to run RevKit in
  a python shell. There are two ways to do this, temporarily
  or permanently.

  Temporarily:
  $ sudo /usr/sbin/setenforce 0

  Permanently:
  Change "enforcing" to "disabled" in "/etc/selinux/config" and reboot.

BUILD

  The build process is divided into two scripts.
  First the RevKit environment is created using the bootstrap script.
  Afterwards the RevKit algorithms are built using the build script.
  This has the benefit of running the second script only if changes
  have been made on the algorithms but not on the environment.
  The bootstrap script should only be called once at the beginning.

  Do the following steps to build the RevKit environment

  $ ./make.py bootstrap

  This will download and compile all dependencies.
  In that process, compiling boost takes some time.
  If you already have installed boost using the distribution's
  package manager, the option -DBOOST_PATH can be used to
  specify its path, e.g. -DBOOST_PATH=/usr.
  Alternatively you can specify the boost include and libs path separately by using --boost, --boost-include-dir and --boost-lib-dir as arguements.

  After bootstraping the environment you are asked to run the build script.

  To run it manually just call

  $ ./make.py build

  This will build the whole RevKit suite including the core,
  algorithms, examples, and the Python bindings.
  The Python bindings enable the CLI to use RevKit
  like a shell. If the system cannot build the Python
  bindings or if they are not needed, they can be deactivated
  by calling

  $ ./make.py build -DBUILD_BINDINGS=OFF

  instead.

  The build script must be called at least once.
  You can use it for compiling the sources after changes have been made, but it is not necessary if your settings are unchanged: Alternatively just call

  $ make

  in the build directory.

START

  To start the RevKit GUI just run

  $ ./tools/gui/gui.py

  from the RevKit directory. This will open a GUI supporting all implemented algorithms.

  If you prefer starting RevKit via python, call

  $ ipython

  and enter

  In [1]: from revkit import *

  If you don't have ipython installed, python will also work.

  A couple of ready-to-use tools (in terms of Python scripts)
  are already available at ./tools.


DOCUMENTATION
  A user manual is available at doc/users/revkit_user_manual.pdf.

  All C++ documentation including
      - installation,
      - usage, and
      - full code documentation
  is available in the Doxygen documentation. The main page
  for the documentation is doc/devs/html/index.html. You can open the documentation
  e.g. by calling

  $ firefox doc/devs/html/index.html

  For generating the documentation on your own, call

  $ cd doc/devs
  $ ./doxygen.pl

Have Fun!

Software Heritage — Copyright (C) 2015–2025, The Software Heritage developers. License: GNU AGPLv3+.
The source code of Software Heritage itself is available on our development forge.
The source code files archived by Software Heritage are available under their own copyright and licenses.
Terms of use: Archive access, API— Contact— JavaScript license information— Web API

back to top