Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Corrections to the 'TryToFindVsSdk2017' build target. Also, make it possible to use the target without needing the 'SQLiteNetDir' MSBuild property. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | vs2017 |
| Files: | files | file ages | folders |
| SHA1: |
628098f876e853872562aaa835216cc7 |
| User & Date: | mistachkin 2017-08-02 20:53:43 |
Context
|
2017-08-02
| ||
| 21:19 | Rename 'TryToFindVsSdk2017' MSBuild target to 'MaybeFindVsSdk2017'. Add 'MaybeMissingVsSdk2017' MSBuild target. Call both of them from the 'InitialTargets' property so they can actually override the build processing, if necessary. check-in: e1d9903754 user: mistachkin tags: vs2017 | |
| 20:53 | Corrections to the 'TryToFindVsSdk2017' build target. Also, make it possible to use the target without needing the 'SQLiteNetDir' MSBuild property. check-in: 628098f876 user: mistachkin tags: vs2017 | |
| 20:06 | Fix a typo. check-in: 6a136b170d user: mistachkin tags: vs2017 | |
Changes
Changes to Targets/SQLite.NET.targets.
261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 |
<!--
******************************************************************************
-->
<Target Name="TryToFindVsSdk2017"
Condition="'$(TryToFindVsSdk2017)' != 'false' And
'$(SQLiteNetDir)' != '' And
!HasTrailingSlash('$(SQLiteNetDir)') And
Exists('$(SQLiteNetDir)\Externals\vswhere\vswhere.exe')">
<!--
HACK: Use a couple undocumented properties of the Exec task in order
to capture the console output of the "vswhere" command. This
is needed to locate the SDK for Visual Studio 2017. For more
information, see:
https://stackoverflow.com/questions/8938679
-->
<Exec ConsoleToMSBuild="true" Command=""$(SQLiteNetDir)\Externals\vswhere\vswhere.exe" -version 15.0 -products * -requires Microsoft.VisualStudio.Component.VSSDK -property installationPath"
WorkingDirectory="$(EagleLibraryToolsDir)">
<Output TaskParameter="ConsoleOutput" PropertyName="VS150INSTALLATIONPATH" />
</Exec>
<CreateProperty Condition="'$(VS150INSTALLATIONPATH)' != '' And
!HasTrailingSlash('$(VS150INSTALLATIONPATH)') And
Exists('$(VS150INSTALLATIONPATH)\VSSDK')"
Value="$(VS150INSTALLATIONPATH)\VSSDK">
<Output TaskParameter="Value" PropertyName="VSSDK150Install" />
</CreateProperty>
</Target>
</Project>
|
| | | | | | |
261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 |
<!--
******************************************************************************
-->
<Target Name="TryToFindVsSdk2017"
Condition="'$(TryToFindVsSdk2017)' != 'false' And
'$(MSBuildProjectDirectory)' != '' And
!HasTrailingSlash('$(MSBuildProjectDirectory)') And
Exists('$(MSBuildProjectDirectory)\..\Externals\vswhere\vswhere.exe')">
<!--
HACK: Use a couple undocumented properties of the Exec task in order
to capture the console output of the "vswhere" command. This
is needed to locate the SDK for Visual Studio 2017. For more
information, see:
https://stackoverflow.com/questions/8938679
-->
<Exec ConsoleToMSBuild="true" Command=""$(MSBuildProjectDirectory)\..\Externals\vswhere\vswhere.exe" -version 15.0 -products * -requires Microsoft.VisualStudio.Component.VSSDK -property installationPath"
WorkingDirectory="$(MSBuildProjectDirectory)\..\Externals\vswhere">
<Output TaskParameter="ConsoleOutput" PropertyName="VS150INSTALLATIONPATH" />
</Exec>
<CreateProperty Condition="'$(VS150INSTALLATIONPATH)' != '' And
!HasTrailingSlash('$(VS150INSTALLATIONPATH)') And
Exists('$(VS150INSTALLATIONPATH)\VSSDK')"
Value="$(VS150INSTALLATIONPATH)\VSSDK\">
<Output TaskParameter="Value" PropertyName="VSSDK150Install" />
</CreateProperty>
</Target>
</Project>
|