AuroraMiddleware/qt5base-lts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

MOC: Avoiding MAX_PATH limit on Windows

Browse Source 
See: http://msdn.microsoft.com/en-us/library/aa365247(v=VS.85).aspx
Task-number: QTBUG-26157

Change-Id: Ie74481cd06c31149a060a432352da5b2731caaef
Reviewed-by: Debao Zhang <dbzhang800@gmail.com>
Reviewed-by: Joerg Bornemann <joerg.bornemann@nokia.com>
This commit is contained in:
Yuchen Deng 2012-06-14 20:27:02 +08:00 committed by Qt by Nokia
parent 8b92d770a0
commit 3db8877d28
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/tools/moc/main.cpp
View File

@ -67,7 +67,15 @@ static QByteArray combinePath(const QByteArray &infile, const QByteArray &outfil
{
QFileInfo inFileInfo(QDir::current(), QFile::decodeName(infile));
QFileInfo outFileInfo(QDir::current(), QFile::decodeName(outfile));
return QFile::encodeName(outFileInfo.dir().relativeFilePath(inFileInfo.filePath()));
const QByteArray relativePath = QFile::encodeName(outFileInfo.dir().relativeFilePath(inFileInfo.filePath()));
#ifdef Q_OS_WIN
// It's a system limitation.
// It depends on the Win API function which is used by the program to open files.
// cl apparently uses the functions that have the MAX_PATH limitation.
if (outFileInfo.dir().absolutePath().length() + relativePath.length() + 1 >= 260)
return QFile::encodeName(inFileInfo.absoluteFilePath());
#endif
return relativePath;
}