-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
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
[BUG] marlin 2.1.2.1 compilation error #26046
Comments
AngelSerra
changed the title
marlin 2.2.2.2 compilation error
marlin 2.1.2.1 compilation error
Jul 3, 2023
AngelSerra
changed the title
marlin 2.1.2.1 compilation error
[BUG] marlin 2.1.2.1 compilation error
Jul 3, 2023
Provided configs with ESP3D_WIFISUPPORT enabled compiles without issue on marlin 2.1.2.1 |
Delete your |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Did you test the latest
bugfix-2.1.x
code?Yes, and the problem still exists.
Bug Description
The problem,
The problem is that when activating //#define ESP3D_WIFISUPPORT // ESP3D Library WiFi management (https://github.com/luc-github/ESP3DLib)
but the MarlinConfigPre.h file exists and is in its place. as vew in the screenshots of the added file
Bug Timeline
new
Expected behavior
No response
Actual behavior
No response
Steps to Reproduce
No response
Version of Marlin Firmware
2.1.2.1
Printer model
HyperCube
Electronics
Tnybee
Add-ons
Bltouch
Bed Leveling
ABL Linear grid
Your Slicer
Prusa Slicer
Host Software
None
Don't forget to include
Configuration.h
andConfiguration_adv.h
.Additional information & file uploads
Configuration.zip
The problem,
The problem is that when activating //#define ESP3D_WIFISUPPORT // ESP3D Library WiFi management (https://github.com/luc-github/ESP3DLib)
but the MarlinConfigPre.h file exists and is in its place. as vew in the screenshots of the added file
The text was updated successfully, but these errors were encountered: