Doc d'install...
This commit is contained in:
Olivier Sirol
parent
33d4499962
commit
c1c9ab696b
|
|
@ -0,0 +1,184 @@
|
|||
# Alliance VLSI CAD System
|
||||
#
|
||||
# Home page : http://www-asim.lip6.fr/alliance/
|
||||
# E-mail support : mailto:alliance-support@asim.lip6.fr
|
||||
# ftp sites : ftp://ftp.lip6.fr/lip6/softs/alliance/
|
||||
# or ftp://ftp-asim.lip6.fr/pub/alliance/
|
||||
#
|
||||
# $Id: CHANGES,v 1.1 1999/05/31 17:11:53 czo Exp $
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
ALLIANCE release 3.2b (15/12/97)
|
||||
|
||||
1/ Easy install
|
||||
|
||||
A "configure" script is now available to configure
|
||||
Alliance on any UNIX system
|
||||
|
||||
2/ New driver :
|
||||
|
||||
Support to VERILOG netlist as been added.
|
||||
Only driver exits. This means you can save your
|
||||
netlists to VERILOG format 'vlg'
|
||||
|
||||
3/ New names :
|
||||
|
||||
- Logic has been splited in 3 parts,
|
||||
. bop : boolean optimizer (logic -o)
|
||||
. scmap : Std cell mapping (logic -s)
|
||||
. c4map : CCCC mapping (logic -c)
|
||||
|
||||
- Desb is replaced by yagle
|
||||
|
||||
- Alligator is replaced by fpmap (X4000)
|
||||
|
||||
- Netoptim is replaced glop
|
||||
|
||||
4/ Cells libraries
|
||||
|
||||
The tree of directories containing the cells
|
||||
libraries has been simplified
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
ALLIANCE release 3.2 (17/05/97)
|
||||
|
||||
|
||||
1/ GRAPHICAL PATTERN VIEWER
|
||||
|
||||
In order to see the patterns resulting from a simulation,
|
||||
the XPAT tools has been developped.
|
||||
|
||||
2/ GRAPHICAL FSM VIEWER
|
||||
|
||||
In order to see the state's graph of an FSM the XFSM tools has
|
||||
been developped.
|
||||
|
||||
3/ RECTANGLE LAYOUT VIEWER
|
||||
|
||||
Now, DREAL is also a real layout editor.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
ALLIANCE release 3.0 (17/05/94)
|
||||
|
||||
1/ FPGA SYNTHESIS
|
||||
|
||||
A logic synthesis tools that maps on FPGA is now available.
|
||||
It works for X3000 devices
|
||||
|
||||
2/ FLOOR-PLAN ROUTING
|
||||
|
||||
Binaries of the CHEOPS router from BULL are available for sparc.
|
||||
|
||||
3/ TIMING ANALYSIS
|
||||
|
||||
The static timing analisys tools TAS is finally available.
|
||||
It can be targetted to several processes though the use of a technological
|
||||
file suffixed `elp'.
|
||||
|
||||
4/ RECTANGLE LAYOUT VIEWER
|
||||
|
||||
In order to see the layout resulting from a symbolic to real translation,
|
||||
the DREAL tools has been developped.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
ALLIANCE release 2.0 (14/02/94) versus ALLIANCE 1.2
|
||||
|
||||
1/ SYMBOLIC LAYOUT EDITOR
|
||||
|
||||
The symbolic layout editor ALC has been replaced by GRAAL.
|
||||
GRAAL provides the same functionnalities than ALC, but is much
|
||||
more reliable. GRAAL support both CMOS and GaAs symbolic layout.
|
||||
|
||||
> man graal
|
||||
|
||||
2/ DESIGN RULE CHECKER
|
||||
|
||||
The Design Rule Checker VERSATIL has been replaced by DRUC.
|
||||
DRUC provides the same functionnalities than VERSATIL.
|
||||
A hierarchical version will be distributed in the next ALLIANCE release.
|
||||
|
||||
> man druc
|
||||
|
||||
3/ LOGIC SYNTHESIS
|
||||
|
||||
The logic synthesis tool LOGIC has been strongly improved.
|
||||
The new tool NETOPTIM is a gate-level net-list optimiser
|
||||
that allows to minimize delays in a synthesized gate net-list.
|
||||
The Finite-state-machine synthesizer SYF allows to describe and
|
||||
synthesize high complexity FSM (more than 100 states)
|
||||
It is possible to describe hierachical FSM using stack (subroutines).
|
||||
|
||||
> man logic
|
||||
> man syf
|
||||
> man netoptim
|
||||
|
||||
4/ DATA-PATH COMPILER
|
||||
|
||||
FPGEN is a data-path compiler using a dedicated macro-cells library.
|
||||
DPR is the place and route tool that creates optimized data-path blocks
|
||||
from the gate net-list generated by FPGEN.
|
||||
|
||||
> man fpgen
|
||||
> man dpr
|
||||
|
||||
5/ PARAMETERIZED MACRO-CELLS
|
||||
|
||||
Six parametrized generators are part of this release:
|
||||
|
||||
> man rsa # fast adder generator
|
||||
> man bsg # barrel shifter generator
|
||||
> man amg # multiplier generator
|
||||
> man rfg # register file generator
|
||||
> man grog # high speed ROM generator
|
||||
> man rage # static RAM generator
|
||||
|
||||
6/ PROCEDURAL LAYOUT DEBUGGER
|
||||
|
||||
The graphic debugger GENVIEW allows to debug custom blocks
|
||||
described with the procedural language GENLIB.
|
||||
It makes possible to design new parameterized generators, using the
|
||||
GENLIB language.
|
||||
|
||||
> man genview
|
||||
|
||||
7/ POSTSCIPT DRIVER
|
||||
|
||||
The postscript driver MBK2PS has been replaced by L2P, in order to
|
||||
obtain a printable postscript file from a cell layout.
|
||||
This tool accept not only symbolic layout (.ap files) but also
|
||||
physical layout (.cif or .gds files).
|
||||
|
||||
> man l2p
|
||||
|
||||
8/ FLOOR-PLAN ROUTER
|
||||
|
||||
There is no floor-plan router in this release.
|
||||
If you need to interconnect two blocks, you can use the BBR tool
|
||||
that is actually a simple gridless channel router.
|
||||
|
||||
> man bbr
|
||||
|
||||
9/ FILE FORMATS
|
||||
|
||||
Both file formats .ap (symbolic layout) and .al (net-list)
|
||||
have been modified, with upward compatibility: all files
|
||||
created with ALLIANCE release 1.2 are readable and usable with
|
||||
ALLIANCE release 2.0.
|
||||
|
||||
> man ap
|
||||
> man al
|
||||
|
||||
10/ PROCESS MAPPING
|
||||
|
||||
The S2R tool that performs the physical mapping to a target process
|
||||
has been documented: the procedure to parameterize the technology
|
||||
file is described in the doc/misc/process_mapping.ps file.
|
||||
The technology file format has been modified.
|
||||
|
||||
> man s2r
|
||||
> man prol
|
||||
|
||||
# EOF
|
||||
|
|
@ -0,0 +1,288 @@
|
|||
# Alliance VLSI CAD System
|
||||
#
|
||||
# Home page : http://www-asim.lip6.fr/alliance/
|
||||
# E-mail support : mailto:alliance-support@asim.lip6.fr
|
||||
# ftp sites : ftp://ftp.lip6.fr/lip6/softs/alliance/
|
||||
# or ftp://ftp-asim.lip6.fr/pub/alliance/
|
||||
#
|
||||
# $Id: FAQ,v 1.1 1999/05/31 17:11:53 czo Exp $
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
FAQ (Frequently Asked Questions)
|
||||
This file contains the basic pointers to
|
||||
the different documents or manuals found in this release.
|
||||
|
||||
Question 1: What is ALLIANCE ?
|
||||
Question 2: What is ALLIANCE general copyright policy ?
|
||||
Question 3: How to install ALLIANCE ?
|
||||
Question 4: How to get started ?
|
||||
Question 5: What are the differences with the previous releases ?
|
||||
Question 6: What is the supported VHDL subset ?
|
||||
Question 7: What is the available online documentation ?
|
||||
Question 8: Where are defined the symbolic layout rules ?
|
||||
Question 9: How is performed the mapping to a target process ?
|
||||
Question 10: How can I get a complete paper documentation ?
|
||||
Question 11: What are the supported file formats ?
|
||||
Question 12: How can I get in touch with the ALLIANCE team ?
|
||||
|
||||
|
||||
Question 1: What is ALLIANCE ?
|
||||
------------------------------
|
||||
|
||||
You can read a general description of the ALLIANCE tools and libraries
|
||||
by printing the PostScript files overview.ps located in the root
|
||||
directory:
|
||||
|
||||
> lpr overview.ps
|
||||
|
||||
|
||||
Question 2: What is ALLIANCE general copyright policy ?
|
||||
-------------------------------------------------------
|
||||
|
||||
"Alliance VLSI CAD System" is free Software.
|
||||
|
||||
Unlike versions of Alliance up to 3.1 that where released
|
||||
including sources, version 3.2 and up will not be available
|
||||
with the source code.
|
||||
|
||||
Source is however still available, but only upon request to
|
||||
alliance-support@lip6.fr. The release of the source is now
|
||||
subject to a non disclosure agreement.
|
||||
|
||||
You are welcome to use the software package even for commercial
|
||||
designs whithout any fee. You are just required to mention :
|
||||
"Designed with Alliance CAD system"
|
||||
|
||||
> more LICENCE
|
||||
|
||||
Question 3: How to install ALLIANCE ?
|
||||
-------------------------------------
|
||||
|
||||
Binary packcages are available for :
|
||||
- i386 Linux_elf
|
||||
- sparc SunOS 4.1.1
|
||||
- sparc Solaris 5.5.1
|
||||
To install Alliance follow the steps written in README
|
||||
|
||||
> more README
|
||||
|
||||
Question 4: How to get started ?
|
||||
--------------------------------
|
||||
|
||||
You can find 3 separate tutorials in the tutorials directory:
|
||||
(Read overview.ps)
|
||||
|
||||
1/ ADDACCU
|
||||
The design of a very simple chip (adder/accumulator) to get started
|
||||
with the ALLIANCE tools.
|
||||
|
||||
>cd tutorials/addaccu
|
||||
|
||||
2/ AMD2901
|
||||
The design of the 4 bits AMD2901 processor, from the VHDL specification to
|
||||
the CIF layout, using the ALLIANCE portable standard cells library.
|
||||
|
||||
>cd tutorials/amd2901
|
||||
|
||||
3/ Data Path
|
||||
Building simple data paths using on a procedural data path generator
|
||||
(fpgen) and a data path place and route tool (dpr).
|
||||
|
||||
>cd tutorials/fitpath
|
||||
|
||||
Question 5: What are the differences with the previous releases ?
|
||||
----------------------------------------------------------------
|
||||
|
||||
The new features of this release are described in the CHANGES file:
|
||||
|
||||
> more CHANGES
|
||||
|
||||
Question 6: What is the supported VHDL subset ?
|
||||
-----------------------------------------------
|
||||
|
||||
You can find a general presentation of the VHDL subset by issuing the
|
||||
following commands:
|
||||
|
||||
> man vhdl
|
||||
|
||||
This gives you an hint about the supported VHDL subset.
|
||||
There is actually three separate architectures types: "Structural",
|
||||
"Data-flow", and "Finite-State-Machine"
|
||||
|
||||
> man vst
|
||||
|
||||
This gives you the VHDL subset supported for structural descriptions.
|
||||
|
||||
> man vbe
|
||||
|
||||
This gives you the data-flow behavioral subset supported by the simulator
|
||||
ASIMUT, the logic synthesis tools BOP and SCMAP and the formal prover PROOF.
|
||||
|
||||
> man fsm
|
||||
|
||||
This gives you the VHDL subset used for Finite-State-Machine description
|
||||
and supported by the FSM synthesis tool SYF.
|
||||
|
||||
Question 7: What is the available online documentation ?
|
||||
--------------------------------------------------------
|
||||
|
||||
Each tools has its own manual.
|
||||
All the tools rely on the use of environment variables: all the relevant
|
||||
variables are listed in the `ENVIRONMENT VARIABLES' section of the manual
|
||||
page.
|
||||
|
||||
1) tools
|
||||
--------
|
||||
|
||||
|
||||
> man asimut # VHDL simulator
|
||||
> man bbr # channel router
|
||||
> man dpr # data-path place & route
|
||||
> man dreal # real layout viewer
|
||||
> man druc # design rule checker
|
||||
> man fpgen # procedural data-path generation language
|
||||
> man fpmap # logic synthesis tool for FPGA
|
||||
> man genlib # procedural net-list generation language
|
||||
> man genpat # procedural pattern generation language
|
||||
> man genview # interactive block genreator debugger
|
||||
> man graal # graphic layout editor
|
||||
> man l2p # layout to postcript translation tool
|
||||
> man bop # boolean optimizer
|
||||
> man lvx # net-list comparator
|
||||
> man lynx # layout extractor
|
||||
> man glop # net-list optimiser
|
||||
> man proof # VHDL description's formal proover
|
||||
> man ring # router between core & pads
|
||||
> man s2r # symbolic layout to real mask expander
|
||||
> man scmap # standard cell mapping
|
||||
> man scr # standard cells place & route
|
||||
> man syf # finite state machine synthesis tool
|
||||
> man tas # static timing analyser
|
||||
> man yagle # functional abstractor
|
||||
|
||||
2) cell libraries
|
||||
-----------------
|
||||
|
||||
> man sclib # standard cells library
|
||||
> man dplib # data path cells library
|
||||
> man fplib # data path cells library
|
||||
> man padlib # pad library
|
||||
> man rsa # fast adder generator
|
||||
> man bsg # barrel shifter generator
|
||||
> man amg # multiplier generator
|
||||
> man rfg # register file generator
|
||||
> man grog # high speed ROM generator
|
||||
> man rage # static RAM generator
|
||||
|
||||
3) ALLIANCE file formats
|
||||
------------------------
|
||||
|
||||
> man vhdl # VHDL overview
|
||||
> man vst # VHDL subset for net-list
|
||||
> man vbe # VHDL subset for data-flow
|
||||
> man fsm # VHDL subset for finite-state-machine
|
||||
> man al # internal ALLIANCE netlist
|
||||
> man ap # internal ALLIANCE symbolic layout
|
||||
> man pat # internal ALLIANCE pattern description
|
||||
|
||||
4) miscellaneous
|
||||
----------------
|
||||
|
||||
> man catal # use of the catalog file
|
||||
> man prol # technology file
|
||||
> man mbkenv # main environement variables
|
||||
|
||||
|
||||
Question 8: Where are defined the symbolic layout rules ?
|
||||
----------------------------------------------------------
|
||||
|
||||
The symbolic layout rules are specified in the Design Rule Checker
|
||||
documentation:
|
||||
|
||||
> man druc
|
||||
|
||||
Question 9: How is performed the mapping to a target process ?
|
||||
---------------------------------------------------------------
|
||||
|
||||
The actual conversion is performed by the s2r tool:
|
||||
|
||||
> man s2r
|
||||
|
||||
If you want to parameterize the S2R tool to a new target technology,
|
||||
you must write a technology file. The method is described in the
|
||||
postscript file doc/misc/process_mapping.ps
|
||||
|
||||
> lpr doc/misc/process_mapping.ps
|
||||
|
||||
Question 10: How can I get a complete paper documentation ?
|
||||
-----------------------------------------------------------
|
||||
|
||||
We are making a printed documentation of all manuals of the
|
||||
ALLIANCE tools. It will be available soon.
|
||||
|
||||
|
||||
Question 11: What are the supported file formats ?
|
||||
--------------------------------------------------
|
||||
|
||||
ALLIANCE tools are interfaced to generic data-structures that
|
||||
support various standard file formats, thanks to a set of
|
||||
specialized parsers/drivers.
|
||||
UNIX environment variables are used to select one particular file format.
|
||||
For a given entity, the file format is defined by the file extension.
|
||||
|
||||
1/ symbolic layout view
|
||||
|
||||
ALLIANCE .ap INPUT OUTPUT
|
||||
COMPASS .cp INPUT OUTPUT
|
||||
|
||||
2/ physical layout view
|
||||
|
||||
CIF .cif OUTPUT
|
||||
GDSII .gds OUTPUT
|
||||
|
||||
3/ netlist view
|
||||
|
||||
ALLIANCE .al INPUT OUTPUT
|
||||
SPICE .spi INPUT OUTPUT
|
||||
EDIF 2.0 .edi INPUT OUTPUT
|
||||
VHDL .vst INPUT OUTPUT
|
||||
COMPASS .hns INPUT OUTPUT
|
||||
HILO .cct OUTPUT
|
||||
VERILOG .vlg OUTPUT
|
||||
|
||||
4/ behavioural view
|
||||
|
||||
VHDL (data-flow) .vbe INPUT OUTPUT
|
||||
VHDL (FSM) .fsm INPUT
|
||||
|
||||
|
||||
Question 12: How can I get in touch with the ALLIANCE team ?
|
||||
------------------------------------------------------------
|
||||
|
||||
Look at the Alliance support Web pages
|
||||
at http://www-asim.lip6.fr/alliance/support
|
||||
|
||||
You may get ALLIANCE by two distinct means:
|
||||
|
||||
1) by anonymous FTP at ftp://ftp.lip6.fr/lip6/softs/alliance/
|
||||
|
||||
2) by sending a blank tape (we can write DC 600A 60 MBytes,
|
||||
DC 6150 150 MBytes and ExaByte 8mm 2,3 GBytes) or a ZIP 100
|
||||
or blank CD-ROM with your complete affiliation to the
|
||||
following address:
|
||||
|
||||
Laboratoire ASIM/LIP6
|
||||
Tour 55-65, 2eme etage
|
||||
Université Pierre et Marie Curie
|
||||
4, Place Jussieu 75252 Paris Cedex 05,
|
||||
France
|
||||
|
||||
Fax : 33 1 44 27 62 86
|
||||
Home page : http://www-asim.lip6.fr/alliance/support
|
||||
E-mail support : mailto:alliance-support@asim.lip6.fr
|
||||
ftp sites : ftp://ftp.lip6.fr/lip6/softs/alliance/ (faster mirror site)
|
||||
: ftp://asim.lip6.fr/pub/alliance/ (primary site)
|
||||
|
||||
|
||||
# EOF
|
||||
|
|
@ -0,0 +1,101 @@
|
|||
# Alliance VLSI CAD System
|
||||
#
|
||||
# Home page : http://www-asim.lip6.fr/alliance/
|
||||
# E-mail support : mailto:alliance-support@asim.lip6.fr
|
||||
# ftp sites : ftp://ftp.lip6.fr/lip6/softs/alliance/
|
||||
# or ftp://ftp-asim.lip6.fr/pub/alliance/
|
||||
#
|
||||
# $Id: LICENCE,v 1.1 1999/05/31 17:11:53 czo Exp $
|
||||
|
||||
|
||||
|
||||
ALLIANCE BINARY PACKAGE LICENCE AGREEMENT
|
||||
|
||||
|
||||
|
||||
Copyright 1990,97 ASIM/LIP6/UPMC
|
||||
|
||||
"Alliance VLSI CAD System" is free Software.
|
||||
|
||||
Unlike versions of Alliance up to 3.1 that where released including
|
||||
sources, version 3.2 and up will not be available with the source
|
||||
code.
|
||||
|
||||
Source is however still available, but only upon request to
|
||||
alliance-support@lip6.fr. The release of the source is now subject to
|
||||
a non disclosure agreement.
|
||||
|
||||
You are welcome to use the software package even for commercial
|
||||
designs whithout any fee. You are just required to mention : "Designed
|
||||
with Alliance CAD system"
|
||||
|
||||
Permission to use, copy, and distribute this software and its
|
||||
documentation for any purpose is hereby granted without fee, provided
|
||||
that the above copyright notice appear in all copies and that the
|
||||
package is not modified.
|
||||
|
||||
|
||||
DISCLAIMER OF WARRANTY. Free of charge Software is provided on an "AS
|
||||
IS" basis, without warranty of any kind, including without limitation
|
||||
the warranties that the Software is free of defects, merchantable, fit
|
||||
for a particular purpose or non-infringing. The entire risk as to the
|
||||
quality and performance of the Software is borne by you. Should the
|
||||
Software prove defective in any respect, you and not Licensor or its
|
||||
suppliers assume the entire cost of any service and repair. In
|
||||
addition, the security mechanisms implemented by the Software have
|
||||
inherent limitations, and you must determine that the Software
|
||||
sufficiently meets your requirements. This disclaimer of warranty
|
||||
constitutes an essential part of this Agreement.
|
||||
|
||||
|
||||
|
||||
Contents copyrighted by
|
||||
|
||||
Nizar ABDALLAH
|
||||
Pascale ALLEGRE
|
||||
Amara AMARA
|
||||
Gregoire AVOT
|
||||
Pirouz BAZARGAN-SABET
|
||||
Lotfi BEN-AMMAR
|
||||
Abdelhafid BOUARAOUA
|
||||
Luc BURGUN
|
||||
Jean-Paul CHAPUT
|
||||
Arnaud CARON
|
||||
Stephane DAYRAS
|
||||
Anne DERIEUX
|
||||
Gilles-Eric DESCAMPS
|
||||
Nathalie DICTUS
|
||||
Karim DIOURY
|
||||
Julien DUNOYER
|
||||
Olivier FLORENT
|
||||
Alain GREINER
|
||||
Amjad HAJJAR
|
||||
Mokhtar HIRECH
|
||||
Ludovic JACOMME
|
||||
Payam KIANI
|
||||
Marc LAURENTIN
|
||||
Anthony LESTER
|
||||
Marie-Minerve LOUERAT
|
||||
Luis LUCAS
|
||||
Francois PECHEUX
|
||||
Frederic PETROT
|
||||
Vincent POUILLEY
|
||||
Eudes PRADO
|
||||
El-Housseine REJOUAN
|
||||
Pascal REMY
|
||||
Patrick RENAUD
|
||||
Philippe ROYANNEZ
|
||||
Mohamed-Chaker SARWARY
|
||||
Olivier SIROL
|
||||
Huu-Nghia VUONG
|
||||
Franck WAJSBURT
|
||||
Laurent WINCKEL
|
||||
|
||||
Special thanks to
|
||||
All the members of the Architecture Team of the ASIM Laboratory
|
||||
All the users of the Alliance CAD system that
|
||||
help us in providing VLSI tools for free.
|
||||
|
||||
|
||||
# EOF
|
||||
|
||||
|
|
@ -0,0 +1,115 @@
|
|||
# Alliance VLSI CAD System
|
||||
#
|
||||
# Home page : http://www-asim.lip6.fr/alliance/
|
||||
# E-mail support : mailto:alliance-support@asim.lip6.fr
|
||||
# ftp sites : ftp://ftp.lip6.fr/lip6/softs/alliance/
|
||||
# or ftp://ftp-asim.lip6.fr/pub/alliance/
|
||||
#
|
||||
# $Id: README,v 1.1 1999/05/31 17:11:53 czo Exp $
|
||||
|
||||
|
||||
|
||||
# Alliance
|
||||
# ===================================================================
|
||||
|
||||
"Alliance VLSI CAD System" is free Software.
|
||||
|
||||
Unlike versions of Alliance up to 3.1 that where released
|
||||
including sources, version 3.2 and up will not be available
|
||||
with the source code.
|
||||
|
||||
Source is however still available, but only upon request to
|
||||
alliance-support@lip6.fr. The release of the source is now
|
||||
subject to a non disclosure agreement.
|
||||
|
||||
You are welcome to use the software package even for commercial
|
||||
designs whithout any fee. You are just required to mention :
|
||||
"Designed with Alliance CAD system"
|
||||
|
||||
You can get Alliance via anonymous FTP from ftp.lip6.fr
|
||||
|
||||
ftp://ftp.lip6.fr/lip6/softs/alliance/
|
||||
|
||||
or ftp://ftp-asim.lip6.fr/pub/alliance/
|
||||
|
||||
|
||||
|
||||
# Downloading
|
||||
# ===================================================================
|
||||
|
||||
|
||||
You will have to download at least two files : one for the common files
|
||||
of Alliance (like cells library) and another containing binaries for
|
||||
your specific platform. Actually only Linux_elf, SunOS and Solaris
|
||||
are supported.
|
||||
|
||||
alliance-3.2b-common.tar.gz Files common to each platform *required*
|
||||
|
||||
alliance-3.2b-i386-linux-2.0.30.tar.gz Binaries Linux_elf
|
||||
|
||||
alliance-3.2b-sparc-sunos-4.1.1.tar.gz Binaries SunOS
|
||||
|
||||
alliance-3.2b-sparc-solaris-2.5.1.tar.gz Binaries Solaris
|
||||
|
||||
|
||||
|
||||
|
||||
# Installation :
|
||||
# ===================================================================
|
||||
|
||||
You *dont* need to be root to install Alliance in a directory you *own*
|
||||
|
||||
In the example above I assume you have logged as root
|
||||
|
||||
1/ cd to the directory where you want to install Alliance
|
||||
|
||||
> cd /usr/local
|
||||
|
||||
2/ Unpack the common package
|
||||
|
||||
> gunzip -c alliance-3.2b-common.tgz | tar -pvxf -
|
||||
|
||||
3/ Unpack one of the platform specific package
|
||||
|
||||
> gunzip -c alliance-3.2b-Linux_elf.tgz | tar -pvxf -
|
||||
|
||||
4/ cd to alliance/share/etc and run the 'configure' script
|
||||
(This is the *only* script you need to run)
|
||||
|
||||
> cd alliance/share/etc
|
||||
> ./configure
|
||||
|
||||
If you install Alliance on different platforms you'll
|
||||
need to run the 'configure' script on each of them
|
||||
|
||||
|
||||
# Usage :
|
||||
# ===================================================================
|
||||
|
||||
Each user has to source alc_env.[c]sh to set Alliance environment
|
||||
variables to be able to run the Alliance tools.
|
||||
|
||||
in sh > . [where you have installed Alliance]/alliance/share/etc/alc_env.sh
|
||||
|
||||
in csh > source [where you have installed Alliance]/alliance/share/etc/alc_env.csh
|
||||
|
||||
This could be done in system's profile (/etc/profile)...
|
||||
so that it would be done at user login
|
||||
|
||||
This sets various default environement variables which could be changed by user
|
||||
later (Like MBK_OUT_LO to set the netlist output file format).
|
||||
|
||||
If you encounter problems, check the value of these variables in alc_env.[c]sh
|
||||
|
||||
$MACHINE : actually Linux_elf
|
||||
or SunOS
|
||||
or Solaris
|
||||
|
||||
$TOP : actually [where you have installed Alliance]/alliance/archi/Linux_elf
|
||||
or [where you have installed Alliance]/alliance/archi/SunOS
|
||||
or [where you have installed Alliance]/alliance/archi/Solaris
|
||||
|
||||
That's all :-)
|
||||
|
||||
|
||||
# EOF
|
||||
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue