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

iOS/ARM support #9

Open
beltex opened this issue Nov 2, 2014 · 4 comments
Open

iOS/ARM support #9

beltex opened this issue Nov 2, 2014 · 4 comments
Labels
enhancement

Comments

@beltex
Copy link
Owner

beltex commented Nov 2, 2014

  • Everything should be the same for the most part (32-bit devices are many though - vm stats)
  • Need cert to test
@beltex beltex mentioned this issue Nov 3, 2014
Closed
@beltex
Copy link
Owner Author

beltex commented Nov 5, 2014

I/O Kit is a private framework on iOS, so current Battery class won't work. Need to use UIDevice class instead.

@beltex
Copy link
Owner Author

beltex commented Dec 3, 2014

  • Not for initial release

@beltex beltex changed the title iOS support iOS/ARM support Dec 6, 2014
@beltex
Copy link
Owner Author

beltex commented Dec 6, 2014

This also implies ARM support

@beltex
Copy link
Owner Author

beltex commented Jan 1, 2015

Examples from Apple split platform specific code into different subdirs. What about the use of macros instead?

beltex added a commit that referenced this issue Feb 7, 2015
@beltex
Add System.CPUPowerLimit()
b1e266c 
- As seen via 'pmset -g therm'
- In terms of placement, arguably this should be moved to a separate Power
  struct of its own. Not only because there are a number of power related
  functions that could be added, but also because this relies on I/O Kit which
  is private on iOS. So when it comes time to work on #9, it could add a bit
  of hassle as it be harder to separate things, since currently, System.swift
  should work fine on iOS. Work around is using a macro.
@beltex beltex mentioned this issue Oct 10, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@beltex