@Christian-Ehrlicher What do you mean really make sure? I call it inside the constructor of classes of my static libraries (if the class uses resources). In my GUI application I call it in main after the application class (QApplication in this case) is created and before the main window is created.

@sierdzio Thank you.

Hi Jamie, Could you put the relevant parts in a minimal compilable example? otherwise we only can guess...

@VRHans seems i was wrong afterall: QResource::registerResource() But you have to provide the resource binary (.rcc file). Created with the following command: rcc -binary myresource.qrc -o myresource.rcc

thanks @raven-worx I've got the point and mark this one as solved thanks for your support!

I solved this problem. I just added this lines in my CMakeLists.txt qt5_add_resources(QT_RESOURCES_CPP resources/qml.qrc) add_executable(my_app src/my_app.cpp src/my_app.h ${QT_RESOURCES_CPP}) target_link_libraries(my_app lib1 lib2 ...) The problem was that I was adding my reference to QT_RESOURCES_CPP in the target_link_libraries(...) instead of add_executable(...). For some reason this didn't work properly. Thank you, Jonatan

icons depend on DevicePixelRatio and are named this way: myIcon.png - corresponds to 1.0 and mdpi - use this name in qml myIcon@2x.png - 2.0 and xhdpi myIcon@3x.png - 3.0 and xxhdpi myIcon@4x.png - 4.0 and xxxhdpi if you want to know the DevicePixelRatio: C++ qApp->primaryScreen()......

@Chris-Kawa Hi Could you pls help me understanding the last point "Use".... I have project which has four .qml files... i have created rcc from qrc...i have loaded .rcc instead of loadin qml...but still i dont know how to use it to display the window which is present in the qml.

@supaiku_ you call that necroposting? This is necroposting! I just discovered resources_big via this thread and it is a-maz-ing. It's also now documented: https://doc.qt.io/archives/qt-5.15/qtcore-cmake-qt5-add-big-resources.html I have a chunky-but-not-altogether-unexpected ~40MB referenced in my qrc, and it was blowing up with the dreaded "virtual memory exhausted: Cannot allocate memory" when compiling on a 32-bit target. No amount of exhaustive and exhausting memory tuning could prevent memory usage (not even involving swap!) from hitting the 2GB critical limit. I simply removed my qrc file from set(PROJECT_SOURCES in CMakeLists and reinstated it in qt5_add_big_resources(PROJECT_SOURCES instead. And boom, compilation blasted through the rcc step and barely broke 1GB usage getting the whole job done.

@Jakob You're welcome. I was a bit concerned that I'm not making my explanation clear enough, but happily that doesn't seem to be the case. Good luck! Kind regards.

@alex_malyu I re-read and you are right. I was sure that only the main expansion file was downloaded and that the patch file download had to be initiated by the app, but this is not the case. At least for now a work around is using two files, but I might get the same problem when the app expands. I am using Windows 7 64-bit and have tried MinGW 4.9.2 compiler on Qt 5.5, MinGW 4.9 on Qt 5.4.2 and MinGW 4.8 on 5.3. I also tried MSVC2012 on Qt 5.5. I will try post a bug report and see if someone can reproduce the same.

Hi and welcome to devnet, Glad you found out and thanks for sharing ! Since you have it working now, please update the thread title prepending [solved] so other forum users may know that a solution has been found :)

You could compile into a single exe. But that requires commercial license. Most people just combine the exe with Qt dll's. These can be found here, note that *.d.dll are for debug. C:\Qt\Qt5.4.1\5.4\mingw491_32\bin For my version at least.