Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build Needs Device Running Issue #16

Open
bubblewaretech opened this issue Feb 7, 2012 · 4 comments
Open

Build Needs Device Running Issue #16

bubblewaretech opened this issue Feb 7, 2012 · 4 comments

Comments

@bubblewaretech
Copy link

The build currently needs the device to be running or an associated emulator window for android builds. I would like to decouple this so we can build quicker and avoid any emulator issues that are not related to building the app.

Here is a log that illustrates this point:

make run platform=android
Building with Titanium... as
PROJECT_ROOT='/usr/local/hudson/hudson-home/jobs/RabbleApp/workspace' DEVICE_TYPE=android bash '/usr/local/hudson/hudson-home
[DEBUG] Titanium not found... Testing another directory
[DEBUG] Titanium found...
[DEBUG] Titanium SDK 1.8.0.1.v20120116174635 found...
[ERROR] Could not find a running emulator.
[ERROR] Run this command in a separate terminal session: ~/Android/tools/emulator-arm -avd 10

@mattapperson
Copy link
Contributor

I am on the road right now... as soon as I return home (friday) I will take a look at it :)

@Sophrinix
Copy link

can we get an update on this, please? Is this still an ongoing issue. I really want to roll MakeTi in to the Appcelerator Classes ( I am a TCE) and I have a class starting up in the last week of May in Tennessee.

Also, on a side note, in that error log, you really should use emulator-x86. It is a lot faster, unless you are needing to support older builds of android.

@mattapperson
Copy link
Contributor

So you asking for the emulator to auto start when not running?

@Sophrinix
Copy link

That is how I am reading the issue. I haven't confirmed or denied this issue yet. I am just checking on if this is still an ongoing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants