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
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 <sdk-version> 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"
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
Actual result
A new build command will be forked and the build will take place for emulator
Expected result
The build target specified should be carried through
I'm not sure this is actually a windows CLI issue so much as a general CLI issue where it's not retaining all the arguments when "forking" to the right SDK.
[~cwilliams] I've looked into this further and have found that it only occurs when 4.0.0.GA is selected as the SDK, if I select a 4.1.0 SDK I can't reproduce. I'm happy to close this as invalid/wont fix as Windows wasn't supported in 4.0.0.GA so I'm not sure what the behavior should be there.
May be, we should show a nice message if SDK doesn't support Windows platform.
Closing, as Windows platform is not supported in the 4.0.0.GA.
Closing ticket as Won't Fix with reference to the above comments.