Don't support moving files to trash on VxWorks
On VxWorks 24.03, the `AT_FDCWD` wasn't defined, which happened to branch to the correct branch. VxWorsk 24.09 TP does define the `AT_FDCWD`, which causes the preprocessor directives to branch to a branch where moving files to trash would be supported. In a sidenote, VxWorks doesn't define `renameat`, `O_DIRECTORY` nor `O_NOFOLLOW`. Task-number: QTBUG-130629 Change-Id: I2b850813aeff6f925ab91932efd7aeb13f753f69 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> (cherry picked from commit 039b0c6b9b94eb7601fa3b652e8b668d32251f7e)
This commit is contained in:
parent
6ade020b22
commit
c81e250f85
@ -1189,7 +1189,7 @@ bool QFileSystemEngine::createLink(const QFileSystemEntry &source, const QFileSy
|
||||
|
||||
#ifdef Q_OS_DARWIN
|
||||
// see qfilesystemengine_mac.mm
|
||||
#elif defined(QT_BOOTSTRAPPED) || !defined(AT_FDCWD) || defined(Q_OS_ANDROID)
|
||||
#elif defined(QT_BOOTSTRAPPED) || !defined(AT_FDCWD) || defined(Q_OS_ANDROID) || defined(Q_OS_VXWORKS)
|
||||
// bootstrapped tools don't need this, and we don't want QStorageInfo
|
||||
//static
|
||||
bool QFileSystemEngine::moveFileToTrash(const QFileSystemEntry &, QFileSystemEntry &,
|
||||
|
Loading…
x
Reference in New Issue
Block a user