On 03/12/2010 07:24 PM, ext Bryce Schober wrote: > Actually, I've been debugging it myself, and not knowing the code > better, it seems pretty deeply rooted. The implementation of > Qt4BuildConfiguration::buildDirectory() does the same. The > implementation of CMakeBuildConfiguration::buildDirectory() looks > different, but is effectively the same, since > cmakeTarget()->cmakeProject()->sourceDirectory() also returns an abs-path. > > I think a more ideal and generic solution would be to allow for relative > paths anchored on the project file. That could actually help satisfy > many of the complaints in this thread, I would think. This would > probably require a distinction between the user-entered build dir, with > possible relative paths, and the build dir used by project-building > functionality, which apparently is most happy with abs-paths for > everything. If a new interface (maybe userBuildDirectory() was used for > re-initing the project fields (GenericBuildSettingsWidget::init), but > everything else used the existing buildDirectory() interface, that seems > like it would work fine. How this would map to the other projectmanager > implementations is beyond me.
Fortunately, there doesn't seem to be a need for a generic solution here, since the pro.user file contains more information that makes it unsuitable anyway for sharing it with other users. For the Generic Project, it seems to make sense to fix this, since there is indeed no reason the path should be stored as absolute. Hence I made a small workaround to avoid changing the build path to absolute in change c0b42868b02317e58acb89d28695ba016301f58e. Regards, Bjørn -- Thorbjørn Lindeijer Software Engineer Nokia, Qt Development Frameworks _______________________________________________ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
