Re: [Interest] How to deal with database specific syntax

[Dmitriy Purgin]

Exactly, that's what I meant by "supporting the stored procedure call
syntax". Sorry, it was a bit vague. Anyway, in this case you're
implementing a single interface for an SP call backed by multiple "syntax
handlers" which is much easier than handling lots of syntactic differences
for any kind of operations one might want to do with a database. It's not
ideal, it has its drawbacks but it also has advantages. Moreover, pmqt71
has explicitly stated that he/she doesn't want to go the ORM way.

Cheers

2015-02-12 12:26 GMT+06:00 alexander golks :

> Am Thu, 12 Feb 2015 08:59:18 +0600
> schrieb Dmitriy Purgin :
>
> > Hi,
> >
> > Actually I don't think it's a Qt-related question but here's my approach
> to
> > it.
> >
> > Since you struggle with both syntaxes, you may want to try and
> encapsulate
> > SQL code to stored procedures on the DB side and by that I mean not only
> > simple data retrieval or updating but also the business logic. You are
> > still obliged to support both DB backends but at least it will reduce the
> > dependencies in your C++ program down to supporting the stored procedure
> > call syntax which is pretty simple. Here you may also gain a performance
> > boost since the data operations are as close to data as it can be.
>
> ifair, each driver may handle stored procedure calls differently (1).
> some need special handling for multiple result sets, others need special
> handling for in/out values.
> so you may still need to handle different "syntax" foreach driver.
>
> [1] http://doc.qt.io/qt-5/sql-driver.html
>
> >
> > Regards
> > Dmitriy Purgin
> >
> > 2015-02-11 18:54 GMT+06:00 pmqt71 :
> >
> > > Hi all,
> > >
> > > in my Qt application I've to duplicate sql instructions for MySql and
> > > Postgres due to different sql syntax.
> > > Most problems are on date types. For instance, MySql has DATEDIFF,
> > > Postgres has EXTRACT, CAST...
> > >
> > > Without using ORMs, is there a way to manage specific sql syntax?
> > >
> > >
> > > Thanks
> > > pm
> > >
> > >
> > > ___
> > > Interest mailing list
> > > Interest@qt-project.org
> > > http://lists.qt-project.org/mailman/listinfo/interest
> > >
> > >
>
>
> --
> /*
>  *  "There's definitely something wrong here."
>  *
>  *  Husse Jul 11 2007
>  */
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to deal with database specific syntax

[alexander golks]

Am Thu, 12 Feb 2015 08:59:18 +0600
schrieb Dmitriy Purgin :

> Hi,
> 
> Actually I don't think it's a Qt-related question but here's my approach to
> it.
> 
> Since you struggle with both syntaxes, you may want to try and encapsulate
> SQL code to stored procedures on the DB side and by that I mean not only
> simple data retrieval or updating but also the business logic. You are
> still obliged to support both DB backends but at least it will reduce the
> dependencies in your C++ program down to supporting the stored procedure
> call syntax which is pretty simple. Here you may also gain a performance
> boost since the data operations are as close to data as it can be.

ifair, each driver may handle stored procedure calls differently (1).
some need special handling for multiple result sets, others need special 
handling for in/out values.
so you may still need to handle different "syntax" foreach driver.

[1] http://doc.qt.io/qt-5/sql-driver.html

> 
> Regards
> Dmitriy Purgin
> 
> 2015-02-11 18:54 GMT+06:00 pmqt71 :
> 
> > Hi all,
> >
> > in my Qt application I've to duplicate sql instructions for MySql and
> > Postgres due to different sql syntax.
> > Most problems are on date types. For instance, MySql has DATEDIFF,
> > Postgres has EXTRACT, CAST...
> >
> > Without using ORMs, is there a way to manage specific sql syntax?
> >
> >
> > Thanks
> > pm
> >
> >
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/interest
> >
> >


-- 
/*
 *  "There's definitely something wrong here."
 *
 *  Husse Jul 11 2007
 */


signature.asc
Description: PGP signature
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Issues building Qt 5.4.0 on CentOS 5.

[Simon Matthews]

On Wed, 11 Feb 2015, Thiago Macieira wrote:


On Wednesday 11 February 2015 19:17:02 Simon Matthews wrote:

OK, nm. By the way, am I correct in my belief that for Qt 5.4.0, that
Webkit depends on icu?


Correct.


Thanks for confirming that. I did not want to waste time chasing down an 
issue that wasn't relevent to my problem.


Using the link and some slight modifications, I got Qt to build, 
apparently with ICU support, but, no Webkit. After installation, there are 
no files called

/usr/lib/Qt/Qt-5.4.0-x86_64/lib/libQt5WebKit*

It looks like I need to figure out how to get it to build with fontconfig 
and maybe other options that I have disabled (multimedia?)


./configure -R ‘\\\$$ORIGIN’ -D _X_INLINE=inline -D 
XK_dead_currency=0xfe6f -D XK_ISO_Level5_Lock=0xfe13 -D 
FC_WEIGHT_EXTRABLACK=215 -D FC_WEIGHT_ULTRABLACK=FC_WEIGHT_EXTRABLACK -v 
-opensource -qt-libpng -qt-zlib -qt-libjpeg  -nomake examples 
-qt-sql-sqlite -confirm-license -prefix /usr/lib/Qt/Qt-5.4.0-x86_64 
-widgets -no-openssl  -no-openssl -no-dbus -no-fontconfig -qt-xcb 
-no-opengl  -skip activeqt -skip androidextras -skip connectivity -skip 
enginio -skip location -skip macextras -skip multimedia -skip quick1 -skip 
sensors -skip serialport -skip wayland -skip webchannel -skip 
webkit-examples  -skip x11extras  -c++11 -icu


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Issues building Qt 5.4.0 on CentOS 5.

