| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Convert custom build command strings with multiple lines2.1 | Miguel Costa | 2017-12-12 | 1 | -6/+21 |
| | | | | | | | | | | | | | | When converting custom build steps to Qt/MSBuild target items, the conversion procedure will now be able to handle command strings with multiple lines. In these cases, only the sub-string with the relevant command will be considered. Custom build steps with multiple lines are potentially problematic, e.g. if empty lines are present in the command string (see associated issue for example of this problem). Task-number: QTVSADDINBUG-414 Change-Id: I93ae2f233ee35d27462b9087ada58b1134102e87 Reviewed-by: Oliver Wolff <oliver.wolff@qt.io> | ||||
| * | Replace custom build steps with MSBuild targets | Miguel Costa | 2017-12-01 | 1 | -0/+540 |
| Overhaul of Qt tool (moc, rcc, uic) usage in generated projects. Running the Qt tools on project files no longer relies on custom build steps but rather on Qt-specific MSBuild targets that are installed together with the VS Tools. Older projects generated with previous versions of the VS Tools can be converted to use the MSBuild targets Conversion is not mandatory as custom build steps are still supported. Change-Id: I4c01491b2c263deb2cdf2c5fcc12ecdf718eb11f Reviewed-by: Oliver Wolff <oliver.wolff@qt.io> | |||||
 |
index : qt-labs/vstools.git | |
| Qt Visual Studio Add-in – https://wiki.qt.io/QtVSAddin |
| aboutsummaryrefslogtreecommitdiffstats |