> On Sep 24, 2015, at 12:50 PM, René J. V. Bertin <rjvber...@gmail.com> wrote: > > Ziller Eike wrote: > >>> QFileSystemWatcher: skipping native engine, using only polling engine >> >> This warning probably appears because the above file path (to the diff) is >> (in >> a directory that somewhere is) a symbolic link, and is harmless if that is >> the >> case. > > Now verified: the warning indeed doesn't occur for files that are not > symlinked > one way or another. > As to harmless: I presume that there is a CPU overhead penalty to this > fallback? > So what happens if a whole set of *directories* are added that are all under > a > common parent directory that has a symlink somewhere in its path, as can > happen > when opening a project? Is falling back to the polling engine still better > than > using, say, the kqueue engine (presuming 1) that one isn't always better and > 2) > it will accept paths with a symlink in them)? > > Alternatively, why not simply resolve the symlink and use the normalised path > with the native engine?
We do resolve the symlink and watch that, but we need to track changes to the symlink itself as well. -- Eike Ziller, Senior Software Engineer - The Qt Company GmbH The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