[Thiago Macieira]

On Wednesday 11 February 2015 19:17:02 Simon Matthews wrote:
> OK, nm. By the way, am I correct in my belief that for Qt 5.4.0, that 
> Webkit depends on icu?

Correct.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Issues building Qt 5.4.0 on CentOS 5.

[Simon Matthews]

On Wed, 11 Feb 2015, Thiago Macieira wrote:

> On Wednesday 11 February 2015 17:56:13 Simon Matthews wrote:
>> I think that Webkit is not included because the test for icu fails:
>> g++ -L /usr/local/lib -L /usr/local/lib/icu -I /usr/local/include/unicode/
>> -I /usr/local/include/layout/
>> ./qtwebkit/Tools/qmake/config.tests/icu/icu.cpp
>> /tmp/ccq3GOLd.o: In function `main':
>> icu.cpp:(.text+0x33): undefined reference to `ucol_open_4_2'
>> icu.cpp:(.text+0x5d): undefined reference to `ucol_close_4_2'
>> collect2: error: ld returned 1 exit status
>
> The -l options seem to be missing.
>
>> I have installed (from source) icu 4.2.1 and these symbols appear in the
>> libraries:
>> strings /usr/local/lib/libicui18n.so.42.1 | grep "ucol_close_4_2"
>> ucol_close_4_2
>
> Hint: use nm instead of strings. Even nm --defined, so you don't catch an
> undefined reference to the symbol.

OK, nm. By the way, am I correct in my belief that for Qt 5.4.0, that 
Webkit depends on icu?

nm --defined /usr/local/lib/libicui18n.so.42.1 | grep ucol_close_4_2
000d0a90 T ucol_close_4_2

Simon
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Deploying Qt to MacOs still...errr, sucks?

[Hamish Moffatt]

On 12/02/15 05:11, Adam Light wrote:
>
> If you're using Qt 5 (maybe only 5.4), macdeployqt may be able to help 
> with the code signing and possibly the dmg part:
>
> /qtbuild5/install/mac64/bin/macdeployqt --help

Unfortunately that's not much use if you need to do anything more than 
copy in Qt; for example bundle extra frameworks you are using, or remove 
Qt plugins you don't need. If you do either of those then you need to 
sign the app in your own scripts, because those operations will 
invalidate any signing done by macdeployqt.

Of course macdeployqt could help by 1. supporting bundling other 
frameworks (which it can find via otool, as it does to find which Qt 
frameworks to bundle), and 2. allow you to include/exclude various Qt 
plugins.

Right now it seems to bundle every plugin (or none, if you tell it to), 
which is both a waste of space and a no-go with the Mac App store for us.


Hamish
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Issues building Qt 5.4.0 on CentOS 5.

[Thiago Macieira]

On Wednesday 11 February 2015 17:56:13 Simon Matthews wrote:
> I think that Webkit is not included because the test for icu fails:
> g++ -L /usr/local/lib -L /usr/local/lib/icu -I /usr/local/include/unicode/ 
> -I /usr/local/include/layout/ 
> ./qtwebkit/Tools/qmake/config.tests/icu/icu.cpp
> /tmp/ccq3GOLd.o: In function `main':
> icu.cpp:(.text+0x33): undefined reference to `ucol_open_4_2'
> icu.cpp:(.text+0x5d): undefined reference to `ucol_close_4_2'
> collect2: error: ld returned 1 exit status

The -l options seem to be missing.

> I have installed (from source) icu 4.2.1 and these symbols appear in the 
> libraries:
> strings /usr/local/lib/libicui18n.so.42.1 | grep "ucol_close_4_2"
> ucol_close_4_2

Hint: use nm instead of strings. Even nm --defined, so you don't catch an 
undefined reference to the symbol.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to deal with database specific syntax

[Dmitriy Purgin]

Hi,

Actually I don't think it's a Qt-related question but here's my approach to
it.

Since you struggle with both syntaxes, you may want to try and encapsulate
SQL code to stored procedures on the DB side and by that I mean not only
simple data retrieval or updating but also the business logic. You are
still obliged to support both DB backends but at least it will reduce the
dependencies in your C++ program down to supporting the stored procedure
call syntax which is pretty simple. Here you may also gain a performance
boost since the data operations are as close to data as it can be.

Regards
Dmitriy Purgin

2015-02-11 18:54 GMT+06:00 pmqt71 :

> Hi all,
>
> in my Qt application I've to duplicate sql instructions for MySql and
> Postgres due to different sql syntax.
> Most problems are on date types. For instance, MySql has DATEDIFF,
> Postgres has EXTRACT, CAST...
>
> Without using ORMs, is there a way to manage specific sql syntax?
>
>
> Thanks
> pm
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Issues building Qt 5.4.0 on CentOS 5.

[Simon Matthews]

On Tue, 10 Feb 2015, Thiago Macieira wrote:


On Tuesday 10 February 2015 22:34:20 Simon Matthews wrote:

../../../../3rdparty/xcb/include/xcb/xcb_bitops.h:51: error: expected ‘=’,
‘,’,  ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’


The one thing "before 'static'" is _X_INLINE.

_X_INLINE is supposed to come from X11/Xfuncproto.h. Can you verify that yours 
defines _X_INLINE?


/* C99 keyword "inline" or equivalent extensions in pre-C99 compilers */
/* requires xproto >= 7.0.9
  (introduced in 7.0.8 but didn't support all compilers until 7.0.9) */
#if defined(inline) /* assume autoconf set it correctly */ || \
  (defined(__STDC_VERSION__) && (__STDC_VERSION__ - 0 >= 199901L)) /* C99 */ 
|| \

  (defined(__SUNPRO_C) && (__SUNPRO_C >= 0x550))
# define _X_INLINE inline
#elif defined(__GNUC__) && !defined(__STRICT_ANSI__) /* gcc w/C89+extensions */
# define _X_INLINE __inline__
#else
# define _X_INLINE
#endif

Given the comment about versions (X11 R7.0.8), I'm guessing your X11 headers 
are also too old and don't include this.


When is X.org 7.0.8 from? 2005 or 2006. That's current to Qt 4.1.


I took another approach, following the instructions on this page:
http://kate-editor.org/2014/12/22/qt-5-4-on-red-hat-enterprise-5/

This involves a small patch to the Qt sources, which seems to eliminate 
the issue with the kernel headers.


This build is successful, but does not include Webkit.

I think that Webkit is not included because the test for icu fails:
g++ -L /usr/local/lib -L /usr/local/lib/icu -I /usr/local/include/unicode/ 
-I /usr/local/include/layout/ 
./qtwebkit/Tools/qmake/config.tests/icu/icu.cpp

/tmp/ccq3GOLd.o: In function `main':
icu.cpp:(.text+0x33): undefined reference to `ucol_open_4_2'
icu.cpp:(.text+0x5d): undefined reference to `ucol_close_4_2'
collect2: error: ld returned 1 exit status

I have installed (from source) icu 4.2.1 and these symbols appear in the 
libraries:

strings /usr/local/lib/libicui18n.so.42.1 | grep "ucol_close_4_2"
ucol_close_4_2

The files appear to be the correct format:
file /usr/local/lib/libicui18n.so.42.1
/usr/local/lib/libicui18n.so.42.1: ELF 64-bit LSB shared object, AMD 
x86-64, version 1 (SYSV), not stripped


Simon


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Fwd: Qt 5.4 build error on OS X 10.7

[René J . V . Bertin]

On Wednesday February 11 2015 13:14:46 Thiago Macieira wrote:

> d47b9ace50d47a4472dc9fb029bbf6e8dd810c01

Great, thanks.

R.


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Fwd: Qt 5.4 build error on OS X 10.7

[Thiago Macieira]

On Wednesday 11 February 2015 18:15:51 René J.V. Bertin wrote:
> On Wednesday February 11 2015 08:42:07 Thiago Macieira wrote:
> > On Wednesday 11 February 2015 17:15:37 René J.V. Bertin wrote:
> > > $D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/../../src/co
> > > reli b/kernel/qmetatype.h:1943:1: error: copying variable of type
> > > 'QBasicAtomicInt' (aka 'QBasicAtomicInteger') invokes deleted
> > > constructor Q_DECLARE_METATYPE_TEMPLATE_2ARG(QPair)
> > > ^~~
> > 
> > This is fixed already.
> > 
> > It was a missing digit in qcompilerdetection.h.
> 
> Good to know, could you point me to the fix, please?

d47b9ace50d47a4472dc9fb029bbf6e8dd810c01

Fix the Apple build version numbers for Clang

A bunch of zeroes were missing. And not to the left.

Task-number: QTBUG-43279
Change-Id: I1a710cf572099547b2ade7b2574a7e0a61649758

> And how come it didn't affect my build of the same code (5.4.0 tarball)?
> Exactly because I used a later compiler version?

Exactly. The problem is the detection of the matching Clang compiler version 
for a given Apple-specific build of its Clang. Since we forgot a digit, it 
matched the wrong version and enabled code that triggered a bug in the Clang 
from XCode 4.2.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to deal with database specific syntax

[Jason H]

Without ORMs o query generators, you  pretty much have to do it yourself. Have two syntaxes for the same query, choose based on the driver. This works for me because I don't like maintaining SQL in code unless I have to, I read my SQL from a YAML/text file, or the database itself. 

 

Sent: Wednesday, February 11, 2015 at 7:54 AM
From: pmqt71 
To: "Qt Project" 
Subject: [Interest] How to deal with database specific syntax


Hi all,
 

in my Qt application I've to duplicate sql instructions for MySql and Postgres due to different sql syntax.

Most problems are on date types. For instance, MySql has DATEDIFF, Postgres has EXTRACT, CAST...

 

Without using ORMs, is there a way to manage specific sql syntax?

 

 

Thanks

pm

 

___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] easily prevent ListView from stealing mouse events from QQuickPaintedItem?

[VStevenP]

I have a ListView where the delegate contains an embedded QQuickPaintedItem 
graph I exposed to QML via qmlRegisterType().  The graph accepts mouse events 
so that the user can drag vertices on the graph in order to edit the graph.  
Unfortunately, the ListView, which is oriented as horizontal,  is not allowing 
horizontal mouse changes to flow to my graph, which breaks the graphical 
editing of the graph.
Is there an easy way to allow the mouse events to propagate to my graph.  I've 
tried playing with z-order but had no luck.  I really need to figure out a way 
to have my Qt graphs appear in QML flickables and not have their editing broken 
by mouse event stealing.
I saw an earlier thread on this topic from last November, but it was a slightly 
different question and I didn't see a clear answer.
- Steve PavaoKorg R&D
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Deploying Qt to MacOs still...errr, sucks?

[Michael Jackson]

On Feb 11, 2015, at 1:43 PM, René J.V. Bertin  wrote:

> On Wednesday February 11 2015 13:27:37 Michael Jackson wrote:
> 
>> I was also the one that reported the MacPort dependency. And I am not really 
>> comfortable just changing the install_name to point towards another library 
>> of the same name but unknown as to how it was compiled or with what options. 
>> I'll count that as another obvious bug and not put in a bug report.
> 
> This is a bit of a delicate matter. If Digia indeed use MacPorts to provide 
> certain dependencies, it will not be that easy to avoid generic libraries 
> like those reported, because it is MacPorts' principle to provide those 
> libraries itself, but compiled with the default system compiler.
> This is of no consequence as long as those in MacPorts are not so far ahead 
> of the ones Apple ship that they become ABI incompatible. Nothing stops Digia 
> from setting up (or having set up) a MacPorts environment that uses the same 
> versions as Apple, and "simply" mark these ports as held, to borrow a Debian 
> term.
> 
>> Now. if QtCreator could just better understand CMake projects I think I 
>> could have a decent experience coding with Qt.
> 
> Do you use a lot of ObjC code? If not, you could have a look at KDevelop. I 
> actually prefer it over Creator in most aspects. You'd still need Creator or 
> Xcode for debugging, though, because KDevelop doesn't support lldb yet.
> 
> R.
> 

Generally, because LLDB is still "new" when compared to gdb, *every body's* 
support for LLDB is very much sub-par at best for OS X. If you switch to Linux 
and use QtCreator to debug then the experience is enjoyable. Same thing for 
Visual Studio on Windows. Enjoyable. Debugger does not lockup, crash, I can see 
actual values in Qt Variables. You, know, stuff I would expect from debugging 
any modern C++ program. But the combination of OS X, with LLDB, CMake and 
QtCreator is just a non-starter at this point. Maybe someday. But not now.

I have had wonderful and enlightening conversations with a some of the Qt 
developers who kindly explained the issues as to why things are in the state 
they are in. I thank those that have enlightened me. I now have the proper 
perspective to make decisions for my company's development environment that 
allow us to be the most productive.

Cheers
Mike Jackson

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Deploying Qt to MacOs still...errr, sucks?

[René J . V . Bertin]

On Wednesday February 11 2015 13:27:37 Michael Jackson wrote:

> I was also the one that reported the MacPort dependency. And I am not really 
> comfortable just changing the install_name to point towards another library 
> of the same name but unknown as to how it was compiled or with what options. 
> I'll count that as another obvious bug and not put in a bug report.

This is a bit of a delicate matter. If Digia indeed use MacPorts to provide 
certain dependencies, it will not be that easy to avoid generic libraries like 
those reported, because it is MacPorts' principle to provide those libraries 
itself, but compiled with the default system compiler.
This is of no consequence as long as those in MacPorts are not so far ahead of 
the ones Apple ship that they become ABI incompatible. Nothing stops Digia from 
setting up (or having set up) a MacPorts environment that uses the same 
versions as Apple, and "simply" mark these ports as held, to borrow a Debian 
term.

> Now. if QtCreator could just better understand CMake projects I think I could 
> have a decent experience coding with Qt.

Do you use a lot of ObjC code? If not, you could have a look at KDevelop. I 
actually prefer it over Creator in most aspects. You'd still need Creator or 
Xcode for debugging, though, because KDevelop doesn't support lldb yet.

R.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Deploying Qt to MacOs still...errr, sucks?

[Michael Jackson]

On Feb 10, 2015, at 7:52 AM, René J.V. Bertin  wrote:

>> 
>> Em Tue Feb 10 2015 at 4:32:58 AM, Thiago Macieira 
>> escreveu:
>> 
> 
>>> That must be the same MacPorts leak issue.
> 
> Yep. The "funny" part of that issue is that Qt's own binaries are generated 
> with a HUGE "rpath" stored in them, which makes it possible to install the 
> distribution just about anywhere and still have enough margin to edit those 
> paths with a simple binary file editor (you can shorten static strings by 
> putting a nullbyte somewhere, but you cannot of course lengthen them).
> For some reason the packager decided not to use install_name_tool for that, 
> and also forgot to take care of the MacPorts dependencies.
> I don't know if install_name_tool is always present on user machines or if it 
> requires the developer tools (which are required anyway for using what the Qt 
> installer installs...). If one can rely on it, it seems a good idea to use 
> that tool to adapt the Qt libraries to the user's chosen install location and 
> handle any remaining MacPorts dependencies at the same time.
> That's all the more true if the tool allows something like `install_name_tool 
> -change /opt/local/lib /usr/lib`, i.e. a path change rather than a path+file 
> change.
> 
> R.

My guess is that the packager does not know about the 
"-headerpad_max_install_names" linker flag. This tells the linker to pad the 
"install_names" on the libraries to the max value so that one can change those 
"install_name" values. There really is NO Need to have some insanely long 
install path for the package when built. The "-headerpad_max_install_names" 
needs to be added to the Qt5 build scripts. I'll count that as an Obvious bug 
and not put in a report. 

I was also the one that reported the MacPort dependency. And I am not really 
comfortable just changing the install_name to point towards another library of 
the same name but unknown as to how it was compiled or with what options. I'll 
count that as another obvious bug and not put in a bug report.

Lastly, CMake has very good support for creating a deployable .app package for 
OS X, even when using Qt 4/5. The issue with MacDeployQt (it is generally very 
good) is that our app has its own set of plugins that also need to be adjusted 
but MacDeployQt does not allow me to send in an additional list of 
Libraries/Plugins to get adjusted. MacDeployQt actually picked up and properly 
fixed my .app package including all my third party libraries like HDF5, TBB, 
Boost, ITK.

Now. if QtCreator could just better understand CMake projects I think I could 
have a decent experience coding with Qt.

Cheers
Mike Jackson

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Deploying Qt to MacOs still...errr, sucks?

[Adam Light]

On Wed, Feb 11, 2015 at 6:08 AM, Mike Krus  wrote:

> Hi all,
>
> this tool is quite useful: https://github.com/auriamg/macdylibbundler
> does the install_name_tool dance for the libs that macdeployqt ignores.
> So I run macdeployqt, then dylibbundler
> Then I still need a script to handle other plugins (for example of OSG).
> And do the code signing…
> And build a nice dmg…
>
>
>
If you're using Qt 5 (maybe only 5.4), macdeployqt may be able to help with
the code signing and possibly the dmg part:

/qtbuild5/install/mac64/bin/macdeployqt --help

Usage: macdeployqt app-bundle [options]

Options:

   -verbose=<0-3> : 0 = no output, 1 = error/warning (default), 2 =
normal, 3 = debug

   -no-plugins: Skip plugin deployment

   -dmg   : Create a .dmg disk image

   -no-strip  : Don't run 'strip' on the binaries

   -use-debug-libs: Deploy with debug versions of frameworks and
plugins (implies -no-strip)

   -executable= : Let the given executable use the deployed
frameworks too

   -qmldir= : Deploy imports used by .qml files in the given path

   -always-overwrite  : Copy files even if the target file exists

   -codesign=  : Run codesign with the given identity on all
executables


I haven't tried using the -codesign flag because I came up with my own
script to do that before it was possible to do it using macdeployqt.

Adam
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Fwd: Qt 5.4 build error on OS X 10.7

[René J . V . Bertin]

On Wednesday February 11 2015 08:42:07 Thiago Macieira wrote:
> On Wednesday 11 February 2015 17:15:37 René J.V. Bertin wrote:
> > $D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/../../src/coreli
> > b/kernel/qmetatype.h:1943:1: error: copying variable of type
> > 'QBasicAtomicInt' (aka 'QBasicAtomicInteger') invokes deleted
> > constructor Q_DECLARE_METATYPE_TEMPLATE_2ARG(QPair)
> > ^~~
> 
> This is fixed already.
> 
> It was a missing digit in qcompilerdetection.h.

Good to know, could you point me to the fix, please?
And how come it didn't affect my build of the same code (5.4.0 tarball)? 
Exactly because I used a later compiler version?

Thanks,
R.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Fwd: Qt 5.4 build error on OS X 10.7

[Thiago Macieira]

On Wednesday 11 February 2015 17:15:37 René J.V. Bertin wrote:
> $D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/../../src/coreli
> b/kernel/qmetatype.h:1943:1: error: copying variable of type
> 'QBasicAtomicInt' (aka 'QBasicAtomicInteger') invokes deleted
> constructor Q_DECLARE_METATYPE_TEMPLATE_2ARG(QPair)
> ^~~

This is fixed already.

It was a missing digit in qcompilerdetection.h.
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Fwd: Qt 5.4 build error on OS X 10.7

[René J . V . Bertin]

Hello,

Someone is testing my MacPorts recipe (portfile) for building Qt 5.4.0 for me 
on OS X 10.7. He reports that the build procedure fails with an error message 
that neither of us can make much of:



{{{
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
 -c -Os -ffunction-secti ons -fPIC -isysroot 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk
 -std=c++11 -stdlib=libc++ -mmacosx-version-min=10.7 -fno-exceptions -Wall -W 
-DQT_NO_MTDEV -DQT_NO_LIBUDEV -DQT_NO_EV DEV -DQT_BOOTSTRAPPED 
-DQT_LITE_UNICODE -DQT_NO_CAST_TO_ASCII -DQT_NO_CODECS -DQT_NO_DATASTREAM 
-DQT_NO_LIBRARY -DQT_N O_QOBJECT -DQT_NO_SYSTEMLOCALE -DQT_NO_THREAD 
-DQT_NO_UNICODETABLES -DQT_NO_USING_NAMESPACE -DQT_NO_DEPRECATED -DQT_NO 
_TRANSLATION -DQT_QMAKE_LOCATION=\"$D/build/qtbase/bin/qmake\" 
-DQT_CRYPTOGRAPHICHASH_ONLY_SHA1 -DQT_NO_CAST_FROM_ASCII 
-DQT_BUILD_BOOTSTRAP_LIB -DQT_BUILDING_QT -DQT_ASCII_CAST_WARNINGS 
-DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS 
-DQT_DISABLE_DEPRECATED_BEFORE=0x05 -DQT_NO_EXCEPTIONS 
-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG 
-I$D/qt-everywhere-opensource-src-5.4.0/qtbase/mkspecs/macx-clang 
-I$D/qt-everywhere-opensource-src-5.4.0/qtbase/src/tools/bootstrap -I 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include 
-I$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore 
-I$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtXml 
-I$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/5.4.0 
-I$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/5.4.0/QtCore 
-I$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtXml/5.4.0 
-I$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtXml/5.4.0/QtXml 
-I../../../include -I../../../include/QtCore -I$D/build/qtbase/include/QtXml 
-I. -o .obj/qlog ging.o 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/src/corelib/global/qlogging.cpp

In file included from 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/src/corelib/global/qlogging.cpp:41:
In file included from 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/qdebug.h:1:
In file included from 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/../../src/corelib/io/qdebug.h:42:
In file included from 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/qtextstream.h:1:
In file included from 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/../../src/corelib/io/qtextstream.h:40:
In file included from 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/qlocale.h:1:
In file included from 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/../../src/corelib/tools/qlocale.h:37:
In file included from 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/qvariant.h:1:
In file included from 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/../../src/corelib/kernel/qvariant.h:40:
In file included from 
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/qmetatype.h:1:
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/../../src/corelib/kernel/qmetatype.h:1943:1:
 error: copying variable
 of type 'QBasicAtomicInt' (aka 'QBasicAtomicInteger') invokes deleted 
constructor
Q_DECLARE_METATYPE_TEMPLATE_2ARG(QPair)
^~~
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/../../src/corelib/kernel/qmetatype.h:1808:32:
 note: expanded from ma
cro 'Q_DECLARE_METATYPE_TEMPLATE_2ARG'
static QBasicAtomicInt metatype_id = Q_BASIC_ATOMIC_INITIALIZER(0); \
   ^ ~
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/../../src/corelib/kernel/qmetatype.h:1509:82:
 note: in instantiation
 of member function 'QMetaTypeId >::qt_metatype_id' 
requested here
static inline Q_DECL_CONSTEXPR int qt_metatype_id() { return 
QMetaTypeId::qt_metatype_id(); }

 ^
$D/qt-everywhere-opensource-src-5.4.0/qtbase/include/QtCore/../../src/corelib/thread/qbasicatomic.h:229:5:
 note: function has be
en explicitly marked deleted here
QBasicAtomicInteger(const QBasicAtomicInteger &) = delete;
^
1 error generated.
}}}

Can anyone here make sense of the error and indicate how to avoid it? We do 
have a number of patches that we apply for MacPorts, but those don't 
(shouldn't) affect anything related to qbasicatomic, not to my knowledge at 
least.

I admit that I've never seen this kind of construct, assigning a keyword to a 
function (constructor). Could it be that my tester isn't using a sufficiently 
recent Xcode version on OS X 10.7, and the error stems simply from a compiler 
insufficiency?

Thanks,
René
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtCreator with very high resolution laptops

[René J . V . Bertin]

On Wednesday February 11 2015 15:16:37 Portale Alessandro wrote:

> recently been added in 5.4. Here is an overview of the support:
> 
> http://doc.qt.io/qt-5/highdpi.html
> 
> Legacy widget based applications should get some High-DPI improvement by just 
> using Qt 5.4. Depending on what the applications do, some adjustment will be 
> needed, though. Especially the inclusion of high-resolution graphics/icons 
> for the High-DPI case.

Here's another interesting read: 
http://blog.davidedmundson.co.uk/blog/kde_apps_high_dpi

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtCreator with very high resolution laptops

[Portale Alessandro]

> From: Etienne Sandré-Chardonnal
>
> About making Desktop apps (legacy, non Qt Quick) working well on high DPI 
> screens, does  Qt 5 improves things significantly?

Qt 5 had High-DPI support for OSX since a few minor versions. Experimental 
High-DPI support for Windows and Linux have recently been added in 5.4. Here is 
an overview of the support:

http://doc.qt.io/qt-5/highdpi.html

Legacy widget based applications should get some High-DPI improvement by just 
using Qt 5.4. Depending on what the applications do, some adjustment will be 
needed, though. Especially the inclusion of high-resolution graphics/icons for 
the High-DPI case.

Br,
Alessandro
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] WebGL content not rendered inside QtQuick2 / QML WebView

[G. Allegri]

I'm doing some basic tests with a QML application to deliver WebGL content
on desktop apps. The basic test is the following code:

https://gist.github.com/giohappy/e1e8a788a823dead7cb8

The window is shown and the HTML content appears but no WebGL content is
shown. I've tested it with other pages (like threejs examples). It seems
that 3D content is somehow processed (at least I suppose it from my fan!),
the framerate display shows numbers, but visually I can't see any WebGL
content.

Do I miss something? Should I enable something else to support WebGL
rendering inside the WebView?

I'm using Qt 5.4 on Windows 8 with VS Express 2013

Tanks,
giovanni

-- 
Giovanni Allegri
http://about.me/giovanniallegri
Twitter: https://twitter.com/_giohappy_
blog: http://blog.spaziogis.it
GEO+ geomatica in Italia http://bit.ly/GEOplus
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Deploying Qt to MacOs still...errr, sucks?

[René J . V . Bertin]

On Wednesday February 11 2015 14:08:20 Mike Krus wrote:

I just noticed the following comment in the CMakeLists.txt file for CMake's own 
Qt app ...

  # We need to install Cocoa platform plugin and add qt.conf for Qt5 on Mac.
  # FIXME: This should be part of Qt5 CMake scripts, but unfortunatelly
  # Qt5 Mac support is missing there.


> And build a nice dmg…

To kick in an open door: if you have everything in a single "distribution" 
folder, this command will take care of things:

%> hdiutil create -srcfolder "${SRC}" -volname "${NAME}" -format UDZO -imagekey 
zlib-level=9 -o "${DMG}" "$@"

That's a bare-bones dmg, though. For a fancier looking one, I find it easier to 
keep a RW image where I just modify changed contents. Adnd exactly like that, 
btw: I don't copy whole app bundles, but the Contents folder contained therein 
(by script or by hand). I suppose that fools the Finder into thinking the app 
didn't change, and so it's less likely to mess up the layout I set up.
Once done, I simply convert the RW image to a RO, compressed one, which is a 
procedure that creates a new image and leaves my RW image untouched.

R.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Deploying Qt to MacOs still...errr, sucks?

[Mike Krus]

Hi all,

this tool is quite useful: https://github.com/auriamg/macdylibbundler 

does the install_name_tool dance for the libs that macdeployqt ignores.
So I run macdeployqt, then dylibbundler
Then I still need a script to handle other plugins (for example of OSG). 
And do the code signing…
And build a nice dmg…


Mike___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] How to deal with database specific syntax

[pmqt71]

Hi all,

in my Qt application I've to duplicate sql instructions for MySql and
Postgres due to different sql syntax.
Most problems are on date types. For instance, MySql has DATEDIFF, Postgres
has EXTRACT, CAST...

Without using ORMs, is there a way to manage specific sql syntax?


Thanks
pm
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] [ANN] ODB C++ ORM 2.4.0 Released, Adds Bulk Operations

[Boris Kolpackov]

I am pleased to announce the release of ODB 2.4.0.

ODB is an open source object-relational mapping (ORM) system for C++. It
allows you to persist C++ objects to a relational database without having
to deal with tables, columns, or SQL and without manually writing any of
the mapping code.

Major new features in this release:

 * Support for bulk operations in Oracle and SQL Server. Bulk operations
   can be used to persist, update, or erase a range of objects using a
   single database statement execution which often translates to a
   significantly better performance.

 * Ability to join and load one or more complete objects instead of, or
   in addition to, a subset of their data members with a single SELECT
   statement execution (object loading views).

 * Support for specifying object and table join types in views (LEFT,
   RIGHT, FULL, INNER, or CROSS).

 * Support for calling MySQL and SQL Server stored procedures.

 * Support for defining persistent objects as instantiations of C++ class
   templates.

A more detailed discussion of these features can be found in the following
blog post:

http://www.codesynthesis.com/~boris/blog/2015/02/11/odb-2-4-0-released/

For the complete list of new features in this version see the official
release announcement:

http://codesynthesis.com/pipermail/odb-announcements/2015/41.html

ODB is written in portable C++ (both C++98/03 and C++11 are supported) and
you should be able to use it with any modern C++ compiler. In particular, we
have tested this release on GNU/Linux (x86/x86-64/ARM), Windows (x86/x86-64),
Mac OS X (x86/x86_64), and Solaris (x86/x86-64/SPARC) with GNU g++ 4.2.x-5.x,
MS Visual C++ 2005, 2008, 2010, 2012, and 2013, Sun Studio 12u2, and Clang 3.x.

The currently supported database systems are MySQL, SQLite, PostgreSQL,
Oracle, and SQL Server. ODB also provides optional profiles for Boost and
Qt (both 4 and 5 are supported), which allow you to seamlessly use value
types, containers, and smart pointers from these libraries in your
persistent classes.

More information, documentation, source code, and pre-compiled binaries are
available from:

http://www.codesynthesis.com/products/odb/

Enjoy,
Boris
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Bluetooth support on Qt 5.5, Linux to iOS bluetooth communication.

[Blasche Alexander]

Qt 5.5 will add support for BTLE on Android and iOS. The API is mostly the 
same. Those new platform ports were the proving ground for the 5.4 API. 
Unfortunately Qt 5.5 is still limited to the BTLE central role. Peripheral mode 
is something I'd like to add at some stage but haven't been able to do so far.


--

Alex


From: interest-bounces+alexander.blasche=theqtcompany@qt-project.org 
 on behalf 
of Johannes Bell 
Sent: Wednesday, February 11, 2015 10:59
To: interest@qt-project.org
Subject: [Interest] Bluetooth support on Qt 5.5, Linux to iOS bluetooth 
communication.

Hello,
Qt 5.4 provide a Tech Preview of Bluetooth Low Energy (client side support on 
Bluez 4 & 5). My Question is how far the Qt 5.5 Bluetooth Low Energy API final 
release will supports the BTLE functionality. Especially I am interested in the 
server side support of BTLE to communicate with iOS (In Apple terms the server 
side is the peripheral role (has data) like a heart rate sensor). I want to 
connect from a iPad to a raspberry pi without using GUI on the rpi and iOS only 
support BTLE. I run in trouble doing the communication in the other direction. 
One Problem was the auto disconnect of iOS BTLE after a short time and due to 
the given role assignment (rpi=central role/wants data) the communication needs 
to be initiated from the rpi, keeping the connection by polling, what is not a 
proper solution for me. Perhaps someone has an advice or docs to help?

Thanks and Regards

Johannes
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtCreator with very high resolution laptops

[Etienne Sandré-Chardonnal]

René : yes of course, I know that code editor & debugger may be scaled. The
question was more about every other part of the UI, such as project
browser, dialogs, etc...

Alessandro : Thanks, it looks great. That means I will have to switch to Qt
5 (at least for Qt Creator!).

About making Desktop apps (legacy, non Qt Quick) working well on high DPI
screens, does  Qt 5 improves things significantly?

Thanks!

Etienne


2015-02-11 11:47 GMT+01:00 Portale Alessandro <
alessandro.port...@theqtcompany.com>:

>  Hi,
>
>
>
> This is a screenshot of Qt Creator 3.3 running on my 3k 15 Inch screen, on
> Windows:
>
>
>
> http://picpaste.com/pics/QtCreatorWindowsHighDpi.1423651325.png
>
>
>
> I launched it with environment variable “QT_DEVICE_PIXEL_RATIO” set to “2”
> and command line parameter “-style fusion”.
>
>
>
> Br,
>
> Alessandro
>
>
>
> *From:* Etienne Sandré-Chardonnal
>
>   Hi,
>
> I'm thinking of buying a new laptop for developping with Qt under Windows.
> Most high-end laptops now have very high resolution displays (3K or 4K, on
> 14-15inch screens). Is QtCreator useable on these screens? Can every text
> be upscaled so that nothing looks tiny?
>
>
>
> Thanks!
>
> Etienne
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtCreator with very high resolution laptops

[Portale Alessandro]

Hi,

This is a screenshot of Qt Creator 3.3 running on my 3k 15 Inch screen, on 
Windows:

http://picpaste.com/pics/QtCreatorWindowsHighDpi.1423651325.png

I launched it with environment variable “QT_DEVICE_PIXEL_RATIO” set to “2” and 
command line parameter “-style fusion”.

Br,
Alessandro

From: Etienne Sandré-Chardonnal

Hi,
I'm thinking of buying a new laptop for developping with Qt under Windows. Most 
high-end laptops now have very high resolution displays (3K or 4K, on 14-15inch 
screens). Is QtCreator useable on these screens? Can every text be upscaled so 
that nothing looks tiny?

Thanks!

Etienne
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtCreator with very high resolution laptops

[René J . V . Bertin]

On Wednesday February 11 2015 10:39:44 Etienne Sandré-Chardonnal wrote:

Hi

>14-15inch screens). Is QtCreator useable on these screens? Can every text
>be upscaled so that nothing looks tiny?

If it's possible I'd love to hear about it, though coming from the opposite 
side. I find that (Mac) Qt Creator's use of what Qt considers the standard font 
(Lucida Grande 13 or even 14) to lead to a UI that takes up way too much space, 
and for some reason it's even more resistant to font settings a style might 
provide than other Qt apps.
So yeah, I'd like to know if it's possible to *downscale* text to avoid wasting 
space, or else add my +1 to a request to add interface font customisation.
Etienne: surely you've seen that it's possible to select the font and typeface 
used in the editor, which ought also apply to the debugger, right?

(I say ought, because on OS X it looks like size is ignored or at least resets 
to the "system default" as soon as you do something in the debugger).

R.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Bluetooth support on Qt 5.5, Linux to iOS bluetooth communication.

[Johannes Bell]

Hello,
Qt 5.4 provide a Tech Preview of Bluetooth Low Energy (client side support
on Bluez 4 & 5). My Question is how far the Qt 5.5 Bluetooth Low Energy API
final release will supports the BTLE functionality. Especially I am
interested in the server side support of BTLE to communicate with iOS (In
Apple terms the server side is the peripheral role (has data) like a heart
rate sensor). I want to connect from a iPad to a raspberry pi without using
GUI on the rpi and iOS only support BTLE. I run in trouble doing the
communication in the other direction. One Problem was the auto disconnect
of iOS BTLE after a short time and due to the given role assignment
(rpi=central role/wants data) the communication needs to be initiated from
the rpi, keeping the connection by polling, what is not a proper solution
for me. Perhaps someone has an advice or docs to help?

Thanks and Regards

Johannes
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] QtCreator with very high resolution laptops

[Etienne Sandré-Chardonnal]

Hi,

I'm thinking of buying a new laptop for developping with Qt under Windows.
Most high-end laptops now have very high resolution displays (3K or 4K, on
14-15inch screens). Is QtCreator useable on these screens? Can every text
be upscaled so that nothing looks tiny?

Thanks!

Etienne
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest