[Interest] How to download QT Automotive Suite??

[Larry]

We are very interested in Qt Automotive Suite, so we want to know how to 
download and get more information about it.
Thanks !___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] using QSetting when host application is using it as well

[Frank Rueter | OHUfx]

Ok, thanks Constantin.

On 5/02/17 2:55 AM, Constantin Makshin wrote:

QtGui.QDesktopServices.storageLocation(QtGui.QDesktopServices.HomeLocation)
and os.path.expanduser('~') will return path to the user's home
directory ("C:\Users\") while the
better/more_common/proper/recommended/whatever place for configuration
files is somewhere under either "C:\Users\\AppData\Local" or
"C:\Users\\AppData\Roaming". It's somewhat like storing
settings in "~/." instead of "~/.config/" on *nix.

On 02/03/2017 06:20 AM, Frank Rueter | OHUfx wrote:

Thanks.
I'm stuck with QT 4.8.5 at the moment so QStandardPaths is not
available, but I could use QDesktopServices instead, e.g.:

QtGui.QDesktopServices.storageLocation(QtGui.QDesktopServices.HomeLocation)


What would be the difference to os.path.expanduser('~') though?

Cheers,
frank



On 2/02/17 8:19 PM, Constantin Makshin wrote:

Hi Frank.

Looks like the host application uses QSettings::setPath()
(http://doc.qt.io/qt-5/qsettings.html#setPath) to enforce a specific
directory for configuration files. Calling that method from your code is
obviously a bad idea (high risk of screwing up the host application), so
your "fallback" is the easiest solution. It'll be even better if you
replace the "~/.config" part with proper runtime detection of user
settings' directory (e.g.
QStandardPaths::writableLocation(QStandardPaths::GenericConfigLocation)).

On 02/02/2017 08:35 AM, Frank Rueter | OHUfx wrote:

In the meantime I am falling back on using this:
  os.path.expanduser('~/.config/companyName/appName')

While this does not give me the OS' native support directory for the
respective user at least it's consistent :)

I'd still be interested in a QSettings solution though.

Cheers,
frank

On 2/02/17 4:51 PM, Frank Rueter | OHUfx wrote:

Hi all,

I have been using QSettings for reading/writing user settings.
All works well until I run my (PySide) application inside a host
application that is also written in QT, and which also uses the
QSettings object.

I am now struggling to understand how I can properly differentiate
between the host application's settings instance and my own.
In particular, I need to use QSettings().fileName() to determine the
correct support path for my ini files for each platform.
But this line gives me different values inside and outside the host
application:

 QtCore.QSettings(QtCore.QSettings.IniFormat,
 QtCore.QSettings.UserScope, "companyName", "appName").fileName()

E.g.:
Outside the host application I get what I want:

 /Users/frank/.config/companyName/appName.ini

But the return value is a completely different inside the host app and
actually points to the host app's internal file structure.
Fair enough too I guess.

So my question is:
How can I use QSettings to determine support paths etc while making
sure that I don't accidentally mess with the host applications QSettings?

Cheers,
frank



___
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] 5.8.0: "Could not find feature posix_fallocate" in sqlite.pri on Windows

[Thiago Macieira]

On segunda-feira, 6 de fevereiro de 2017 22:18:14 PST m...@herrdiel.de wrote:
> Am 05.02.2017 um 19:33 schrieb Thiago Macieira:
> > [...] I was assuming that you tried to compile everything and it
> > succeeded
> > up until the point in the build that it tries to compile sqlite. Is that
> > not the case?
> 
> No, not at all - I've used the Qt installer. I've never dared to compile
> Qt myself. Sorry if I should have stated that more explicitly in my
> original post than I did, I tried to be brief and concise.

It wasn't clear, because we're talking about Sqlite here. The other SQL 
plugins often do require that you build them separately, as the client 
libraries aren't present on Windows. Even on Linux, the soname changes often 
for the MySQL library, so recompiling is often necessary.

Not so for Sqlite. The plugin should have come with your binary installation. 
So you should not need to recompile. The fact that you were trying was quite 
surprising.

BTW, why?

> > If it's not, explain what you're trying to do.
> 
> I want to compile a lib ("CuteEntityManager") that I use in my app. I

For my purposes, this is all "your code".

