Defaulting to device might be problematic on iOS: sure we can detect if a device is attached (using iso-deploy), but the build might fail because a signing cert/provisioning profile is not valid (I think the only way to check is to just build, I might be wrong).
The only "guaranteed" way it will always run is through emulator (at least on iOS). On Tue, Mar 3, 2015 at 2:50 PM, Michal Mocny <mmo...@chromium.org> wrote: > Imho, it should do what: "cordova run" would do. > > I would think it would run once for each platform, defaulting to device if > attached. > > On Tue, Mar 3, 2015 at 4:37 PM, Shazron <shaz...@gmail.com> wrote: > >> What is the expected behaviour here? >> `cordova build` >> >> My expectation is that it would build for both device and emulator. In >> iOS pre-3.8.0 it does, but now it only builds for emulator only after >> the node.js script port, which may or may not be a bug depending on >> consensus. >> >> The online docs and cli docs do not give any clue regarding this. >> >> What do other platforms experience? >> >> The problem with building for both device and emulator is your build >> times now approximately double. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >> For additional commands, e-mail: dev-h...@cordova.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
