Jon Lund Steffensen
30c805f5e7
This is primarily for improved discovery. Some users report that they didn't know about redshift-gtk, but had it been available on tab completion they would have noticed. Also, I think it is in general good practice that closely related programs have the same prefix.
30 lines
672 B
Plaintext
30 lines
672 B
Plaintext
Build from bzr branch
|
|
---------------------
|
|
$ ./bootstrap
|
|
$ ./configure
|
|
|
|
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
|
|
|
|
|
|
Notes
|
|
-----
|
|
- verbose flag is (currently) only held in redshift.c; thus, write all
|
|
verbose messages there.
|