View Single Post
Old 11-11-2011, 11:59 AM   #23
ldolse
Wizard
ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.
 
Posts: 1,337
Karma: 123455
Join Date: Apr 2009
Location: Malaysia
Device: PRS-650, iPhone
Quote:
Originally Posted by fab672000 View Post
Like I said, calibre-debug now works for me but just to make sure I understand what you suggested:

I did setup calibre_develop_from, as shown below:
[fab]~/devl $ set | grep CALIBRE
CALIBRE_DEVELOP_FROM=/Users/fab/devl/calibre/src
[fab]~/devl/calibre/src $ pwd
/Users/fab/devl/calibre/src

and tried running commands like:
python startup.py -g

it always complain that it doesn't find the import libs, looks like calibre-debug would set these import libs for me ...
I'd just like to get a more precise understanding here of what calibre-debug does for me...
Calibre has a self contained python install - you don't want to use the Mac OS python because it is indeed missing dozens of libs.

Generally just run calibre or calibre-debug from an environment with the environment variable set.

If you want Calibre's python environment to execute a script like startup.py you'd use this command:
calibre -e startup.py
ldolse is offline   Reply With Quote