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

Fix issues that stopped ESP32 build after change to events #611

Merged
merged 1 commit into from
Feb 13, 2018
Merged

Fix issues that stopped ESP32 build after change to events #611

merged 1 commit into from
Feb 13, 2018

Conversation

AdrianSoundy
Copy link
Member

@AdrianSoundy AdrianSoundy commented Feb 13, 2018

Description

Commented out CPU_Sleep from nanoHALV2.h for now as compile giving error that uint64_t is not defined. Can't find out why for moment. But doesn't seem to need it as also defined in TargetHal_power.h. Both arm and esp32 builds ok without it.

Types of changes

  • Improvement (non-breaking change that improves a feature, code or algorithm)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Signed-off-by: adriansoundyadriansoundy@gmail.com

Commented out CPU_Sleep from nanoHALV2.h for now as compile giving error that uint64_t is not defined. Can't find out why for moment.  But doesn't seem to need it as also defined in TargetHal_power.h.  Both arm and esp32 build ok without it.
@nfbot
Copy link
Member

nfbot commented Feb 13, 2018

Hi @AdrianSoundy,

I'm nanoFramework bot.
Thank you for your contribution!

A human will be reviewing it shortly. 😉

@josesimoes josesimoes merged commit 1aad6fc into nanoframework:develop Feb 13, 2018
@josesimoes
Copy link
Member

It's curious that the Appveyor build didn't complain about these... Needs further investigation.

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

Successfully merging this pull request may close these issues.

3 participants