Winford
Winford
Just to be clear before I start working on this issue, should this only apply to the generic_unix platform?
This issue is probably being caused by issue #272. The Elixir beams are not being packed into atomvmlib.avm like they should be.
Not a good sign that all activity on this repo stopped in Jan 2018... some of these pull requests have been here for two years... dimich-dmb your repo is by...
The error is because the header you supplied had the needed definition, but that is not the header compiled into the kernel so the kernel had no idea what to...
Sorry to hear you are experiencing problems... It looks like you are the victim of a rare bug we are trying to track down. We still are not certain why...
Glad to here that the workaround took care of the build problem! Since you found us in the [Telegram AtomVM Chat](https://t.me/atomvm) we can sort out your next issue with you...
This is still an problem and is related to Issue #377.
The atomvm_adc driver should work with esp-idf 4.x versions, but currently will not compile using esp-idf 5.x versions. The APIs completely changed and support for IDF 5.x is taking longer...
Since we can't merge the atomvm_adc component into AtomVM until it is updated to compile with ESP-IDF 5.x versions, would you mind opening an issue in the atomvm_adc repo so...
No, the only components that the ADC driver uses are included in the esp-idf. They only thing preventing moving atomvm_adc to AtomVM core is that it currently doesn't build with...