Project: titanium
Issue TIMOB-19106: Windows: Build target is not respected when forking a new build command due to mismatched SDKs
h5.Description When building for Windows if there are mismatched SDKs, the tiapp.xml is set to a different SDK than the selected SDK in the CLI, then the build target is not respected and the build will always be to wp-emulator {code} C:\Users\Windo_000\Documents\Appcelerator_Studio_Workspace\pkgTest>appc run -p windows -T wp-device Appcelerator Command-Line Interface, version 4.1.0-4 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. [INFO] tiapp.xml set to 4.1.0.v20150629125430, but current Titanium SDK set to 4.0.0.GA [INFO] Forking correct SDK command: "C:\Program Files (x86)\nodejs\node.exe" "C:\Users\Windo_000\.appcelerator\install\4.1.0-4\package\node_modules\a ppc-cli-titanium\node_modules\titanium\bin\titanium" "build" "--sdk" "4.1.0.v20150629125430" "--no-banner" "--config-file" "C:\Users\WINDO_~1\AppData\ Local\Temp\build-1435614283393.json" "--platform" "windows" "--project-dir" "." "--log-level" "info" {code} h5.Steps to reproduce 1. Set your selected SDK to a different SDK than in the tiapp using {{appc ti sdk select 4.0.0.GA}} 2. Build using {{appc run -p windows -T wp-device}} h5.Actual result A new build command will be forked and the build will take place for emulator h5.Expected result The build target specified should be carried through
Story points: 3