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.

Sign up for GitHub

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

Jump to bottom

Allow configuring enabled architectures in the environment #357

Closed
advayDev1 opened this issue Aug 18, 2015 · 0 comments
Closed

Allow configuring enabled architectures in the environment #357

advayDev1 opened this issue Aug 18, 2015 · 0 comments
Assignees
@advayDev1
Labels
type:enhancement
Milestone
0.5 Release

Comments

@advayDev1
Copy link
Contributor

Similar to configuring debug, release, and translateOnly on a per-environment basis for developer convenience, permit enabling architectures in the environment via local.properties.

This is separate and in addition to setting the /supported/ architectures in the build file itself. The final architectures built are the intersection of the supported architectures and the per-environment enabled ones (if any).
@advayDev1 advayDev1 self-assigned this Aug 18, 2015
@advayDev1 advayDev1 added this to the 0.5 Release milestone Aug 18, 2015
advayDev1 added a commit to madvay/j2objc-gradle that referenced this issue Aug 18, 2015
@advayDev1
Enabled architectures, fixes j2objc-contrib#357
ba3d364 
Similar to configuring debug, release, and translateOnly on a per-environment basis for developer convenience, permit enabling architectures in the environment via local.properties.

This is separate and in addition to setting the /supported/ architectures in the build file itself. The final architectures built are the intersection of the supported architectures and the per-environment enabled ones (if any).
advayDev1 added a commit to madvay/j2objc-gradle that referenced this issue Aug 18, 2015
@advayDev1
Enabled architectures, fixes j2objc-contrib#357
8eb7da5 
Similar to configuring debug, release, and translateOnly on a per-environment basis for developer convenience, permit enabling architectures in the environment via local.properties.

This is separate and in addition to setting the /supported/ architectures in the build file itself. The final architectures built are the intersection of the supported architectures and the per-environment enabled ones (if any).
advayDev1 added a commit that referenced this issue Aug 20, 2015
@advayDev1
Merge pull request #358 from madvay/enabledArchs
7ef3450 
Enabled architectures, fixes #357
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@advayDev1 advayDev1

Labels
type:enhancement
Projects
None yet
Milestone
0.5 Release
Development

No branches or pull requests
1 participant
@advayDev1