qmake & mocing problem
-
Hi,
Do you have QObject based classes in your project ?
How are they declared ?
What version of Qt are you using ?
On what OS ? -
@VeNToR said in qmake & mocing problem:
@SGaist, same problem for regular examples...
What do you mean by that ?
-
@VeNToR said in qmake & mocing problem:
@SGaist, same problem for regular examples...
What do you mean by that ?
-
I'm not sure I'm following you there.
Does it also happen in a local folder ?
-
@SGaist There is no problem when remote folder copied to local. But, mounted (cifs or nfs) folder occurs problems, such as;
- no moc generated
- Info: creating stash file /mnt/ChRSM/ChRSM/.qmake.stash
/usr/lib/qt/mkspecs/features/toolchain.prf:407: Cannot write cache file /mnt/ChRSM/ChRSM/.qmake.stash: Cannot create parent directory
Info: creating cache file /mnt/ChRSM/ChRSM/.qmake.cache
/mnt/ChRSM/ChRSM/ChRSM.pro:5: Cannot write cache file /mnt/ChRSM/ChRSM/.qmake.cache: Cannot create parent directory
-
@VeNToR said in qmake & mocing problem:
But, mounted (cifs or nfs) folder occurs problems
So why do you think Qt can do something against this? Looks like your mount options are wrong so e.g. the timestamps of the generated files are wrong and /or the permissions do not match.
Don't build on an external volume - it will greatly slow down your build times due to the network in between. -
@VeNToR said in qmake & mocing problem:
But, mounted (cifs or nfs) folder occurs problems
So why do you think Qt can do something against this? Looks like your mount options are wrong so e.g. the timestamps of the generated files are wrong and /or the permissions do not match.
Don't build on an external volume - it will greatly slow down your build times due to the network in between.@Christian-Ehrlicher It seems, problem begins from last update of Qt. Mounted volume is storage, and contains lots of sources etc., so I have to copy everything to Mac, Rasp, Linux machines to compile... I am using VS for debug etc. when I change anything in codes then just compile on the each system that's ok ?
-
@VeNToR said in qmake & mocing problem:
It seems, problem begins from last update of Q
moc did not change and such problems are well known on filesystems which have a wrong timestamp / don't handle timestamps correctly.
-
@VeNToR said in qmake & mocing problem:
It seems, problem begins from last update of Q
moc did not change and such problems are well known on filesystems which have a wrong timestamp / don't handle timestamps correctly.
@Christian-Ehrlicher I solved the problem with workaround that using rsync the folders... I gonna lookup later cause'f project waits...
