On segunda-feira, 1 de agosto de 2016 12:36:32 PDT Hamish Moffatt wrote:
> I have tracked this down to macdeployqt, which is running strip on my
> binary. However it is also running strip on the Qt frameworks, yet its
> symbol names survive?
They have to. You're calling them.
More specifically:
When I get crash dumps from customers on OSX, I have no symbol names for
functions in my own code, but I do get names in the Qt libraries.
For example,
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.risingsoftware.auralia5 0x000102807815 0x10229f000 + 5670933
1
I have described the problem on my last email. When the target is a lib and not
an app things don’t happen as expected. My target is a lib and not a an app.
> On 31 Jul 2016, at 21:50, Petar Koretić wrote:
>
> How are you building your application?
> I can also state that I have no problems usi
How are you building your application?
I can also state that I have no problems using static qt with quick
controls 2 (gallery example -
qtquickcontrols2/examples/quickcontrols2/gallery).
On Sun, Jul 31, 2016 at 1:01 PM, Nuno Santos
wrote:
> Mitch,
>
> No, I haven’t. I have been digging. This is
My aim is to integrate a help system into my (py)qt application. I can
assemble the required help files and understand that part. I had a closer
look at QAssistantClient. In terms of functionality, this is what I need,
but I dislike being dependent on external programs (when deploying
software), wh
Mitch,
No, I haven’t. I have been digging. This is what I found. qmake is handling
correctly the case of a app template, generating the appropriated
plugin_import.cpp files. However, if the template is a lib, it is not. This is
what happens:
qmlRegisterType was saying that it requires absolute
