.pro.user and version control
-
Hi
I am using git as my version control tool.
I have setup shadow builds for my project and set the folders for these builds asD:\QtBuilds\%{CurrentProject:Name}\%{CurrentKit:FileSystemName}-%{CurrentBuild:Name}Now I believe that this is stored in the .pro.user file and no where else.
So if I add .pro.user to git, every time that I quit Creator this file is updated and needs to be checked into git or reverted.
Is there a way of setting up shadow builds such that they dont get stored in the .pro.user?
Thanks -
Hi
I am using git as my version control tool.
I have setup shadow builds for my project and set the folders for these builds asD:\QtBuilds\%{CurrentProject:Name}\%{CurrentKit:FileSystemName}-%{CurrentBuild:Name}Now I believe that this is stored in the .pro.user file and no where else.
So if I add .pro.user to git, every time that I quit Creator this file is updated and needs to be checked into git or reverted.
Is there a way of setting up shadow builds such that they dont get stored in the .pro.user?
Thanks@GrahamLa said in .pro.user and version control:
Is there a way of setting up shadow builds such that they dont get stored in the .pro.user?
Currently no, sadly.
That said: Don't check in the *.pro.user into version control! It will break anytime you upgrade Qt, Creator or check out on a different machine.
To achive what you want, it would be the easiest to set up the default build directory in Tools > Options > Build & Run > General.
PS: The default also uses a function to remove special chars from the build directory name to avoid problems:
%{JS: Util.asciify("build-%{CurrentProject:Name}-%{CurrentKit:FileSystemName}-%{CurrentBuild:Name}")} -
@GrahamLa said in .pro.user and version control:
Is there a way of setting up shadow builds such that they dont get stored in the .pro.user?
Currently no, sadly.
That said: Don't check in the *.pro.user into version control! It will break anytime you upgrade Qt, Creator or check out on a different machine.
To achive what you want, it would be the easiest to set up the default build directory in Tools > Options > Build & Run > General.
PS: The default also uses a function to remove special chars from the build directory name to avoid problems:
%{JS: Util.asciify("build-%{CurrentProject:Name}-%{CurrentKit:FileSystemName}-%{CurrentBuild:Name}")} -
@GrahamLa said in .pro.user and version control:
Is there a way of setting up shadow builds such that they dont get stored in the .pro.user?
Currently no, sadly.
That said: Don't check in the *.pro.user into version control! It will break anytime you upgrade Qt, Creator or check out on a different machine.
To achive what you want, it would be the easiest to set up the default build directory in Tools > Options > Build & Run > General.
PS: The default also uses a function to remove special chars from the build directory name to avoid problems:
%{JS: Util.asciify("build-%{CurrentProject:Name}-%{CurrentKit:FileSystemName}-%{CurrentBuild:Name}")} -
@aha_1980
Hi
I have set the default build directory but the output does not go to the specified folder - it now goes to debug/release in the the project folder -
@GrahamLa said in .pro.user and version control:
@aha_1980
It seems that the default build path is only set on project creationYes, that's how it works.
-
@GrahamLa said in .pro.user and version control:
@aha_1980
It seems that the default build path is only set on project creationYes, that's how it works.
