|
@pbw - it has been a long while since I setup my Eclipse environment, but from what I recall all I did was
- do a bazaar retrieval of the code into a directory,
- create a new empty Eclipse project in a different folder,
- right-click in the package explorer and add a new folder, click Advanced, and use the "Link to alternate location" to point to the "src" subfolder of the calibre code.
- the PYTHONPATH is set to the src/calibre folder. No external libraries etc.
- set your various other PyDev related defaults. Browse for the setting up Aptana thread in this forum for details of what they are
That is all there is to it from memory. You don't "run" calibre from eclipse - you just use it for editing/navigating the code. You set your CALIBRE_DEVELOP_FROM to point to the same src folder, and just run calibre as per normal, or calibre-debug -g if you want console output.
In my case for writing plugins I have a second folder I keep within src that contains them all, and as part of each plugin subfolder I keep a batch file that launches calibre after installing that plugin. So I can just double click on the batch file in the package explorer of Eclipse to see the new plugin in action.
|