The Firefox Add-on SDK (aka Jetpack) uses a virtualenv but I want to keep the dependencies for Oplop development in a project-specific virtualenv, not in the
firefox-addon-sdk-1.2.1 one. I use virtualenvwrapper so I added
predeactivate hooks to make it easy to switch between the 2 virtualenvs. The
postactivate hook is:
predeactivate just destroys the
sdk alias as a cleanup.
For development, Oplop requires Jinja2 and SCons. Jinja2 is easily installed in a virtualenv with pip, but Scons doesn’t play nice with pip and I ran into this issue. Fortunately that’s easily remedied by downloading the scons tarball, unpacking it and installing with
python setup.py install (with the project virtualenv activated, of course).
With that all in place I can use
workon oplop-firefox-addon to activate the virtualenv where Jinja2 and Scons are available and use Scons to render templates, etc., then use
sdk to flip to the
firefox-addon-sdk-1.2.1 virtualenv to use
cfx to test the add-on.
No Pingbacks for this post yet...
A private blog for life, cycling, and my computing fiddlings.
|<< <||> >>|