| 1 | Note for building CVC3 on linux
|
|---|
| 2 |
|
|---|
| 3 | sudo apt-get install
|
|---|
| 4 | g++
|
|---|
| 5 | bison
|
|---|
| 6 | flex
|
|---|
| 7 | libgmp10
|
|---|
| 8 | libgmp-dev
|
|---|
| 9 | openjdk-7-jdk
|
|---|
| 10 |
|
|---|
| 11 |
|
|---|
| 12 | for 32-bit:
|
|---|
| 13 | ./configure CXXFLAGS=-m32 --enable-dynamic --enable-java --with-java-home=/usr/lib/jvm/java-7-openjdk-i386
|
|---|
| 14 |
|
|---|
| 15 | for 64-bit:
|
|---|
| 16 | ./configure CXXFLAGS=-m64 --enable-dynamic --enable-java --with-java-home=/usr/lib/jvm/java-7-openjdk-amd64
|
|---|
| 17 |
|
|---|
| 18 |
|
|---|
| 19 |
|
|---|
| 20 |
|
|---|
| 21 | Dependencies and licenses...
|
|---|
| 22 |
|
|---|
| 23 | pcollections : MIT license,
|
|---|
| 24 | http://opensource.org/licenses/mit-license.php
|
|---|
| 25 | need to distribute license with product
|
|---|
| 26 | clj-ds
|
|---|
| 27 | EPL (Eclipse), https://github.com/krukow/clj-ds/blob/master/epl-v10.html,
|
|---|
| 28 | distribute license with code
|
|---|
| 29 | cvc3
|
|---|
| 30 | http://www.cs.nyu.edu/acsys/cvc3/doc/LICENSE.html
|
|---|
| 31 | uses zchaff which has limiting license
|
|---|
| 32 | antlr-runtime
|
|---|
| 33 | BSD license: http://antlr.org/license.html
|
|---|
| 34 | libgmp: LGPL
|
|---|
| 35 |
|
|---|
| 36 |
|
|---|
| 37 | include licenses in distribution
|
|---|
| 38 |
|
|---|
| 39 | include version number and civl revision?
|
|---|
| 40 |
|
|---|
| 41 | CIVL/
|
|---|
| 42 | lib/
|
|---|
| 43 | civl-0.1-r239.jar
|
|---|
| 44 | civl.jar -> civl-0.1-r239.jar
|
|---|
| 45 | etc.
|
|---|
| 46 | LICENSE
|
|---|
| 47 | bin/
|
|---|
| 48 | doc/
|
|---|
| 49 |
|
|---|
| 50 | Stable releases: each with complete distributions or just jar,
|
|---|
| 51 | different OS types
|
|---|
| 52 |
|
|---|
| 53 | Unstable release: just give the latest, complete distribution and
|
|---|
| 54 | just the civl jar.
|
|---|
| 55 |
|
|---|
| 56 | Process for unstable latest: automate in build script
|
|---|
| 57 | ant should do "release" target: create directory called
|
|---|
| 58 | "release" with whatever you want, copy it over. waste.
|
|---|
| 59 |
|
|---|
| 60 | worker should perform perl substitutions, bundle everything
|
|---|
| 61 | up into one directory called build-r256 (e.g.)
|
|---|
| 62 |
|
|---|
| 63 | preparing release: create directories, copy jar and dependencies,
|
|---|
| 64 | create symlinks, tar, gzip
|
|---|
| 65 |
|
|---|
| 66 | prepare stable release: goes in tags, leave out revision number
|
|---|
| 67 |
|
|---|
| 68 | how to tell which version you are in. Put in repository a file
|
|---|
| 69 | called VERSION. That is it.
|
|---|
| 70 |
|
|---|
| 71 | Stable: leave off r part. put in tags directory
|
|---|
| 72 |
|
|---|
| 73 |
|
|---|
| 74 | release_civl
|
|---|
| 75 | stable_release_civl
|
|---|
| 76 |
|
|---|
| 77 | put VERSION file in CIVL main directory.
|
|---|
| 78 | manager needs to copy jar file over (civl.jar) and rename it?
|
|---|
| 79 | manager needs to know what it is called.
|
|---|
| 80 |
|
|---|
| 81 |
|
|---|
| 82 | civl/
|
|---|
| 83 | test/
|
|---|
| 84 | trunk/
|
|---|
| 85 | latest@
|
|---|
| 86 | r98/
|
|---|
| 87 | r99/
|
|---|
| 88 | release/
|
|---|
| 89 | civl.jar@->
|
|---|
| 90 | CIVL.tgz@->
|
|---|
| 91 | civl-trunk_99.jar
|
|---|
| 92 | CIVL-trunk_99.tgz (untars to CIVL-trunk-r99/, and inside there is
|
|---|
| 93 | civl-trunk-r99.jar and in bin civl, which is a script that references the
|
|---|
| 94 | directory /Applications/CIVL-trunk-r99 ... ) This way user can have multiple
|
|---|
| 95 | CIVL versions installed at once and set path appropriately.
|
|---|
| 96 | 1.0/
|
|---|
| 97 | latest@
|
|---|
| 98 | r100/
|
|---|
| 99 | r101/
|
|---|
| 100 | civl-1.0_101.jar
|
|---|
| 101 | CIVL-1.0_101.tgz
|
|---|
| 102 |
|
|---|
| 103 | web/
|
|---|
| 104 | r123/
|
|---|
| 105 | junit/
|
|---|
| 106 | coverage/
|
|---|
| 107 | javadoc/
|
|---|
| 108 | release/
|
|---|
| 109 | CIVL-1.0-osx-r279.tgz
|
|---|
| 110 | CIVL-1.0-linux-r279.tgz
|
|---|
| 111 | civl.jar
|
|---|
| 112 |
|
|---|
| 113 |
|
|---|
| 114 |
|
|---|
| 115 | give some examples usages.
|
|---|
| 116 |
|
|---|
| 117 | documentation must be included.
|
|---|
| 118 |
|
|---|
| 119 | command line options.
|
|---|
| 120 |
|
|---|
| 121 |
|
|---|