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

Missing Target SDK #1

Open
leviwilson opened this issue Sep 17, 2012 · 5 comments
Open

Missing Target SDK #1

leviwilson opened this issue Sep 17, 2012 · 5 comments
Labels

Comments

@leviwilson
Copy link
Contributor

Description

When missing a value for the target SDK, brazenhead is unable to start the application.

Proposed Behavior

brazenhead should decide upon a default order. I would say target -> min -> max and if we still have not resolved this, default to 1.

@mlemley
Copy link

mlemley commented May 2, 2013

how about looking at the project.properties since this file is created both by the "android" command and the process that eclipse provides when generating the project.

there is a line item that will tell you what that value is. The "uses-sdk" field in the manifest is optional and only is auto generated by the eclipse project creation flow.

//Project target.
target=android-17

Not trying to tell you how to pluck your chicken.. Food for thought :)

Take care Brother

@leviwilson
Copy link
Contributor Author

Brazenhead is limited to only working with the apk and an optional keystore information. If the info ends up in the apk manifest, we can use it. I will check this out to see what gets packed in there if you don't provide one.

@mlemley
Copy link

mlemley commented May 3, 2013

Good point :-D
On May 2, 2013 8:48 PM, "Levi Wilson" notifications@github.com wrote:

Brazenhead is limited to only working with the apk and an optional
keystore information. If the info ends up in the apk manifest, we can use
it. I will check this out to see what gets packed in there if you don't
provide one.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-17373640
.

@leviwilson
Copy link
Contributor Author

I also don't even know if this is really an issue. The only reason it needs it is to update the brazenhead apk with the newly written manifest. When you update an apk with aapt, you have to provide an android.jar to link against. I imagine that using the first one you come across would work as well?

@mlemley
Copy link

mlemley commented May 3, 2013

I think a clear error message saying why there is a failure would be
perfect. I was frustrated the first time because I had no idea what the
problem was until I looked at the implementation
On May 2, 2013 11:36 PM, "Levi Wilson" notifications@github.com wrote:

I also don't even know if this is really an issue. The only reason it
needs it is to update the brazenhead apk with the newly written manifesthttps://github.com/leandog/brazenhead/blob/master/lib/brazenhead/package.rb#L23.
When you update an apk with aapt, you have to provide an android.jar to
link against. I imagine that using the first one you come across would work
as well?


Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-17377232
.

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

No branches or pull requests

2 participants