1

Topic: .qrc AND precompiled headers

Whether there is a method to explain rcc that it is necessary to compile.qrc for the project with  titles? At moc for this purpose there is a parameter-b, but at rcc it is not present version 5.6. It is used CMake, not qmake. PS I correctly understood, what support  in Qt still is not present resources from a word absolutely?

2

Re: .qrc AND precompiled headers

Hello, BigBoss, you wrote: whether BB> There is a method to explain rcc that it is necessary to compile.qrc for the project with  titles? At moc for this purpose there is a parameter-b, but at rcc it is not present version 5.6. It is used CMake, not qmake. And than you in cmake fasten PCH? And in what, actually, a problem? I truth manually pull qt5_add_resources (QRC_LIST $ {QRC_FILES}) BB> PS I correctly understood, what support  in Qt still is not present resources from a word absolutely? It is not present and is not necessary, since it is not supported by target platforms.

3

Re: .qrc AND precompiled headers

Hello, BigBoss, you wrote: BB>... It is used CMake, not qmake. Tell better as from qmake to pass on CMake...

4

Re: .qrc AND precompiled headers

Hello, MasterZiv, you wrote: MZ> Tell better as from qmake to pass on CMake... To Study CMake, to rewrite  scripts? Examples: https://github.com/mailru/icqdesktop https://github.com/dava/dava.engine/tre … rces/CMake

5

Re: .qrc AND precompiled headers

Hello, SaZ, you wrote: SaZ> Hello, BigBoss, you wrote: whether BB>> There is a method to explain rcc that it is necessary to compile.qrc for the project with  titles? At moc for this purpose there is a parameter-b, but at rcc it is not present version 5.6. It is used CMake, not qmake. SaZ> And than you in cmake fasten PCH? At us  assembly system. SaZ> and in what, actually, a problem? I truth manually pull qt5_add_resources (QRC_LIST $ {QRC_FILES}) MSVC something like #include "stdafx.h" in the beginning of everyone c ++ wants a file if are resolved pch. rcc from a box so is not able, here I and ask. BB>> PS I correctly understood, what support  in Qt still is not present resources from a word absolutely? SaZ> Is not present and it is not necessary, since it is not supported by target platforms. The purposes at all, of course, different But in any jacket graphic applications have icons, for example. On me so it would be reasonable, if the same QIcon itself was able them it is necessary to read whence instead of storing the second copy of "resources" among the data.

6

Re: .qrc AND precompiled headers

Hello, MasterZiv, you wrote: MZ> Hello, BigBoss, you wrote: BB>>... It is used CMake, not qmake. MZ> Tell better as from qmake to pass on CMake... In what a problem that? The chief comes, speaks that now all will be in CMake. And all

7

Re: .qrc AND precompiled headers

Hello, BigBoss, you wrote: BB> At us  assembly system. SaZ>> and in what, actually, a problem? I truth manually pull qt5_add_resources (QRC_LIST $ {QRC_FILES}) BB> MSVC something like #include "stdafx.h" in the beginning of everyone c ++ wants a file if are resolved pch. rcc from a box so is not able, here I and ask. There is an option "Configuration Properties\C/C ++\Advanced\Forced Include File", register there for the project $ (ProjectDir) src/precompiled.h; % (ForcedIncludeFiles), also it is not necessary to register hands in each file #include "stdafx.h".

8

Re: .qrc AND precompiled headers

Hello, BigBoss, you wrote: BB> At us  assembly system. So and here cmake? BB> MSVC something like #include "stdafx.h" in the beginning of everyone c ++ wants a file if are resolved pch. He wants that to it registered in Use Precompiled Header. BB> rcc from a box so is not able, here I and ask. What exactly is not able? rcc all collects, cmake too. BB> the Purposes at all, of course, different But in any jacket graphic applications have icons, for example. On me so it would be reasonable, if the same QIcon itself was able them it is necessary to read whence instead of storing the second copy of "resources" among the data. No, not reasonably. It is much more convenient, when all resources lie in one place with an identical principle of access. And for the sake of a beautiful icon on an application icon it is possible and.rc a file pens . Though, I somehow time fastened parcer PE that under  to draw out localization from  resources (since to the project The project was ancient and all tools of localization were on MFC, ground under  resources). It appeared much easier, than to saw all localization system.