Menu

Tree [ddd5da] master /
 History

HTTPS access


File Date Author Commit
 doc 2011-07-05 Josh Busch Josh Busch [6657bd] no longer need nasm ABI also added in x86_64 isa
 include 2011-07-13 Josh Larson Josh Larson [ddd5da] Reorganized arraylist code so that the arraylis...
 src 2011-07-13 Josh Larson Josh Larson [ddd5da] Reorganized arraylist code so that the arraylis...
 test 2011-07-03 Josh Busch Josh Busch [f4f432] spring cleaning, plus a few new docs
 tmp 2011-07-05 Josh Larson Josh Larson [5ea194] Set up autotools (I think)
 utils 2011-06-15 Josh Busch Josh Busch [9dc97a] small edit to vimrc to prevent weird XORG thingy
 Makefile.am 2011-07-05 Josh Larson Josh Larson [5ea194] Set up autotools (I think)
 README 2011-07-05 Josh Larson Josh Larson [17885e] Added the README file and changed a command in ...
 at_setup.sh 2011-07-05 Josh Larson Josh Larson [17885e] Added the README file and changed a command in ...
 compile.sh 2011-07-05 Josh Larson Josh Larson [d6fef8] Updated and added scripts to make autotools eas...
 configure.ac 2011-07-05 Josh Larson Josh Larson [bafb04] Added system and ir to autotools and updated ma...
 run.sh 2011-07-13 Josh Larson Josh Larson [ddd5da] Reorganized arraylist code so that the arraylis...

Read Me

********************************************************************************
Setting up autotools and compiling
********************************************************************************
The first thing you need to do is make sure that you have autotools and libtool
installed.

Then, run 
$ ./at_setup.sh init

Which is the same as
$ autoreconf --install

This will generate the configure file, as well as a metric ton of other files 
(they are actually listed in at_setup.sh, if you care), such as Makefile.in
and m4/a-whole-bunch-of-stuff. 

Next, run
$ ./compile.sh init

That is equivalent to
$ ./configure --prefix=$PWD/build
$ make && make install

Congrats, you have installed jcomp (which would be called josh if there weren't
already a directory in src/ called josh). To run it, you can either do
$ build/bin/jcomp

or
$ ./run.sh

********************************************************************************
Recompiling
********************************************************************************
This is easy. If you've changed something in the code and want to recompile, 
then at the root of our project, run 
$ ./compile

That is the same as
$ make && make install

********************************************************************************
Cleaning up
********************************************************************************

To clean up, run
$ ./compile.sh clean

That is equivalent to
$ make uninstall
$ make distclean

And it removes executables, object files, and the like - basically, restores 
our code to the point AFTER calling ./at_setup.sh init. That is, configure,
m4/stuff, and all the rest are still there. 

To completely clean up - that is - restore your code to the point where svn st
actually gives you meaningful output, use
$ ./at_setup.sh clean

That removes all of the auto-generated files. At least, it does on my system...
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.