@Norzka said in Problems with building qt from source (it doesn't generate lib files): D:\Libraries\Qt\6.6.0\Build\plugins\styles\qwindowsvistastyle.lib Hang on, why do you expect a .lib file for a plugin, that is supposed not to be linked to (it is loaded at runtime)? There should be a .dll, but not a .lib file. Do you (try to) explicitly link against the plugin nevertheless, in your project file? Or do you somehow try a static build (which would require Qt to be built statically, too)?

@Dariusz said in QT Sdk - practive, can one private object access another one?: Would it not make sense if a private class can access other widget's private classes? No. Private is there for a reason. Private stuff should not be accesed directly by the outside world. If there is no public API yet for something and it is really needed, then it needs to be added. But this is not a reason to break encapsulating by allowing direct access to private APIs. Also, in C++ you can't access private members/methods from other classes without making these classes friends. Nothing Qt can do about (and it also should not). And as @SGaist pointed out: the PIMPL design pattern is there to prevent ABI from changing if internal implementation changes. Means: if you change something in the private implementation without changing public API, then the user code does not have to be rebuilt. Since you can't restrict access to private APIs to private classes (like what your example shows: widget->getPrivate()) also non-private classes would be able to access those interfaces and (even worse) user code.

@_ove_ said in Qt 6.1.2 on Windows x64, lots of errors configuring build from source: By now I have realized the compilation process has of a lot of dependencies that I cannot find documented anywhere. https://doc.qt.io/qt-6/windows-building.html https://wiki.qt.io/Building_Qt_6_from_Git

Okay, I think the problem here is that I was doing 'jom release' when I built it and that just doesn't seem to work. If I just do 'jom', it seems to work fine.

Hi, I described the steps I followed in a post over here, https://mechatronicsblog.com/cross-compile-and-deploy-qt-5-12-for-raspberry-pi/ Some people found some issues and posted comments there, the “qendian” issue seems to be related to this bug, there is also a patch there. https://bugreports.qt.io/browse/QTBUG-71945

Ok, thank You so much. I will try to do it, tomorrow.

Thanks @J-Hilk The link provided needs other configuration. My machine configuration is Red Hat Linux - 32 bit Qt creator 1.2.92, based on Qt 4.6.0 (32 bit) Make version: GNU Make 3.81 Qmake version: 1.07a (Qt 3.3.6) Please let me know what are the pre-requisites for a plugin. I want to create a menu item for Qt creator. Thanks in advance.

@michalos Well knowing windows searching, i always cheat and use https://www.voidtools.com/ On NTFS drives, it will find anything really fast and takes wildcards. Its only for filenames but on the other hand, it finds a file in secs even on a 4 TB drive. :)

@SGaist thank you for that! That took care of the qtquickcontrols2. Now I just have a hand full of other modules I need to build and install, according to these errors: /Live3DWidget.qml:4 module "QtQuick.Scene3D" is not installed /Live3DWidget.qml:9 module "Qt3D.Extras" is not installed /Live3DWidget.qml:7 module "Qt3D.Render" is not installed /Live3DWidget.qml:6 module "Qt3D.Core" is not installed /Live3DWidget.qml:8 module "Qt3D.Input" is not installed /Live3DWidget.qml:4 module "QtQuick.Scene3D" is not installed /Live3DWidget.qml:9 module "Qt3D.Extras" is not installed /Live3DWidget.qml:7 module "Qt3D.Render" is not installed /Live3DWidget.qml:6 module "Qt3D.Core" is not installed /Live3DWidget.qml:8 module "Qt3D.Input" is not installed /Live3DWidget.qml:4 module "QtQuick.Scene3D" is not installed /Live3DWidget.qml:9 module "Qt3D.Extras" is not installed /Live3DWidget.qml:7 module "Qt3D.Render" is not installed /Live3DWidget.qml:6 module "Qt3D.Core" is not installed /Live3DWidget.qml:8 module "Qt3D.Input" is not installed /Live3DWidget.qml:4 module "QtQuick.Scene3D" is not installed /Live3DWidget.qml:9 module "Qt3D.Extras" is not installed /Live3DWidget.qml:7 module "Qt3D.Render" is not installed /Live3DWidget.qml:6 module "Qt3D.Core" is not installed /Live3DWidget.qml:8 module "Qt3D.Input" is not installed /Live3DWidget.qml:4 module "QtQuick.Scene3D" is not installed /Live3DWidget.qml:9 module "Qt3D.Extras" is not installed /Live3DWidget.qml:7 module "Qt3D.Render" is not installed /Live3DWidget.qml:6 module "Qt3D.Core" is not installed /Live3DWidget.qml:8 module "Qt3D.Input" is not installed I will try to install relevant modules and try again. Will report back.

You have here a list of the modules and their state. QtWebkit as been deprecated and removed. QtQuick1 as been deprecated and removed You can still build them from sources but you have to clone them specifically.

Looks like you built the qtscript module successfully, that's why I'm asking whether you ran make install before trying to build the example.

@Mark81 Yes both the Hello World and content of the variable were shown. Again it's on OS X with a recent version of bash.

Hi @JKSH, @Leonardo, Many thanks for your tips and apologies for delay. I got distracted by another task, but will get back to this one again. Just to report what happened so far. All my attempts on one machine failed. Switching to another computer I managed to to statically build Qt and Qt Creator once (using your receipts), but failed to reproduce that again. I'm putting all this down to my inexperience on Windows platform. However, I have learnt a lot and I'll get back to this problem again. BTW, working with VS is not as scary as it originally looked :-). Once I managed to install it, that is. The installation of VS was a pain as due to my inexperience and some bugs. E.g. installing VS via RDC produces a transparent window - I waiting for hours for something to happen, then tried another version of VS, ... Best, J.

Oh well, I had a typo in my config path, sorry ! Configure and make work well now! cheers Manfred