On Monday 09 February 2015 22:17:26 Thiago Macieira wrote:
> On Monday 09 February 2015 22:07:19 Simon Matthews wrote:
> > In file included from /usr/include/asm-x86_64/byteorder.h:30:0,
> >
> > from /usr/include/asm/byteorder.h:5,
> > from 3rdparty/linux_perf_e
On Monday 09 February 2015 22:07:19 Simon Matthews wrote:
> In file included from /usr/include/asm-x86_64/byteorder.h:30:0,
> from /usr/include/asm/byteorder.h:5,
> from 3rdparty/linux_perf_event_p.h:19,
> from qbenchmarkperfevents.cpp:53:
> /us
I am trying to build Qt5 (5.4.0) on CentOS 5, so far without success. I
would appreciate any advice on getting the build to work.
I found packages for xcb-util, xcb-util-devel, libxcb-devel and xcb-proto
in the Atrpms repository and installed these.
The configuration stage is successful. My c
On Tuesday 10 February 2015 09:54:18 Hamish Moffatt wrote:
> I think there are also problems with libxslt.1.dylib and
> libsqlite3.0.dylib. macdeployqt is complaining here about both missing
> from /opt/local/lib, and both are in /usr/lib.
That must be the same MacPorts leak issue.
--
Thiago Ma
On 10/02/15 05:11, René J.V. Bertin wrote:
> On Monday February 09 2015 18:41:06 Till Oliver Knoll wrote:
>
>> Just recently there was a discussion that some pre-build Qt library
>> errorneously links with libz located in /opt (Mac Ports), instead of /usr
>> (=Apple).
>> You apparently just hit t
On Monday February 09 2015 22:09:41 Daniel França wrote:
> Thanks for the tip René, for now I'm trying to really understand
> install_name_tool.
>
> I thought I did :P
Don't worry, I don't think you're the only one :)
> The error is that it's referencing my local Qt for QtCore and QtSql, right
When you realize you sent an email too soon =/
The driver not being loaded was just that it was missing in the .pro
file += sql
Em Mon Feb 09 2015 at 11:09:39 PM, Daniel França
escreveu:
> Thanks for the tip René, for now I'm trying to really understand
> install_name_tool.
>
> I thought I did
Thanks for the tip René, for now I'm trying to really understand
install_name_tool.
I thought I did :P
But then after run the script that fixes the dylibs, and copy the
libsqlite.dylib to /MyBundle.app/Contents/PlugIns/sqlidrivers/
otool -L output:
MyBundle.app/Contents/PlugIns/sqldrivers/libqsq
On Monday February 09 2015 18:41:06 Till Oliver Knoll wrote:
> Just recently there was a discussion that some pre-build Qt library
> errorneously links with libz located in /opt (Mac Ports), instead of /usr
> (=Apple).
> You apparently just hit that same problem with Qt 5.4.
That discussion *wa
On Monday February 09 2015 16:46:18 Daniel França wrote:
> Hi guys,
> I know the subject is a little rude, but 2 years ago I'd a lot of problems
> trying to deploy an app to OS X, as you can see here:
> http://stackoverflow.com/questions/20895398/cant-deploy-qt-5-2-quick-app-to-mac-osx
...
> I can'
> Am 09.02.2015 um 18:33 schrieb Daniel França :
>
> ...
> Trying this command I get a:
> ERROR: no file at "/opt/local/lib/libz.1.dylib"
> ...
Just recently there was a discussion that some pre-build Qt library
errorneously links with libz located in /opt (Mac Ports), instead of /usr
(=Apple
Sorry, I haven’t checked. I have just written directly.
I think it’s best to start with an empty project.
As Till Oliver said, you must be careful with additional dependencies.
If you don’t depend from nothing else than Qt itself you should have no problem.
Below is one working example for my
Thanks Oliver,
I definitely need to understand better how to use install_name_tool.
I'll look into that, but I think my case it should be simpler, as I don't
use any 3rd party library.
Em Mon Feb 09 2015 at 6:33:40 PM, Daniel França
escreveu:
> I think the first parameter of macdeployqt must be
I think the first parameter of macdeployqt must be the app bundle.
Trying this command I get a:
*ERROR: no file at "/opt/local/lib/libz.1.dylib"*
*ERROR: no file at "/opt/local/lib/libz.1.dylib"*
*ERROR: no file at "/opt/local/lib/libz.1.dylib"*
*ERROR: no file at "/opt/local/lib/libz.1.dylib"*
> Am 09.02.2015 um 17:46 schrieb Daniel França :
>
> ...
> The solutions usually involves some custom script/app/macdeployqt.
AFAIK the recommended way is still to run the 'macdeployqt' tool and then
manually remove all unecessary Qt plugins ("manually" = "by qmake commands or
own script").
Daniel,
To deploy a Mac OSX Qt Quick app do the following:
Imagine that your build was made to /tmp/build_YOUR_APP_NAME_clang_64_Release
cd /tmp
/PATH_TO_YOUR_QT/clang_64/bin/macdeployqt -qmldir=/path_to_your_app_source
YOUR_APP_NAME.app
You need to run macdeployqt with the qmldir option, spec
Hi guys,
I know the subject is a little rude, but 2 years ago I'd a lot of problems
trying to deploy an app to OS X, as you can see here:
http://stackoverflow.com/questions/20895398/cant-deploy-qt-5-2-quick-app-to-mac-osx
You can see people with similar problems:
http://qt-project.org/forums/viewt
That's a great hint! Thank you! =)
On Mon, Feb 9, 2015 at 5:27 PM, Thiago Macieira
wrote:
> On Monday 09 February 2015 17:23:53 Valery Kotov wrote:
> > It could be an option. But, the problem here, I have no clue where to
> put a
> > breakpoint. =) I would expect it should be somewhere around QM
On Monday 09 February 2015 17:23:53 Valery Kotov wrote:
> It could be an option. But, the problem here, I have no clue where to put a
> breakpoint. =) I would expect it should be somewhere around QMetaObject. I
> will dig deer to find out.
All signal activations are a call to QMetaObject::activate
Hello Thiago,
Thank you for your hints!
> Why is it queued? You're adding a delay of one full event loop processing
> after the timer fires, which already happens inside the event loop.
Actually, it is direct. My bad. I didn't notice that it uses auto.
> You can do that if you write a testcase.
> -Original Message-
> From: Jason H [mailto:jh...@gmx.com]
> Sent: Friday, 6 February 2015 3:09 PM
> To: Curtis Mitch
> Cc: Agocs Laszlo; interest@qt-project.org
> Subject: Re: RE: [Interest] "Flat Light" Style How?
>
> All pretty simple:
>
> 1) Font sizes are simply too small.
I'm no
On Mon, 9 Feb 2015 11:39:06 +0100
Federico Buti wrote:
> Hi all.
>
> Reading the documentation for mapToItem/mapFromItem functions I've
> understand that it is possibile to translate a point to/from the
> coordinate system of the item itself. In particular, given the
> signature:
>
> .mapToItem
Hi all.
Reading the documentation for mapToItem/mapFromItem functions I've
understand that it is possibile to translate a point to/from the coordinate
system of the item itself. In particular, given the signature:
.mapToItem(null, 0, 0)
it is possibile to map the coordinate system origin of the
> On 06 Feb 2015, at 16:22, Thomas Sevaldrud wrote:
>
> Hi,
>
> I have two questions regarding QSGNodes. In my application I have used a
> Repeater with delegate Items to place labels defined in QML on objects in a
> 3D scene. To achieve this, I made a class derived from QSGSimpleRectNode and
24 matches
Mail list logo
