Re: [Interest] L Word

[Giuseppe D'Angelo via Interest]

On 29/04/2021 00:08, Roland Hughes wrote:


On 4/21/21 5:00 AM, Giuseppe D'Angelo wrote:

On your right: witness B, found to be lying multiple times in the past


I have never lied in here. Been incorrect at times? Most assuredly at 
some point. I have never lied.


https://plato.stanford.edu/entries/lying-definition/

=

(L1)To lie =_df to make a believed-false statement to another person 
with the intention that the other person believe that statement to be true.


L1 is the traditional definition of lying. According to L1, there are at 
least four necessary conditions for lying. First, lying requires that a 
person make a statement (statement condition). Second, **lying requires 
that the person believe the statement to be false**; that is, lying 
requires that the statement be untruthful (untruthfulness condition). 
Third, lying requires that the untruthful statement be made to another 
person (addressee condition). Fourth, lying requires that the person 
intend that that other person believe the untruthful statement to be 
true (intention to deceive the addressee condition).




Fantastic! Let's go with this, with a random example: did you or did you 
not believe that operator new was "deprecated in C++20 and slated for 
removal in C++23", and that smart pointers "most likely they will go 
away with "new.""?



https://lists.qt-project.org/pipermail/interest/2019-December/034245.html


If the answer is yes, you were lying. If the answer is no, or you don't 
answer, then you're trolling the mailing list. You'll get my apology; 
I'll even throw in, for free, my personal congratulations for the long 
trolling. But, you'll get a nice permanent ban from here.




Long ago I came to terms with every Usenet news group or Internet 
mailing list comes one troll with a God complex. They have skin ten 
thousands of an inch thick and consider everything a personal insult. 
For whatever reason, you've chosen to be that here. Fine.


Ha ha ha ha.


What I can't understand is why the moderators haven't yet put you on a 
forced 18+month vacation, especially given all of the emails coming 
around off-list.


Oh really? Have I contacted YOU off-list? Could you produce an example? 
(You may have noticed that my emails are cryptographically signed, so 
good luck with this).


Or someone else contacted you off-list? In which case, you must be so 
lucky at having so many dedicated fans writing directly to you. If only 
they came forward here contributing to the discussions, this mailing 
list would be much more alive.




Here's the thing.

[snip of a huge, nonsensical 


**lying requires that the person believe the statement to be false**

__OR__

You can make amends, here, publicly, and go away for a while whether it 
is imposed or not.


Failing that I will have to pursue this via other avenues.


Get out.


--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: S/MIME Cryptographic Signature
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] L Word

[Roland Hughes via Interest]

On 4/21/21 5:00 AM, Giuseppe D'Angelo wrote:

On your right: witness B, found to be lying multiple times in the past


I have never lied in here. Been incorrect at times? Most assuredly at 
some point. I have never lied.


https://plato.stanford.edu/entries/lying-definition/

=

(L1)To lie =_df to make a believed-false statement to another person 
with the intention that the other person believe that statement to be true.


L1 is the traditional definition of lying. According to L1, there are at 
least four necessary conditions for lying. First, lying requires that a 
person make a statement (statement condition). Second, **lying requires 
that the person believe the statement to be false**; that is, lying 
requires that the statement be untruthful (untruthfulness condition). 
Third, lying requires that the untruthful statement be made to another 
person (addressee condition). Fourth, lying requires that the person 
intend that that other person believe the untruthful statement to be 
true (intention to deceive the addressee condition).


=

Long ago I came to terms with every Usenet news group or Internet 
mailing list comes one troll with a God complex. They have skin ten 
thousands of an inch thick and consider everything a personal insult. 
For whatever reason, you've chosen to be that here. Fine.


What I can't understand is why the moderators haven't yet put you on a 
forced 18+month vacation, especially given all of the emails coming 
around off-list.


Here's the thing.

I don't care when Internet trolls call me names or even when they accuse 
me of vile physical relationships with blood relatives, family pets, or 
farm animals. It's what trolls do. Be on the Internet long enough and 
you figure it out. Apparently I have rather thick skin because I 
generally don't even notice things others call personal insults. I don't 
care when people try to hold up my code and laugh at it. Very few things 
I write compile on the very first attempt. Most certainly they tend to 
compile and run incorrectly until I track down the major issues and some 
of the minor ones. Generally I'm confident that I have many thousands 
(many tens of thousands most likely) of code in devices that are helping 
to save lives each and every day. Most of the people who try to laugh at 
my code don't have that, and I know this.


None of that bothers me in general. It might irritate at the end of a 
particularly long and frustrating day, but in general it's just gas.


When you made that statement, you jumped with both feet onto the L Word.

https://www.law.cornell.edu/wex/libel

You weren't directly responding to a single statement with something 
like "That's a lie" stating disbelief. You directly attacked my 
professional integrity without citation.


Before you go reaching for the old chestnut of K with no meaning be advised:

=

in Message-ID: <10924316.ADL2evRJuH@tjmaciei-mobl1> Thiago stated

The KDE representative to the KDE Free Qt Foundation was also there and 
he says he's

the one who tried to retroactively call it "Kool" but it didn't stick.

That's the opposite of Linux, where the original author had a different name
for his project when he first uploaded it and it didn't stick.

=

My statements were based on the official upload/entry/registration. 
Everybody arguing with me had a passion for a development code name. 
They don't appear to have the same passion when it comes to Windows 10. 
I don't hear any of them calling it Redstone, Santorini, Vibranium, etc.


https://en.wikipedia.org/wiki/List_of_Microsoft_codenames

People remember from official release and registration. That's what 
people (not me) are writing books about.


Hopefully you aren't going to reach for what Tweedle Dee and Tweedle Dum 
discussed with me on dart nights at Two Rivers because nobody in this 
list was there.


Sadly, you did this using your kdab.com email address, thus exposing 
them as well.


I guess I can give you until end of day on Monday (locally for me in the 
Chicago timezone) to scrounge through the archives and identify at least 
two messages from me (you did say multiple) that meet the Standford 
definition of a lie. You can't, but I'm willing to let you try. Keep 
this in mind:


**lying requires that the person believe the statement to be false**

__OR__

You can make amends, here, publicly, and go away for a while whether it 
is imposed or not.


Failing that I will have to pursue this via other avenues.

My apologies to everyone else for them having to read this.

--
Roland Hughes, President
Logikal Solutions
(630)-205-1593

http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog

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

Re: [Interest] Porting custom QML plugin to the Qt6

[Ulf Hermann]

Hi Jakub,

nice to hear someone is trying the fancy new QML type registration!


[...]
I spotted, I believe, the most important changes. QQmlExtensionPlugin 
being changed to QmlEngineExtensionPlugin, QML_ELEMENT added in Qt 
5.15.X and removal of QQmlExtensionPlugin::registerTypes.


Technically, QQmlExtensionPlugin with its cruft is still there, but 
indeed you shouldn't use it. The new CMake API will default to 
auto-generating a minimal optional plugin. The actual meat of the QML 
types will then be in a backing library that you can directly link into 
your application. This way it won't have to load the plugin at all.


Then I noticed stuff about QML_IMPORT_NAME, QML_IMPORT_MAJOR_VERSION and 
'CONFIG += qmltypes' that are supposed to be added to the .pro project 
files. And, although, docs are silent about CMake, there is handy 
example located at:
https://code.qt.io/cgit/qt/qtdeclarative.git/tree/examples/qml/qmlextensionplugins/CMakeLists.txt?h=6.0 


Well, yes, the CMake API is in tech preview right now, and it will 
change quite a bit.



[...] > omitting, for the moment, the "QT_QMLTYPES_FILENAME
imports/TimeExample/plugins.qmltypes" as I was typically generating 
.qmltypes manually using the supplied qmlplugindump and some associated 
CMake hackery.


Don't do this. qmlplugindump is deprecated. qmltyperegistrar can 
generate better qmltypes files.



[...]

But! My includes are not available under  but 
rather under "IzLibrary/SomeBeautifulHeader.h" as denoted by my 
target_include_directories:


# include directories for target
target_include_directories(
     IzLibraryPlugin
PUBLIC
     $
     $
PRIVATE
     ${CMAKE_CURRENT_SOURCE_DIR}/private
)

So, my questions (for now :P) are:
Is this the intended behavior or have I fubared something and not added 
"something, somewhere" in my CMakeLists.txt?


This is expected. You need to make the headers for your QML-exposed 
types available in the include paths for the generated code to find it. 
An -IIzLibrary should fix this. Anything else would be a series of never 
ending headaches, considering the different paths of your sources and 
generated files in source, build, and install directories. Also, the 
metatype information is generated by moc and moc doesn't know where your 
"reference" path should be.



Is there a documentation for the qt6_* cmake functions?


Not yet. The CMake API is being redesigned right now. Don't expect 
anything to stay the same.



Is the stuff "qt6_add_qml_module" important or can I skip it?


That will indeed be the way to add QML modules. However, what you 
currently see there is not very useful.


cheers,
Ulf
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Locale detection of Qt application hosted via WASM

[Elvis Stansvik]

Den ons 28 apr. 2021 kl 22:05 skrev Thorsten Glaser :
>
> On Wed, 28 Apr 2021, Elvis Stansvik wrote:
>
> > Agree to put in an option to change language, but surely it should be
> > possible to have the default be based on the language the user has set
> > in the OS/browser, just like many web applications do? (not
>
> Sure, as last resort, if the user has not yet set a cookie or so,
> or connected a language with their account profile, this could
> determine the default language. You’re going to need a default
> anyway.

The language of the browser is going to be the desired one in the vast
majority of cases, so I would rather think of the unusual cases, such
as using someone elses computer or wanting a different language for
some other reason, where the user needs to actively change the
language, as the last resort.

>
> This is why I said make the language selection very discoverable
> (use icons, not just names; don’t place it too small in the
> bottom of the page, etc).

Agreed.

Elvis

>
> bye,
> //mirabilos
> --
> Infrastrukturexperte • tarent solutions GmbH
> Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
> Telephon +49 228 54881-393 • Fax: +49 228 54881-235
> HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
> Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
>
> *
>
> Mit dem tarent-Newsletter nichts mehr verpassen: www.tarent.de/newsletter
>
> *
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Locale detection of Qt application hosted via WASM

[Thorsten Glaser]

On Wed, 28 Apr 2021, Elvis Stansvik wrote:

> Agree to put in an option to change language, but surely it should be
> possible to have the default be based on the language the user has set
> in the OS/browser, just like many web applications do? (not

Sure, as last resort, if the user has not yet set a cookie or so,
or connected a language with their account profile, this could
determine the default language. You’re going to need a default
anyway.

This is why I said make the language selection very discoverable
(use icons, not just names; don’t place it too small in the
bottom of the page, etc).

bye,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

Mit dem tarent-Newsletter nichts mehr verpassen: www.tarent.de/newsletter

*
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Porting custom QML plugin to the Qt6

[Jakub Narolewski]

Lately, mostly for fame and glory, I decided to port some of my stuff from Qt5 to Qt6. 
Most of it went ok'ish - after some CMakeLists.txt hacking and 'modernizing' the code I 
was able to compile two of my dynamic libraries under Qt6.


Problems started with my custom QML plugin. Here after compiling and importing my module 
in my example app I got:

"qrc:/src/QML/MainWindow.qml:5:1: module "IzLibrary" plugin "IzLibraryPlugin" not 
found"

Well oopsie doopsie, some more work is needed. After quick look at:
https://doc.qt.io/qt-6/qtqml-modules-cppplugins.html

I spotted, I believe, the most important changes. QQmlExtensionPlugin being changed to 
QmlEngineExtensionPlugin, QML_ELEMENT added in Qt 5.15.X and removal of 
QQmlExtensionPlugin::registerTypes.


Then I noticed stuff about QML_IMPORT_NAME, QML_IMPORT_MAJOR_VERSION and 'CONFIG += 
qmltypes' that are supposed to be added to the .pro project files. And, although, docs are 
silent about CMake, there is handy example located at:

https://code.qt.io/cgit/qt/qtdeclarative.git/tree/examples/qml/qmlextensionplugins/CMakeLists.txt?h=6.0

I added to my CMakeLists.txt:

set_target_properties(
IzLibraryPlugin
PROPERTIES
QT_QML_MODULE_VERSION 1.0
QT_QML_MODULE_URI IzLibrary
)

omitting, for the moment, the "QT_QMLTYPES_FILENAME imports/TimeExample/plugins.qmltypes" 
as I was typically generating .qmltypes manually using the supplied qmlplugindump and some 
associated CMake hackery.


I also added the:

qt6_qml_type_registration(IzLibraryPlugin)

And this is when first build error occurred. qt6_qml_type_registration seems to be trying 
to automate some of the QML type registration machinery and generates the 
"izlibraryplugin_qmltyperegistrations.cpp" file. In my case it looks like this:


#include 
#include 

#include 
#include 
#include 

void qml_register_types_IzLibrary()
{
qmlRegisterTypesAndRevisions("IzLibrary", 1);
qmlRegisterTypesAndRevisions("IzLibrary", 1);
qmlRegisterTypesAndRevisions("IzLibrary", 1);
QMetaType::fromType().id();
QMetaType::fromType().id();
qmlRegisterModule("IzLibrary", 1, 0);
}

static const QQmlModuleRegistration registration("IzLibrary", 
qml_register_types_IzLibrary);


But! My includes are not available under  but rather under 
"IzLibrary/SomeBeautifulHeader.h" as denoted by my target_include_directories:


# include directories for target
target_include_directories(
IzLibraryPlugin
PUBLIC
$
$
PRIVATE
${CMAKE_CURRENT_SOURCE_DIR}/private
)

So, my questions (for now :P) are:
Is this the intended behavior or have I fubared something and not added "something, 
somewhere" in my CMakeLists.txt?

Is there a documentation for the qt6_* cmake functions?
Is the stuff "qt6_add_qml_module" important or can I skip it?
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Locale detection of Qt application hosted via WASM

[Elvis Stansvik]

Den ons 28 apr. 2021 kl 18:57 skrev Thorsten Glaser :
>
> On Wed, 28 Apr 2021, Nicholas Yue wrote:
>
> > I am new to locale handling in general and definitely new to locale on the
> > web browser.
>
> If you’re targetting a webbrowser, make the language selectable in
> the software itself. Anything else is an affront: both geolocation
> and browser language preferences fail, e.g. when in an Internet
> Café in a foreign country. Make it easily enough reachable and
> discoverable so it’ll be of use to all kinds of users. Then set
> the language of the application based on it and, perhaps, even
> store the chosen language in a cookie. DO NOT rely on either of the
> other possible language sources.

Agree to put in an option to change language, but surely it should be
possible to have the default be based on the language the user has set
in the OS/browser, just like many web applications do? (not
geolocation though, agree that is a bad basis for default language).

Elvis

>
> bye,
> //mirabilos
> --
> Infrastrukturexperte • tarent solutions GmbH
> Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
> Telephon +49 228 54881-393 • Fax: +49 228 54881-235
> HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
> Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
>
> *
>
> Mit dem tarent-Newsletter nichts mehr verpassen: www.tarent.de/newsletter
>
> *
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Locale detection of Qt application hosted via WASM

[Nicholas Yue]

Thank you Thorsten for the insight :-)

On Wed, 28 Apr 2021 at 09:55, Thorsten Glaser  wrote:

> On Wed, 28 Apr 2021, Nicholas Yue wrote:
>
> > I am new to locale handling in general and definitely new to locale on
> the
> > web browser.
>
> If you’re targetting a webbrowser, make the language selectable in
> the software itself. Anything else is an affront: both geolocation
> and browser language preferences fail, e.g. when in an Internet
> Café in a foreign country. Make it easily enough reachable and
> discoverable so it’ll be of use to all kinds of users. Then set
> the language of the application based on it and, perhaps, even
> store the chosen language in a cookie. DO NOT rely on either of the
> other possible language sources.
>
> bye,
> //mirabilos
> --
> Infrastrukturexperte • tarent solutions GmbH
> Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
> Telephon +49 228 54881-393 • Fax: +49 228 54881-235
> HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
> Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander
> Steeg
>
> *
>
> Mit dem tarent-Newsletter nichts mehr verpassen: www.tarent.de/newsletter
>
> *
>


-- 
Nicholas Yue
Graphics - Arnold, Alembic, RenderMan, OpenGL, HDF5
Custom Dev - C++ porting, OSX, Linux, Windows
http://au.linkedin.com/in/nicholasyue
https://vimeo.com/channels/naiadtools
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Locale detection of Qt application hosted via WASM

[Thorsten Glaser]

On Wed, 28 Apr 2021, Nicholas Yue wrote:

> I am new to locale handling in general and definitely new to locale on the
> web browser.

If you’re targetting a webbrowser, make the language selectable in
the software itself. Anything else is an affront: both geolocation
and browser language preferences fail, e.g. when in an Internet
Café in a foreign country. Make it easily enough reachable and
discoverable so it’ll be of use to all kinds of users. Then set
the language of the application based on it and, perhaps, even
store the chosen language in a cookie. DO NOT rely on either of the
other possible language sources.

bye,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

Mit dem tarent-Newsletter nichts mehr verpassen: www.tarent.de/newsletter

*
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Locale detection of Qt application hosted via WASM

[Nicholas Yue]

Hi,

I have the following code (part of a small project) which is being built
both as a standalone executable and a wasm web application.

They both work except the locale determination.

On my Linux console, I can set the LANGUAGE environment to de and the
executable will load the correct labels

However, when I run it wasm web app and connect to it via a German language
OS web browser, it keeps thinking that the locale is still "C" and not
"de_DE"

I am new to locale handling in general and definitely new to locale on the
web browser.

I am developing with Qt 5.14.0

Code ===
#include 
#include 
#include 
#include 
#include 
#include "CMEForm.h"

int main(int argc, char *argv[]) {

QApplication app(argc, argv);
QTranslator translator;


std::cout << "Locale is " << QLocale::system().name().toStdString() <<
std::endl;
if (QLocale::system().name().startsWith("de_")) {
if (translator.load(":/language/.qm/cme_de.qm")) {
app.installTranslator();
} else {
std::cerr << "ERROR: Translation failure to load" << std::endl;
}
}

CMEForm cme;
cme.show();

return app.exec();

}

-- 
Nicholas Yue
Graphics - Arnold, Alembic, RenderMan, OpenGL, HDF5
Custom Dev - C++ porting, OSX, Linux, Windows
http://au.linkedin.com/in/nicholasyue
https://vimeo.com/channels/naiadtools
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] How to actually use QSGRenderNode?

[Nuno Santos]

Hi,

I’m trying to make use of QSGRenderNode in order to change the glBlendFunc to a 
custom mode.

https://doc.qt.io/qt-5/qsgrendernode.html 


However, I don’t can’t understand how to make proper use of this class since 
all the experiments I have run, didn’t result in any change at all. 

Below is the node architecture:

BASE NODE
LAYER NODE 1
CHILD NODE 1
CHILD NODE 2
LAYER NODE 2
CHILD NODE 1
CHILD NODE 2

Each child node is using a custom QSGMaterial to draw a custom shader. 

The goal is to affect the way the color blends.

Does QSGRenderNode will allow me in any to achieve this? How?

Thanks!

Regards,

Nuno___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt permanently broke on computer

[Andrei Golubev]

Hi Jason and everyone,

This looks like a typical issue with not found QPA [1] plugin to me. If you 
build from source, make sure that you really build *everything*. QPA plugins 
are dynamically loaded (hence, plugins) and do not explicitly link against any 
target (thus they are excluded from build dependencies) which means that if you 
build a specific part of Qt (e.g. only QtCore + QtGui + something else), they 
might not be built at all. I guess on windows you're looking for something 
called QWindowsIntergrationPlugin (see [1]).
If you build everything, then probably the discovery inside Qt couldn't find 
the plugin for some reason (you might want to experiment with PATH env var).

Also, feel free to add a bug report if the issue does not seem solvable (IIRC 
there's "QPA: Windows" component that you could use in the bug report). You 
also mention deployment, so maybe something goes wrong during that step.

[1] https://doc.qt.io/qt-6/qpa.html
Qt Platform Abstraction | Platform Integration 
6.0.3
The Qt Platform Abstraction (QPA) is the main platform abstraction layer in Qt. 
The API can be identified by the QPlatform* class prefix, and is used for 
implementing higher level classes typically found in Qt GUI, e.g. 
QPlatformWindow for window system integration exposed through QWindow, or 
QPlatformTheme for deeper platform theming and integration, exposed through 
QStyleHint and QStyle.
doc.qt.io


--
Best Regards,
Andrei

From: Interest  on behalf of J?r?me Godbout 

Sent: Monday, April 26, 2021 7:30 PM
To: Jason H 
Cc: interestqt-project.org 
Subject: Re: [Interest] Qt permanently broke on computer


You might try to delete the .user files for the project and clean the build 
folder manually (erase the whole folder). Check the project config to spot any 
differences there. If some project work with the same Qt version, the Qt 
install is probably good. Make sure all you dependencies are ok.





From: Interest  on behalf of Jason H 

Date: Monday, April 26, 2021 at 11:11 AM
To: Jason H 
Cc: interestqt-project.org 
Subject: Re: [Interest] Qt permanently broke on computer


> Sent: Monday, April 26, 2021 at 11:01 AM
> From: "Jason H" 
> To: "Jason H" 
> Cc: "interestqt-project.org" 
> Subject: Re: [Interest] Qt permanently broke on computer
>
> > I tried to port an app on a Win10 PC. That went well. Then I tried to 
> > deploy (windeployqt) it.
> >
> > Now when I run it in creator I get:
> > 10:26:28: Starting 
> > C:\Users\Admin\Projects\build-phidget-spinner-Desktop_Qt_5_15_2_MinGW_64_bit-Debug\debug\phidget-spinner.exe
> >  ...
> > qt.qpa.plugin: Could not find the Qt platform plugin "windows" in ""
> >
> > I have deleted the C:\Qt dir and re-installed.
> > I have cleaned the app source dir and deleted the shadow build dirs, 
> > deleted the .pro.user file,
> > I launched QtC from the start menu.
> >
> > I have no idea how to get this working again.
>
> Some additional info:
> Other projects work.
> The crash is in this statement:
> QGuiApplication app(argc, argv);
>
> the stack indicates a crash starting at:
> QGuiApplicationPrivate::createPlatformIntegration()
>
>
> All the online help (stackexchange) seems to be about deployment, but I'm 
> just trying to run it in creator.

Update #2:

The same thing happens on a totaly new computer, never had qt on it before, 
installed Qt, copied the source and built it, some error.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Svar: Qt permanently broke on computer

[Kai Köhne]

> Von: Interest  Im Auftrag von Jason H
> Betreff: Re: [Interest] Svar: Qt permanently broke on computer
>
> Good news everybody, I have partialyl figured it out, but I hope you can help 
> me further.
> 
> MYPROJ = ../phidget-spinner
> win32 {
>INCLUDEPATH +=$$MYPROJ/libraries/phidget22-windevel/lib/c
> #this works:
>LIBS +=-L$$PWD/../phidget-spinner/libraries/phidget22-windevel/lib/c/x64 
> -lphidget22
> #these breaks Qt (each):
>   LIBS +=-L$$MYPROJ/libraries/phidget22-windevel/lib/c/x64 -lphidget22
>   LIBS +=-L"$${MYPROJ}/libraries/phidget22-windevel/lib/c/x64" -lphidget22
>   LIBS +=-L$${MYPROJ}/libraries/phidget22-windevel/lib/c/x64 -lphidget22
> }
[...]
>Not sure why $$MYPROJ works for INCLUDEPATH but breaks the linker? 

You're probably using a shadow build directory (that is, build directory != 
source directory), which is the default of Qt Creator.

INCLUDEPATH is a qmake variable. qmake will see that it is a relative path, and 
make it relative to the build directory. That is, what's passed to the compiler 
isn't -I../phidget-spinner/libraries/phidget22-windevel/lib/c , but something 
like 
-Ibuild-myproject-5_15_msvc_2019_amd64-Debug/../myproject/phidget-spinner/libraries/phidget22-windevel/lib/c

Now for the library search path, LIBS is added (more or less) directly to the 
linker command line. And for the linker, the 'current working directory' is the 
build directory.

IIRC you can use LIBPATH to get the same effect as with INCLUDEPATH. Anyhow, 
the qmake documentation recommends using LIBS in the way you did... The easy 
fix (as you found out) is to use absolute paths here.

> If the link path is wrong I would expect it to fail the build, bot break Qt?

It's hard to say what happened for you. Maybe you had another version of your 
libraries registered in the environment, which were picked up instead?

Regards

Kai
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest