One thing I didn't test before:
On OSX, I only used `calibre-debug -g` and when I use it like that everything works just fine. While installing it asks me for placement in main toolbar etc. and I did it. After restart and running again `calibre-debug -g` plugin is installed just like in Linux and Windows.
The only message I get while running `calibre-debug -g` is:
Code:
QCocoaView handleTabletEvent: This tablet device is unknown (received no proximity event for it). Discarding event.
`calibre-debug -g` on OSX behaves exactly the same like `calibre` on Linux and Windows. Unfortunately running `calibre` on OSX brings problems I described above.
I wonder what are the differences in running `calibre` and `calibre-debug -g` on OSX? Is there anything I can add to plugin which will run only on OSX so it gets installed and running?
I'm happy to explore the differences in calibre-debug and calibre. The only problem I see at the moment is compiling calibre with debugging/print statements on OSX. I never compiled Calibre on OSX, I run it inside of a Virtualbox on my Linux machine and I would prefer if I don't need to go through custom compiles of Calibre on OSX.