[BUG] Compilation error when MESH_EDIT_MENU is enabled for AUTO_BED_LEVELING_[LINEAR|3POINT]

[ondrada]

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

When ABL is configured as AUTO_BED_LEVELING_LINEAR or AUTO_BED_LEVELING_3POINT and both LCD_BED_LEVELING and MESH_EDIT_MENU options are enabled in Configuration.h, Marlin fails to compile and gives errors about undeclared preprocessor variables Z_VALUES (for both AUTO_BED_LEVELING_3POINT and AUTO_BED_LEVELING_LINEAR) and GRID_MAX_POINTS_X and GRID_MAX_POINTS_Y (for AUTO_BED_LEVELING_3POINT only).

I've tried to solve that by adding a condition to enable Mesh edit menu only if HAS_MESH (here: ondrada@63150c5 ). But don't know if it wouldn't be better to add a conditional like "MESH_EDIT_MENU is not compatible with AUTO_BED_LEVELING_LINEAR/AUTO_BED_LEVELING_3POINT", or if it is possible to have the menu without 'Z' part for AUTO_BED_LEVELING_LINEAR.

Bug Timeline

No response

Expected behavior

Compilable Marlin when AUTO_BED_LEVELING_[LINEAR|3POINT] is selected together with LCD_BED_LEVELING and MESH_EDIT_MENU, or some incompatibility message.

Actual behavior

Compilation failure with beyond combination of options in Configuration.h

Steps to Reproduce

Try to compile Marlin with:
LCD_BED_LEVELING enabled
MESH_EDIT_MENU enabled
AUTO_BED_LEVELING_LINEAR or AUTO_BED_LEVELING_3POINT enabled

Version of Marlin Firmware

2.0.x bugfix

Printer model

Ender 3 Pro

Electronics

BTT E3 RRF

Add-ons

No response

Your Slicer

No response

Host Software

No response

Additional information & file uploads

No response

[ellensp]

AUTO_BED_LEVELING_LINEAR and AUTO_BED_LEVELING_3POINT are not MESHES, so enabling MESH_EDIT_MENU does not make sense.

[ondrada]

I see that, wasn't sure about LINEAR... But shouldn't there be some message like "MESH_EDIT_MENU is not compatible with AUTO_BED_LEVELING_LINEAR/AUTO_BED_LEVELING_3POINT" in SanityCheck.h or somewhere, rather than compile errors at Marlin/src/lcd/menu/menu_bed_leveling.cpp ?

[github-actions]

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.