-
Notifications
You must be signed in to change notification settings - Fork 20
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
Compatibility with esp32-idf 4.0+ #6
Comments
Hello, I commited a change that allows to compile with latest version of esp-idf. It should probably work for esp32-idf-4.0 as well |
Hi, tried to compile with idf 4.0 and it throw errors. Did you test to compile with idf 4, with idf.py build? |
@Ebiroll it doesn't compile, fails with:
If you fix that, it would fail with:
|
I'd make a PR with the changes I've made, but I technically cannot as your project doesn't have a license, so technically it is not open-source. |
OK. I have commited some changes. Hopefully it will compile now. |
You must enable sump in main/app-config.h |
@Ebiroll about the License - I'm not a lawyer, but here's my opinion: TLDR; But overall I would suggest to choose between BSD, MIT, Apache2, GPLv2, GPLv3, LGPLv2 and LGPLv3. If you've used code that's distributed under any GPL license you basically have no choice other than to adopt GPL for the whole project, but otherwise you can mostly freely choose. Rather good comparison/wizard is: https://choosealicense.com/ (github's resource to my knowledge). Otherwise your code falls into https://choosealicense.com/no-permission/#for-users which is tricky for people to use/contribute. Long version: Good examples are GPLv2/v3, LGPLv2/v3, Apache2, etc. It also depends on what you want. Different licenses have different requirements, for example famously GPL overrides all other licenses to become GPL (you still can use libraries or parts of the code licensed under BSD/MIT and other compatible licenses). BSD/MIT/Apache are more permissive (basically they allows other people to use your work as part of their closed source project, with small restrictions, like they need to put that statement somewhere that this is the code they use and depends on version it also covers the name of your application and other stuff). There is another class of licenses which are tricky to actually use - those are WTFPL-like licenses. Their problem is that depends on a country they might be considered not a valid license (WTFPL even the updated version is not considered a valid license in US and some other countries, some other countries could not recognise CC0 license, etc). And the last one is even more strict than GPL, which is AGPLv3. With GPL there is a "problem" that you can use GPL code in a backend of your application and sell your work as SaaS without providing source code of your backend. AGPLv3 fixes that problem. The problem is that for such licenses some external people have restrictions in what they can contribute to. E.x. I cannot contribute to projects under AGPLv3 even in my free time without getting approval for specific project. And that's true not only for me, but that's rather common restriction imposed by US-based IT Companies. Oh, and another thing, most licenses limits liability and warranty, which is something that you might want as well (to not be responsible for your application's behavior or damages caused by it). |
I tried now with 115200, and sump(SUMP_OVER_UART) is enabled/defined in app-config.h Bootlog looks like this I (106) cpu_start: Pro cpu up. I (0) cpu_start: App cpu up. |
esp32-idf-4.0 removed some of deprecated functions:
esp_adc_cal_get_characteristics
was removed in favor toesp_adc_cal_characterize
(parameters are in different order, but otherwise the same)i2s_write_bytes
was removed (could be safely copypasted from pre-4.0 sources as it's basically wrapper aroundi2s_write
with extra checking)bit_num
instruct ledc_timer_config_t
was renamed toduty_resolution
components/tft/tftspi.c
must explicitly includedrivers/gpio.h
I'm not sure that after those fixes it works properly though...
The text was updated successfully, but these errors were encountered: