ESP-IDF: Propagating compiler flags to ExternalProject builds

[Lapshin]

📝 Description

Publish date

Expected publish date: YYYY-MM-DD

Review process

• Initiate technical review
  • This item is N/A
  • Add subject matter experts (your team members, experts in the field)
• Once tech review mostly done, initiate editorial review
  • Add technical editors (@f-hollow, @FBEZ, and/or @pedrominatel)

Checks

• Article folder and file names:
  • Folder path is content/blog/YYYY/MM/my-new-article (articles only)
  • Folder and file names have no underscores, spaces, or uppercase letters (My new_article)
• New article's YAML frontmatter:
  • Title updated
  • Date matches the format date: 20YY-MM-DD
  • Summary updated
  • Authors added (see Add youself as an author)
  • Tags added
• Updated article's YAML frontmatter:
  
  • This item is N/A
  • If article folder is moved or renamed, the field aliases: with a new URL slug is added
  • Date of update is added lastmode: 20YY-MM-DD
• Article media files:
  • All images are in .WebP format (see Use WebP for raster images)
  • Images are compressed within 100-300 KB, with a hard limit of ≤ 500 kB
  • Where possible, Hugo shortcodes are used instead of raw HTML for content types unsupported by markdown (see Use additional content types)
• Links in articles
  • Make sure all links are valid
  • No links to Google docs present
  • Use a specific ESP-IDF version in links (avoid stable, hard no for latest)
• Git history
  • Commits are clean and squashed to the minimum necessary
  • Commit messages follow Conventional Commits format
  • Your feature branch is rebased on main

🔗 Related

🧪 Testing (Hugo)

[github-actions]

🎉 A preview for this PR is available at: https://preview-developer.espressif.com/pr697/