| 1 |
08.02.2011, 09:21, mattmatteh@×××××.com: |
| 2 |
>>>> ššIs this behavior intentional? Note that this application are not supposed to be used from command line. |
| 3 |
>>> šI think it is intentional to at least provide a symlink (or wrapper that |
| 4 |
>>> šcalls open /path/too/My.app) in usr/bin to the app like it would be |
| 5 |
>>> šavailable on Linux, but there is nothing against building the bundles if |
| 6 |
>>> šthat actually makes it work right. |
| 7 |
>> šI guess something is wrong in qt4.eclass or mkspec macx-g++ (if it's changed in Gentoo somehow). |
| 8 |
>> šQt projects provide Mac-specific logic, and it works fine when building with official Qt libraries, but IIRC |
| 9 |
>> š"manual" building of Qt projects with qmake from Gentoo produces similar "broken" bundles (will check it ASAP) |
| 10 |
> |
| 11 |
> i have noticed that qt with prefix uses the unix install, not the mac |
| 12 |
> way so bundles are not default. š |
| 13 |
|
| 14 |
You are not correct, bundles ARE created, but executable is placed outcide bundle |
| 15 |
|
| 16 |
>i actaully like it this way. |
| 17 |
|
| 18 |
Do you like to have applications with default "Unix application" icon in your dock? )) |
| 19 |
Console utilities are not bundled. |
| 20 |
|
| 21 |
Also, executables of Qt applications like designer, assistant, etc. are named |
| 22 |
differently on Mac (e.g. designer -> Designer, qtcreator -> Qt\ Creator), so installation |
| 23 |
differs anyway |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
Regards, |
| 28 |
Konstantin |
Archives