Files
redshift-rebooted/HACKING
T
Jon Lund Steffensen d9f35a5989 Clean up install instructions in README, INSTALL, HACKING
Setup automake to "foreign" so that no additional files are required to be present.
Remove AUTHORS and ChangeLog (this info can be found in the git repository), and remove INSTALL.
Add a reference to the HACKING document in README.
Add dependency information in HACKING.
2013-11-23 17:12:07 -05:00

43 lines
977 B
Plaintext

Build from repository
---------------------
$ ./bootstrap
$ ./configure
The bootstrap script will use autotools to set up the build environment
and create the `configure` script.
Use `./configure --help' for options. Use `--prefix' to make an install in
your home directory. This is necessary to test python scripts. Example:
$ ./configure --prefix=$HOME/redshift/root
Now, build the files:
$ make
The main redshift program can be run at this point. To install to the
prefix directory run:
$ make install
You can now run the python scripts. Example:
$ PYTHONHOME=$HOME/redshift/root/lib/python2.7/site-packages \
$HOME/redshift/root/bin/redshift-gtk
Depenencies
-----------
* autotools, gettext
* libxcb, libxcb-randr (Optional, for RandR support)
* libX11, libXxf86vm (Optional, for VidMode support)
* geoclue (Optional, for geoclue support)
Notes
-----
- verbose flag is (currently) only held in redshift.c; thus, write all
verbose messages there.