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/virtualagc/virtualagc
25 December 2018, 16:55:25 UTC
  • Code
  • Branches (14)
  • Releases (0)
  • Visits
    • Branches
    • Releases
    • HEAD
    • refs/heads/20080615
    • refs/heads/Fictitious-1201
    • refs/heads/block1
    • refs/heads/counters
    • refs/heads/empty
    • refs/heads/gh-pages
    • refs/heads/luminary130
    • refs/heads/master
    • refs/heads/scenarios
    • refs/heads/schematics
    • refs/heads/wiki
    • refs/import/raw
    • refs/tags/20100220
    No releases to show
  • 22dd35c
  • /
  • BuildingTargets.md
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 ...

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
swh:1:cnt:701fe33559e6dfb9b5774602463abdb90009e3d2
origin badgedirectory badge
swh:1:dir:22dd35ca3bdb6355d3f9c5b92c85d524e80082ce
origin badgerevision badge
swh:1:rev:689b58c51d2268e9fc3a5c61aa74c9321891ddea
origin badgesnapshot badge
swh:1:snp:cdcd2bc43331a436e8c659ba93175ef7d7eb339b

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: 689b58c51d2268e9fc3a5c61aa74c9321891ddea authored by Google Code Exporter on 07 April 2015, 19:26:57 UTC
Migrating wiki contents from Google Code
Tip revision: 689b58c
BuildingTargets.md
![http://virtualagc.googlecode.com/svn/trunk/Apollo32.png](http://virtualagc.googlecode.com/svn/trunk/Apollo32.png)
# Building Virtual AGC Targets #

First obtain get a working copy of the sources from the Source tab.

## 1 Building for Linux ##

### 1.1 Linux Prerequisites ###
The following software packages are required:
  * gcc
  * pkg-config
  * autoconf
  * automake
  * glib-dev
  * libgtk, libgtk-dev (version 2.0 or higher)
  * readline-devel, (either curses or ncurses)
  * Allegro

### 1.2 Build Linux Software ###
To build the software change your active working directory to the location where you placed the virtualagc files ( e.g. cd 

<path>

/virtualagc ). From there execute the following four commands to consecutively configure your build environment, remove all the previous targets, build the new targets and install them (default: /usr/local). To change this install location use the --prefix=

<InstallDirectory>

 as an argument to the configure script.
```
configure
make clean
make
sudo make install
```

## 2 Building for Win32 ##

### 2.1 Win32 Prerequisites ###
To build under windows an extensive list of packages needs to be installed in order to build the simulation tools yaDEDA and yaDSKY. The gtk+ binaries and development packages can be downloaded from [The GTK+ Project](http://www.gtk.org/). If you are just interested in building the yaAGC, yaAGS and other command line tools then you do not need all gtk+ packages but you still need [POSIX Threads](http://sources.redhat.com/pthreads-win32) for Win32, the [GNU Readline](http://gnuwin32.sourceforge.net/packages/readline.htm) for Win32 library and the GNU Compiler tool set [MinGW](http://www.mingw.org/) with a basic set of UNIX tools packaged as MSYS (also hosted on the MinGW site). The following is a list of all packages that will enable a full Win32 build:

  * MinGW GNU compiler toolset
  * MSYS Base System
  * ATK Binaries and Dev packages
  * cairo Binaries and Dev packges
  * gettext-runtime Binaries and Dev packages
  * GLib Binaries and Dev packages
  * GTK+ Binaries and Dev packages
  * jpeg Binaries and Dev packages
  * GNU libiconv Binaries,Dev and DLL packages
  * libpng Binaries and Dev packages
  * Pango Binaries and Dev packages
  * pkg-config Tool binaries
  * tiff Binaries and Dev packages
  * Zlib Binaries and Dev packages
  * Readline Binaries
  * pthreads-win32 package

### 2.2 Win32 Setup ###
First install MinGW in its default location (i.e. C:\MinGW). Then install MSYS in its default location and make it aware of the MinGW location (as requested during install). Extract all the GTK+ packages to the MinGW as well as the readline package. From the pthreads library make sure to copy the shared libraries files (i.e. .dll) into the bin directory of MinGW and the header files (i.e. .h )and library (i.e. .a) into respectively the include and lib folder of MinGW. If the installers haven't done so make sure both the MinGW and MSYS bin directories are added to your search path.

### 2.3 Build Win32 Software ###
Change directory into the root of the virtualagc project sources and type:
```
make -f Makefile.Win32 all
make -f Makefile.Win32 install
```

back to top

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— Content policy— Contact— JavaScript license information— Web API