bisonc++ Code
Brought to you by:
fbb
| File | Date | Author | Commit |
|---|---|---|---|
| bisonc++ | 2015-05-17 |
|
[aacad9] Updated the bisonc++.xref file |
| sf | 2015-08-25 |
|
[4d84fd] Moved to GitHub |
| .gitignore | unknown | ||
| README | 2006-03-21 |
|
[9329f8] This commit was manufactured by cvs2svn to crea... |
| distribution | 2006-03-21 |
|
[9329f8] This commit was manufactured by cvs2svn to crea... |
| excluded | unknown | ||
| parsergen | unknown | ||
| sourcetar | 2013-04-09 |
|
[dd4eff] Updated sourcetar to use ../tarballs with -d |
This is the top-level directory of the bisonc++ program source tree.
The directory `sourceforge' is probably not useful for anybody but me, but
since it serves an important role for me in uploading the Bisonc++ docs to
sourceforge, they belong to this project. The same holds true for the
bisonc++/debian directory. Since the construction of the Debian package is now
using the configuration files at
https://svn.openfmi.net/debian-addons-bg/bisonc++
it is likely that the bisonc++/debian directory will at some point in the
future.
To create a source archive, run
./sourcetar
This will create an archive named like bisonc++_1.45.tar.gz.
To create an `upstream debian archive' provide sourcetar with an (any)
argument. E.g.,
./sourcetar deb
This will create an archive named like bisonc++_1.45.orig.tar.gz
The numbers will of course follow bisonc++'s version.
The `distribution' script is also probably not useful to anybody but me,
and it may be removed from new distributions at some future point in time.
To create the program from its sources, either descend into the bisonc++
directory, or unpack a created archive, cd into its top-level directory
and follow the instructions provided in the INSTALL file found there.