Ok, thanks!
I've tried to decode the launcher app (the binary) "calibre-debug" to find out the Calibre entry point in debug-mode and other arguments but in vain. dtrace does give you only a limited view of the program arguments.
I've also tried to find out how it works by looking in the source for the luncher apps but there are no docs how they are constructed and as I don't have a complete dev-env I can't use the build process.
Can anyone please give me a hint how calibre-debug is starting up things? A qualified guess is that "start_gui" ("srs/gui2/main.py") might be the entry point...
PHP Code:
$ pwd
~/src/calibre/bypy/macos
$ ls -l
total 128
-rw-r--r-- 1 calibre staff 31460 Jul 6 16:17 __main__.py
-rw-r--r-- 1 calibre staff 1642 Jul 6 16:17 launcher.c
-rw-r--r-- 1 calibre staff 1072 Jul 6 16:17 placeholder.c
-rw-r--r-- 1 calibre staff 3304 Jul 6 16:17 sign.py
-rw-r--r-- 1 calibre staff 5293 Jul 6 16:17 site.py
-rw-r--r-- 1 calibre staff 6427 Jul 6 16:17 util.c
-rw-r--r-- 1 calibre staff 246 Jul 6 16:17 util.h
Btw, whats the reason why the launcher apps are created as binaries instead of regular scripts?