> use QtCreator 4.2.1 with pretty much the default settings. Compiling the
> lib works perfectly with the Qt5.7.1 kit, but with Qt5.8.0 there is the
> error message below. The compile output - in its entirety - is:
[cut]
> C:/Qt/5.8/mingw53_32/bin/qmake.exe -o Makefile
> ../../entitymanager/src/src.pro -spec win32-g++ CONFIG+=debug
> CONFIG+=qml_debug
> 
> Project ERROR: Could not find feature posix_fallocate.
> 
> Makefile:218: recipe for target 'Makefile' failed
> 
> mingw32-make[1]: Leaving directory
> 'C:/Users/SeDi/cpp/cit2/classintouch-2/ClassInTouch2/libs/build-EntityManage
> r-Desktop_Qt_5_8_0_MinGW_32bit2-Debug/src'

The problem is in entitymanager/src/src.pro. Please attach or give me a link 
to where it's present.

> I have tracked the problem down to sqlite.pri. There has been one single
> change in it from 5.7.1 to 5.8.0 - this is line 4:
> qtConfig(posix_fallocate): DEFINES += HAVE_POSIX_FALLOCATE=1

That line changing is normal and expected. What I don't get is:

a) how can this cause a problem, since clearly Qt compiled and thus the line 
worked when Qt was compiling [I have a theory, see below]

b) how sqlite.pri affects anything in your build. It's part of the Qt source 
code and simply cannot affect your code [also a theory].

> So something else must have changed between versions, that now seems to
> keep the compiler(?) from finding the "posix_fallocate" feature, whose
> very existence I had never been aware of before.

qmake, not the compiler.

My theory to explain the problem is:

The qtConfig qmake function only works inside the Qt build. It's not meant to 
be used by third-party code: that's why it works during the Qt build, but not 
when building your code.

And your code is trying to include(src/3rdparty/sqlite/sqlite.pri). That is 
not permitted. Fix your code to not do that.

-- 
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] 5.8.0: "Could not find feature posix_fallocate" in sqlite.pri on Windows

[mail]

Am 05.02.2017 um 19:33 schrieb Thiago Macieira:
[...] I was assuming that you tried to compile everything and it 
succeeded

up until the point in the build that it tries to compile sqlite. Is that not
the case?
No, not at all - I've used the Qt installer. I've never dared to compile 
Qt myself. Sorry if I should have stated that more explicitly in my 
original post than I did, I tried to be brief and concise.

If it's not, explain what you're trying to do.
I want to compile a lib ("CuteEntityManager") that I use in my app. I 
use QtCreator 4.2.1 with pretty much the default settings. Compiling the 
lib works perfectly with the Qt5.7.1 kit, but with Qt5.8.0 there is the 
error message below. The compile output - in its entirety - is:


%
20:07:29: Starting: "C:\Qt\Tools\mingw530_32\bin\mingw32-make.exe" -j9

cd src/ && ( test -e Makefile || C:/Qt/5.8/mingw53_32/bin/qmake.exe -o 
Makefile 
C:/Users/SeDi/cpp/cit2/classintouch-2/ClassInTouch2/libs/entitymanager/src/src.pro 
-spec win32-g++ CONFIG+=debug CONFIG+=qml_debug ) && 
C:/Qt/Tools/mingw530_32/bin/mingw32-make -f Makefile


mingw32-make[1]: Entering directory 
'C:/Users/SeDi/cpp/cit2/classintouch-2/ClassInTouch2/libs/build-EntityManager-Desktop_Qt_5_8_0_MinGW_32bit2-Debug/src'


C:/Qt/5.8/mingw53_32/bin/qmake.exe -o Makefile 
../../entitymanager/src/src.pro -spec win32-g++ CONFIG+=debug 
CONFIG+=qml_debug


Project ERROR: Could not find feature posix_fallocate.

Makefile:218: recipe for target 'Makefile' failed

mingw32-make[1]: Leaving directory 
'C:/Users/SeDi/cpp/cit2/classintouch-2/ClassInTouch2/libs/build-EntityManager-Desktop_Qt_5_8_0_MinGW_32bit2-Debug/src'


mingw32-make[1]: *** [Makefile] Error 3

Makefile:40: recipe for target 'sub-src-make_first-ordered' failed

mingw32-make: *** [sub-src-make_first-ordered] Error 2

20:07:31: The process "C:\Qt\Tools\mingw530_32\bin\mingw32-make.exe" 
exited with code 2.


Error while building/deploying project EntityManager (kit: Desktop Qt 
5.8.0 MinGW 32bit2)


When executing step "Make"

20:07:31: Elapsed time: 00:02.

%

I have tracked the problem down to sqlite.pri. There has been one single 
change in it from 5.7.1 to 5.8.0 - this is line 4:

