File: HACKING

package info (click to toggle)
flashproxy 1.7-4
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid, stretch
  • size: 936 kB
  • ctags: 876
  • sloc: python: 3,708; sh: 823; makefile: 246; lisp: 15
file content (26 lines) | stat: -rw-r--r-- 872 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
== Running from source checkout

In order to run the code directly from a source checkout, you must make sure it
can find the flashproxy module, located in the top-level directory of the
source checkout, which is probably the parent directory. You have two options:

1. Install it in "development mode", see [1]

  flashproxy# python setup-common.py develop

This process is reversible too:

  flashproxy# python setup-common.py develop --uninstall

The disadvantage is that other programs (such as a system-installed flashproxy,
or other checkouts in another directory) will see this development copy, rather
than a more appropriate copy.

2. Export PYTHONPATH when you need to run

  $ export PYTHONPATH=..
  $ make && make check

The disadvantage is that you need to do this every shell session.

[1] http://pythonhosted.org/distribute/setuptools.html#development-mode