Building Calibre on OSX Lion?

[KevinH]

Hi,

Originally Posted by dwanthny

How does this have any bearing on whether this is a GPL project? The source is there to contribute to the project or build as you wish. There is no requirement in the GPL that folks have their hand held through building

Again, I find this response very troubling. I have never seen a GPL project that will not help volunteer developers with building and packaging issues on supported platforms (or even unsupported platforms if they are attempting a port). And I have been developing software and helping out on various projects since the late 1970s.

No one is asking for "hand-holding". If it is not immediately clear how to build a release package for Mac OS X, please include even a rough README_MacOSX.txt file that at least outlines the sequence of steps needed. Please also include any scripts of makefiles you are currently using.

No secrecy exists here, the source is well documented and other groups have used the basic project in endeavors of there own without hand holding or knowing any secret handshake or secret code.

Glad to hear it. So please ... if the steps on how to build and package for a specific supported platform are not already part of the source code release, please include the makefiles, scripts, or instructions that do exist for that platform ... no matter how rough ... so that others can figure things out too.

I do not think that is too much to ask for any OpenSource / GPL project.

Thank you.

KevinH

[KevinH]

Hi,

Originally Posted by kovidgoyal

@KevinH: The provided sources are fully buildable if you know a lot about the OS and python and a couple of dozen other things are willing to to spend a couple of days doing it.

Great, when I have time next week, I will give it a shot and try to simplify it (if that is even possible) or at least document the Mac OS X build and packaging. I have access to Linux and Windows build environments as well and hopefully, across the 3 of them I should be able to figure something out what works for Mac OS X.

KevinH

[fab672000]

Originally Posted by dwanthny

I have not run from source and I am unfamiliar with OSX, but could what you are looking for be part of the Command line tools? To install the command line tools, go to Preferences->Advanced->Miscellaneous.

Yes now I understand the paragraph ":guilabel:Preferences->Advanced->Miscellaneous in the calibre GUI." in the documentation,
Thanks!

BTW, the documentation also says run calibredb shouldn't it be calibre-debug then or is it platform dependent ?

Thank you very much, could print debug info from the __init__.py that starts here for me

[DoctorOhh]

Originally Posted by KevinH

Again, I find this response very troubling.

Since my first sentence declared my ignorance I would find it hard to believe you could actually find the response very troubling.

[ldolse]

Originally Posted by KevinH

I have never seen a GPL project that will not help volunteer developers with building and packaging issues on supported platforms (or even unsupported platforms if they are attempting a port).

I think you misunderstood the intent of our responses - the intent was to avoid, for both the OP and ourselves a tremendous amount of hassle if the recommended method met his needs, which it did. Hence the focus on explaining the recommended approach vs. trying to solve the build from scratch problems.

[kovidgoyal]

@KevinH: The scripts used to build calibre are included in the source tarball. The difficulty lies in setting up the OS environment for it. Run

python setup.py build
python setup.py osx32_freeze

to build the app bundle. It will fail, you will have to fix the errors one by one by setting up the dev environment on OS X.

[fab672000]

Originally Posted by kovidgoyal

@fab672000: You do not need calibre-debug, as long as you have correctly set CALIBRE_DEVELOP_FROM, you can just run calibre normally.

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...

[ldolse]

Originally Posted by fab672000

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

[fab672000]

@Idolse: thank you now I understand, these tools are binaries, I originally thought they would only be scripts that would setup the environment but it apparently does much more as it has python embedded.

Just being curious what calibre-debug does more for debug than calibre:
Does calibre-debug embeds debugger capabilities permitting to have breakpoints as an example, or is the debug version only permits to run unitary scripts facilities within the calibre env only ?
Anyone having successfully setup a PyDev w/calibre env for OS X ?

[KevinH]

Hi,

Thanks for the tip. I will give it a go and try to document the build requirements and set-up (Qt, Python 2.7, other graphics libs?, etc) and will write up a README so that others can give it a try if they want too.

Kevin

Originally Posted by kovidgoyal

@KevinH: The scripts used to build calibre are included in the source tarball. The difficulty lies in setting up the OS environment for it. Run

python setup.py build
python setup.py osx32_freeze

to build the app bundle. It will fail, you will have to fix the errors one by one by setting up the dev environment on OS X.

[ldolse]

Originally Posted by fab672000

@Idolse: thank you now I understand, these tools are binaries, I originally thought they would only be scripts that would setup the environment but it apparently does much more as it has python embedded.

Just being curious what calibre-debug does more for debug than calibre:
Does calibre-debug embeds debugger capabilities permitting to have breakpoints as an example, or is the debug version only permits to run unitary scripts facilities within the calibre env only ?
Anyone having successfully setup a PyDev w/calibre env for OS X ?

I believe the main difference is it just outputs more debug messages to the CLI.

Read here for pydev:
https://www.mobileread.com/forums/sho...ighlight=pydev


Personally I just use debug statements and check the calibre-debug output, and comment them out or delete them when I'm done.