%qtConfig(posix_fallocate): DEFINES += HAVE_POSIX_FALLOCATE=1%
If I deactivate this line in sqlite.pri, everything compiles and works.

In 5.7.1 the line originally was:
%contains(QT_CONFIG, posix_fallocate):DEFINES += HAVE_POSIX_FALLOCATE=1%
And this still works well under 5.7.1, but copy-pasting the line into 
5.8.0 instead of the new one doesn't do the trick either. In 5.8.0, only 
commenting out line 4 works.


So something else must have changed between versions, that now seems to 
keep the compiler(?) from finding the "posix_fallocate" feature, whose 
very existence I had never been aware of before.


Thanks,
Sebastian



--
http://www.classintouch.de  - Tablet-Software für Lehrer

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

Re: [Interest] QtCreator configure with custom compiler

[Konstantin Shegunov]

Okay, this settles it then.
Thank you!
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtCreator configure with custom compiler

[Thiago Macieira]

On segunda-feira, 6 de fevereiro de 2017 14:03:07 PST Konstantin Shegunov 
wrote:
> I don't have a separate mkspec, and this must be the reason for the
> issue. Thanks, Thiago, for the feedback. I was hoping to use the
> default g++ mkspec, as the wrapper is fully compatible with the
> installed g++, but perhaps this isn't trivial to do from Creator. What
> would be the right way to override the binary without actually
> changing anything in the default mkspec? Should I copy the g++ mkspec
> and rename it, and then just change how the compiler binary is called?

Create a new mkspec whose qmake.conf does:

include(../linux-g++/qmake.conf)
QMAKE_CC = mpicc
QMAKE_CXX = mpic++
QMAKE_LINK = $$QMAKE_LINK
QMAKE_LINK_SHLIB = $$QMAKE_LINK

> Is it possible to use the default g++ mkspec but change how the
> compiler is called (from g++ to mpic++) from inside Creator?

Qt Creator has no such power.

You can change some things in your .pro file, but that has nothing to do with 
Qt Creator.

-- 
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] [Announcement] QtWebKit Technology Preview 5

[Konstantin Tokarev]

Hi all,

QtWebKit Technology Preview 5 is out.

Highlights of these release are:

* WebGL, accelerated compositing and accelerated 2D canvas are supported now. 
Accelerated compositing is disabled by default for now, it is known to cause 
minor artifacts on some sites.

* MinGW compiler is now fully supported on Windows

This improves feature parity with previous releases of QtWebKit [1]. The only 
major remining thing is QML API (based on WebKit2) which is being worked on 
right now [2]

You can find more detailed release changelog and binary builds compatible with 
official Qt 5.8 SDK at

https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5

Big thanks to all contributors!


[1] https://github.com/annulen/webkit/wiki/Comparison-with-QtWebKit-5.6
[2] https://github.com/annulen/webkit/tree/wk2
 https://github.com/annulen/webkit/wiki/Building-WebKit2-%28WIP%29

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

Re: [Interest] QtCreator configure with custom compiler

[Konstantin Shegunov]

On Sun, Feb 5, 2017 at 8:30 PM, Thiago Macieira
 wrote:
> Maybe you should give more information on the problem.

Here's how I've configured it. I didn't do anything special, just
chose GCC as type and added the path to the binary.
https://s23.postimg.org/olw98w3vf/Screenshot_20170206_140101.png

> If your compiler is not called "g++", then you must have a mkspec, but you 
> didn't mention that.

I don't have a separate mkspec, and this must be the reason for the
issue. Thanks, Thiago, for the feedback. I was hoping to use the
default g++ mkspec, as the wrapper is fully compatible with the
installed g++, but perhaps this isn't trivial to do from Creator. What
would be the right way to override the binary without actually
changing anything in the default mkspec? Should I copy the g++ mkspec
and rename it, and then just change how the compiler binary is called?

> Also, please compile on the command-line and confirm it works. After that, let
> us know in what ways compiling inside Qt Creator changes.

I confirm, it works, probably it's bit hacky though. I add this to the
project file:
MPICC = mpicc
MPICXX = mpic++

QMAKE_CC = $$MPICC
QMAKE_CXX = $$MPICXX
QMAKE_LINK = $$MPICXX
QMAKE_LINK_SHLIB = $$MPICXX

to override the compiler binary (only) and everything is working fine.

Perhaps then I should rephrase the question:
Is it possible to use the default g++ mkspec but change how the
compiler is called (from g++ to mpic++) from inside Creator?

Thanks again!
Kind regards.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest