You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When building a .sln with v3.3.1 which hasn't been modified and worked fine with v3.2.0, I get the following error:
C:\Users\...\AppData\Local\QtMsBuild\qt_vars.targets(521,5): error MSB4044: The "ReadLinesFromFile" task was not given a value for the required parameter "File".
It's possible that it worked with v3.3.0, too, as the last successful build was after that version was tagged, but I don't know if there was an automatic update installed between it being tagged and that build.
To Reproduce
Steps to reproduce the behavior:
Currently unknown - the specific project's under NDA, so I can't provide it, and I'm about to finish work for the day, so want this posted in case anyone who knows something figures it out overnight. I'll try and come up with something tomorrow.
Expected behavior
This error doesn't happen, and the build succeeds.
Screenshots
Desktop (please complete the following information):
Qt VS Tool Version 3.3.1
Visual Studio version: VS2022
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
I think I've isolated the cause. It's a <Keyword>Qt4VSv1.0</Keyword> project, so doesn't set QtVsProjectSettings. The part of qt_vars.targets that sets QtVarsFilePath has Condition="'$(QtVsProjectSettings)' == 'true'", so it's left unset, and so <ReadLinesFromFile File="$(QtVarsFilePath)"> in the QtVarsRead target has its File set to an empty string.
That line was added by 1ef7c52, and before that, it looks like the file was imported, directly, and that was gated behind an Exists('$(QtVarsFilePath)') check. I've tested, and Exists returns false when it's passed an empty string.
Based on that, I tried just gating the QtVarsRead target off so it doesn't do anything when QtVsProjectSettings is unset, but haven't yet managed to get that working.
I managed to reproduce the error by modifying the QtProjectV200.vcxproj from this repo's Tests/ProjectFormats directory. When I compared the unmodified file to the one from the project that died, a difference that stuck out to me was that the dead project had
at the end. Adding that block to this repo's test gave the same error. Lots of the other templates and tests in this repo have the same ImportGroup, so I guess this is something that's supposed to work.
I've done enough to confirm this is a regression, identify what caused it and how to reproduce it to satisfy myself, so I'm going to downgrade to an older version so I can move on with my work now.
Describe the bug
When building a
.sln
with v3.3.1 which hasn't been modified and worked fine with v3.2.0, I get the following error:It's possible that it worked with v3.3.0, too, as the last successful build was after that version was tagged, but I don't know if there was an automatic update installed between it being tagged and that build.
To Reproduce
Steps to reproduce the behavior:
Currently unknown - the specific project's under NDA, so I can't provide it, and I'm about to finish work for the day, so want this posted in case anyone who knows something figures it out overnight. I'll try and come up with something tomorrow.
Expected behavior
This error doesn't happen, and the build succeeds.
Screenshots
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: