Skip to content

Not able to compile WLED with Visual Studio Code #4171

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

Closed
1 task done
TPPTim opened this issue Oct 2, 2024 · 8 comments
Closed
1 task done

Not able to compile WLED with Visual Studio Code #4171

TPPTim opened this issue Oct 2, 2024 · 8 comments
Labels
documentation documentation should be updated to explain behaviour question workaround The issue contains a workaround

Comments

@TPPTim
Copy link

TPPTim commented Oct 2, 2024

What happened?

Hello,
I am not able to compile the WLED project using Visual Studio Code. I followed this guide: https://kno.wled.ge/advanced/compiling-wled/

When I hit the build check button on the bottom PIO bar, only this line popps up in the search fild.
image

Nothing else happened. The Problems shows:
image

I did not change any thing else in the WLED project folder. Can you please help me what is wrong?

To Reproduce Bug

Install Git
Install Node JS
Install Visual Studio Code
Install Platform IO Plugin
Open WLED project folder

Expected Behavior

compiling the project

Install Method

Self-Compiled

What version of WLED?

0.14.4

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

No response

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@TPPTim TPPTim added the bug label Oct 2, 2024
@netmindz
Copy link
Member

netmindz commented Oct 2, 2024

You should really be selecting which build env to use. Please also include a screenshot of what is shown when you select platformio on the right

@netmindz netmindz added question and removed bug labels Oct 2, 2024
@TPPTim
Copy link
Author

TPPTim commented Oct 2, 2024

When I hit the build check button still nothing happened.
image

When I click on build at the left side in the menue, then it starts to compile:
image

Is this behavior ok?
The Problem is, i do not know how to compile this way with custom build_flags.

@blazoncek
Copy link
Collaborator

That is a known issue with PIO since update sometime in late 2022.

@TPPTim
Copy link
Author

TPPTim commented Oct 2, 2024

OK thank you very much! What is the common solution for this problem.
Is there an work around or should I use the Build option from the left sided Menue bar instead in future?

@softhack007 softhack007 added workaround The issue contains a workaround documentation documentation should be updated to explain behaviour labels Oct 2, 2024
@softhack007
Copy link
Collaborator

@TPPTim you can either use the build options, or follow this proposal for directly selecting the buildenv:

wled/WLED-Docs#161

@TPPTim
Copy link
Author

TPPTim commented Oct 4, 2024

Thank you very much! I have tried this, but I get an error that I cannot explain.

For this I created the platformio_override.ini in the main Folder and added some -D Pindefines:
image

Warning! Ignore unknown configuration option -d btnpinin section [env:esp32dev_audioreactive] Warning! Ignore unknown configuration option-d irpinin section [env:esp32dev_audioreactive] Warning! Ignore unknown configuration option-d statusledin section [env:esp32dev_audioreactive] Warning! Ignore unknown configuration option-d rlypin` in section [env:esp32dev_audioreactive]
Processing esp32dev_audioreactive (board: esp32dev; platform: [email protected]; framework: arduino)

Verbose mode can be enabled via -v, --verbose option
*** use existing my_config.h ***
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32dev.html
PLATFORM: Espressif 32 (3.5.0) > Espressif ESP32 Dev Module
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (esp-prog) External (esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:

  • framework-arduinoespressif32 @ 0.0.0+sha.4b0c087
  • tool-esptoolpy @ 1.30100.210531 (3.1.0)
  • toolchain-xtensa32 @ 2.50200.97 (5.2.0)
    Converting wled00.ino
    LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
    LDF Modes: Finder ~ chain, Compatibility ~ strict
    Found 36 compatible libraries
    Scanning dependencies...
    Dependency Graph
    |-- LittleFS_esp32 @ 1.0.6+sha.f0817ca
    |-- AsyncTCP @ 1.2.0+sha.38b8475
    |-- FastLED @ 3.6.0
    |-- IRremoteESP8266 @ 2.8.2
    |-- NeoPixelBus @ 2.7.5
    |-- ESPAsyncWebServerWLED @ 2.2.1+sha.6d2540d
    |-- arduinoFFT @ 1.9.2+sha.419d7b0
    |-- Wire @ 1.0.1
    |-- SD(esp32) @ 1.0.5
    |-- SD_MMC @ 1.0
    |-- SPI @ 1.0
    |-- EEPROM @ 1.0.3
    |-- ArduinoOTA @ 1.0
    |-- DNSServer @ 1.1.0
    |-- ESPmDNS @ 1.0
    |-- WiFi @ 1.0
    |-- ESP32 Async UDP @ 1.0.0
    |-- WebServer @ 1.0
    Building in release mode
    Compiling .pio\build\esp32dev_audioreactive\src\wled00.ino.cpp.o
    Retrieving maximum program size .pio\build\esp32dev_audioreactive\firmware.elf
    Checking size .pio\build\esp32dev_audioreactive\firmware.elf
    Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
    RAM: [== ] 22.1% (used 72356 bytes from 327680 bytes)
    Flash: [======== ] 81.7% (used 1284885 bytes from 1572864 bytes)
    ================================================================================ [SUCCESS] Took 20.54 seconds ================================================================================

Environment Status Duration


esp32dev_audioreactive SUCCESS 00:00:20.544
================================================================================= 1 succeeded in 00:00:20.544 =================================================================================

  • Terminal will be reused by tasks, press any key to close it.`

@blazoncek
Copy link
Collaborator

Github issues are not intended to educate users.
Please use WLED forum or Discord for help and support questions.

@blazoncek blazoncek closed this as not planned Won't fix, can't repro, duplicate, stale Oct 4, 2024
@TPPTim
Copy link
Author

TPPTim commented Oct 4, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation documentation should be updated to explain behaviour question workaround The issue contains a workaround
Projects
None yet
Development

No branches or pull requests

4 participants