On May 11, 2010, at 12:38 PM, André Fillipe wrote: On Tue, May 11, 2010 at 1:45 PM, Ed Sutton <[email protected]<mailto:[email protected]>> wrote:
I am not sure I understand. I am trying to make the Qt Creator project run settings paths relative (no hard-coded absolute paths ). I want any Red Hat Enterprise Linux developer to be able to extract a project tarball to his home directory, open the Qt project file and be able to build, run, and debug from within Qt Creator without having to modify any Qt Creator project setings. The problem is the Qt project "Working Directory" "Run Setting" seems to only accept hard-coded absolute paths. Are you including the ".pro.user" files in the tarball? If you are, you shouldn't. Yes, I am. I have also included the ".pro.user" files in version control. Is the preferred alternative to not rely on Qt Creator project settings at all? Basically everything should be persisted in the "*.pro" file? Obviously if I delete the ".pro.user" file I lose all Qt Project settings; custom build steps, build environment, run settings, and run environment settings. I had added an environment variable required by a 3rd-party library to the run settings environment. The "pro.user" persisted this and without this file a user cannot simply extract, open a project in Qt Creator, build, and run. I will need to think about alternatives. Coming from Windows Visual Studio 2008 I saw Qt Creator as a viable replacement tool (or maybe a crutch) in my new Linux world. I viewed the Qt *.pro files as the equivalent to Visual Studio's project *.sln solution file and *.csproj project file which I typically versioned control as well. Thank you both for sharing your experience and time. -Ed _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
