arduino-esp32/.gitignore

tools/xtensa-esp32-elf
tools/dist
tools/esptool
tools/esptool.exe
tools/mkspiffs/mkspiffs
tools/mkspiffs/mkspiffs.exe
.DS_Store
 
#Ignore files built by Visual Studio/Visual Micro
[Dd]ebug*/
[Rr]elease*/
.vs/
__vm/
*.vcxproj*
.vscode/
initial import 2016-10-06 13:21:30 +02:00			`tools/xtensa-esp32-elf`
ignore dist folder 2016-10-06 13:24:44 +02:00			`tools/dist`
move to binary esptool. Run get.py/get.exe to get it! With this step we remove all dependencies, but git. Mac and Linux come with Python by default, so they will keep using get.py to update the toolchain and support binaries. Windows users have an "All point and click" installation option that requires only git and Arduino to be downloaded. Fingers crossed :) 2017-01-19 14:58:29 +01:00			`tools/esptool`
			`tools/esptool.exe`
Add mkspiffs 2017-10-13 21:20:35 +02:00			`tools/mkspiffs/mkspiffs`
			`tools/mkspiffs/mkspiffs.exe`
Convert the few remaining cr/lf files to use lf for eol. (#1316) If you develop on windows and need cr/lf files, see this: https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration#_formatting_and_whitespace Git can handle this by auto-converting CRLF line endings into LF when you add a file to the index, and vice versa when it checks out code onto your filesystem. You can turn on this functionality with the core.autocrlf setting. If you're on a Windows machine, set it to true - this converts LF endings into CRLF when you check out code: $ git config --global core.autocrlf true 2018-04-16 16:34:39 +02:00			`.DS_Store`
Expand gitignore to cover files created by Visual Micro (#2934) * Expand gitignore to cover files created by Visual Micro's Arduino IDE for Visual Studio (cherry picked from commit d6209c79ea16a26564fe27e74e5f277160129847) * Also ignore VS project files (cherry picked from commit e0ec212bd41e75a3570a6098a66ee66787db58db) 2019-07-09 18:28:04 +02:00
			`#Ignore files built by Visual Studio/Visual Micro`
			`[Dd]ebug*/`
			`[Rr]elease*/`
			`.vs/`
			`__vm/`
			`.vcxproj`
M5Stack's product offering includes various ESP32-based camera devices. (#4030) They are all broadly similar, all being based on the ESP32-D0WD core, but have some subtle differences between variants around PSRAM inclusion and camera pin mappings. The ESP32CAM "unit" product (SKU: U007) has no PSRAM and maps the "Pixel Data 0" (Y2 GPIO/OV2640 D2) camera pin to IO17 rather than IO32 as is the case with most other M5Stack ESP32 camera devices. The ESP32CAM also requires the "hmirror" and "vflip" camera configuration bits setting in order to capture a true image. The relevant M5Stack pin configuration documentation can be found here: https://docs.m5stack.com/#/en/unit/esp32cam?id=pinmap 2020-06-01 00:41:56 +02:00			`.vscode/`