On Thu, Sep 29, 2011 at 8:16 AM, <[email protected]> wrote: > You can't tell Qt Creator directly to use a different .user file. It is > always called yourproject.pro.user. As already said, you can't share the > .user file. So I see two options for you: > > 1) Use dropbox to mount your mercurial repository. Don't work on it > directly, but check the repository from dropbox out locally on Mac and > Windows separately. After all, you are using a distributed source control, > so use it :) . That way you share the sources, but actually work on > different copies, and as long as you don't check the .user into source > control you are fine. >
This would be a bit easier if the mercurial commit interface within QT Creator worked. By some chance was that one of the bugs resolved in 2.3.1? > ...the .user files *can not be shared between different computers*, even > not between computers with the same OS... > That answers the question I asked on the other thread, and thank you. Also, given what you say, permit me to say "conratulations" on how successful Qt Creator seems to be about acting defensively. I have been cross-loading this file "successfully", in the sense that Qt Creator seems to do enough validation to avoid messing itself up. It takes rare discipline to implement that level of checking consistently. My compliments to the programmers. Now given that the .user file does *not* go under change control, is there possibly something we can do in the QMakefile so that Qt Creator will be able to reconstruct the correct build targets and rules when it is re-generating this file? Or if not in the QMakefile, perhaps someplace else? Thanks
_______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
