Eclipse 2018-12 local.eagle.app.v6.common.ld: No such file or directory

[Superfred1]

Hello,
the build with Eclipse fails with the Error "cannot open linker script file local.eagle.app.v6.common.ld: No such file or directory"

Esp8266 Arduino 2.5.0-beta2
Eclipse Version: 2018-12 (4.10.0) Build id: 20181214-0600 Windows 1809 64 Bit
Plugin: Eclipse C++ IDE for Arduino 3.0 (not the Sloeber Plugin), installed per default in Eclipse .

Exact Log message:
....
"C:/Users/xxxx/.arduinocdt/packages/esp8266/tools/xtensa-lx106-elf-gcc/2.5.0-3-20ed2b9/bin/xtensa-lx106-elf-gcc" -Wl,-Map "-Wl,./T2.map" -g -w -Os -nostdlib -Wl,--no-check-sections -u app_entry -u _printf_float -u _scanf_float -Wl,-static "-LC:\Users\xxxx.arduinocdt\packages\esp8266\hardware\esp8266\2.5.0-beta2/tools/sdk/lib" "-LC:\Users\xxxx.arduinocdt\packages\esp8266\hardware\esp8266\2.5.0-beta2/tools/sdk/ld" "-LC:\Users\xxxx.arduinocdt\packages\esp8266\hardware\esp8266\2.5.0-beta2/tools/sdk/libc/xtensa-lx106-elf/lib" "-Teagle.flash.512k.ld" -Wl,--gc-sections -Wl,-wrap,system_restart_local -Wl,-wrap,spi_flash_read -o "./T2.elf" -Wl,--start-group project/T2.cpp.o "./core.a" -lhal -lphy -lpp -lnet80211 -llwip2-536-feat -lwpa -lcrypto -lmain -lwps -lbearssl -laxtls -lespnow -lsmartconfig -lairkiss -lwpa2 -lstdc++ -lm -lc -lgcc -Wl,--end-group "-L."

c:/users/xxxx/.arduinocdt/packages/esp8266/tools/xtensa-lx106-elf-gcc/2.5.0-3-20ed2b9/bin/../lib/gcc/xtensa-lx106-elf/4.8.2/../../../../xtensa-lx106-elf/bin/ld.exe: cannot open linker script file local.eagle.app.v6.common.ld: No such file or directory

Board selected: Generic ESP 8266 Module

Even with this minimal Sketch:
#include <Arduino.h>
void setup() {
}
void loop() {
}

ESP32 and AVR Boards working fine.

I tried this but still not working: https://arduino-esp8266.readthedocs.io/en/latest/eclipse/eclipse.html

[earlephilhower]

The local.eagle.app.v6.common.ld file is generated by a stage of the platform.txt using settings from the IDE or #defines to adjust where things like vtables are placed.

I think the document you're pointing to in our readthedocs is related to the Sloeber(sp?) plugin, but you mention another plugin. Is there some steps you used to get the generic Arduino plugin going?

[Superfred1]

Is there some steps you used to get the generic Arduino plugin going?

Actually it is very simple because the Arduino plugin is already installed:
-Download & extract eclipse-cpp-2018-12-R-win32-x86_64.zip
-Start eclipse.exe
-klick Window->Preferences, open C/C++->Arduino
-Add the esp8266 / ESP32 json file(s), close
-Klick Help->Arduino Downloads Manager
-Select esp8266 and/or ESP32, close, wait until installation finishes
-Kilck File->New->Arduino Project
-Add a Launch Target (6th Symbol from left), select Arduino and your board type.
Done.

[Superfred1]

I forgot:
You have to enable the libraries you need in the project properties:
Alt+Enter, go to Libraries and enable what you need (Wifi, etc).

[earlephilhower]

I was able to repro this locally. It's in the Eclipse IDE, so I'm not sure we can do anything on our end.

I've opened the following bug report there:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=543476

[d-a-v]

@Superfred1 You probably can use a generated version of this file until the bug is solved.

[Superfred1]

@d-a-v Now it compiles, but the .bin file is not created:
...
"C:/Users/xxxx/.arduinocdt/packages/esp8266/tools/xtensa-lx106-elf-gcc/2.5.0-3-20ed2b9/bin/xtensa-lx106-elf-g++" -D__ets__ -DICACHE_FLASH -U__STRICT_ANSI__ "-IC:\Users\xxxx.arduinocdt\packages\esp8266\hardware\esp8266\2.5.0-beta2/tools/sdk/include" "-IC:\Users\xxxx.arduinocdt\packages\esp8266\hardware\esp8266\2.5.0-beta2/tools/sdk/lwip2/include" "-IC:\Users\xxxx.arduinocdt\packages\esp8266\hardware\esp8266\2.5.0-beta2/tools/sdk/libc/xtensa-lx106-elf/include" "-I./core" -c -w -Os -g -mlongcalls -mtext-section-literals -fno-rtti -falign-functions=4 -std=c++11 -MMD -ffunction-sections -fdata-sections -fexceptions -DF_CPU=80000000L -DLWIP_OPEN_SRC -DTCP_MSS=536 -DLWIP_FEATURES=1 -DLWIP_IPV6=0 -DARDUINO=10608 -DARDUINO_ESP8266_GENERIC -DARDUINO_ARCH_ESP8266 -DARDUINO_BOARD="ESP8266_GENERIC" -DLED_BUILTIN=2 -DESP8266 -I"C:/Users/xxxx/.arduinocdt/packages/esp8266/hardware/esp8266/2.5.0-beta2/cores/esp8266" -I"C:/Users/xxxx/.arduinocdt/packages/esp8266/hardware/esp8266/2.5.0-beta2/variants/generic" "C:/Users/xxxx/.arduinocdt/packages/esp8266/hardware/esp8266/2.5.0-beta2/cores/esp8266/WString.cpp" -o "core/WString.cpp.o"

"C:/Users/xxxx/.arduinocdt/packages/esp8266/tools/xtensa-lx106-elf-gcc/2.5.0-3-20ed2b9/bin/xtensa-lx106-elf-ar" cru "./core.a" "core/WString.cpp.o"

"C:/Users/xxxx/.arduinocdt/packages/esp8266/tools/xtensa-lx106-elf-gcc/2.5.0-3-20ed2b9/bin/xtensa-lx106-elf-gcc" -Wl,-Map "-Wl,./T4.map" -g -w -Os -nostdlib -Wl,--no-check-sections -u app_entry -u _printf_float -u _scanf_float -Wl,-static "-LC:\Users\xxxx.arduinocdt\packages\esp8266\hardware\esp8266\2.5.0-beta2/tools/sdk/lib" "-LC:\Users\xxxx.arduinocdt\packages\esp8266\hardware\esp8266\2.5.0-beta2/tools/sdk/ld" "-LC:\Users\xxxx.arduinocdt\packages\esp8266\hardware\esp8266\2.5.0-beta2/tools/sdk/libc/xtensa-lx106-elf/lib" "-Teagle.flash.512k.ld" -Wl,--gc-sections -Wl,-wrap,system_restart_local -Wl,-wrap,spi_flash_read -o "./T4.elf" -Wl,--start-group project/T4.cpp.o "./core.a" -lhal -lphy -lpp -lnet80211 -llwip2-536-feat -lwpa -lcrypto -lmain -lwps -lbearssl -laxtls -lespnow -lsmartconfig -lairkiss -lwpa2 -lstdc++ -lm -lc -lgcc -Wl,--end-group "-L."

Program store usage: 283331 of maximum 499696 bytes

Initial RAM usage: 26875 of maximum 81920 bytes

esptool v0.4.13-1-gf80ae31 - (c) 2014 Ch. Klippel ck@atelier-klippel.de
setting board to ck
setting baudrate from 115200 to 115200
setting port from COM1 to COM3
setting address from 0x00000000 to 0x00000000
espcomm_upload_file
error: stat ./T3.bin failed: No such file or directory

[d-a-v]

It's the same bug as the one @earlephilhower reported:
Another recipe is not executed ref

It is much more complex to generate it by hand, it would be

esptool.exe -eo bootloaders/eboot/eboot.elf -bo firmware.bin -bm dio -bf 40 -bz 4M -bs .text -bp 4096 -ec -eo firmware.elf -bs .irom0.text -bs .text -bs .data -bs .rodata -bc -ec

(and adjust all these options according to your configuration)

Then you would have to flash it by hand too...
You should go and vote on the issue to the reported bug on eclipse website.

You also may have a look to sloeber, it seems to work

[Superfred1]

@earlephilhower @d-a-v
Thank you for looking into this.
I have an older version of Eclipse + Sloeber working, so no problem for me.

I reported this because I see a great potential for the future in the native Arduino support in Eclipse.

Have a nice day.
Fred

[earlephilhower]

http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/tree/toolchains/arduino/org.eclipse.cdt.arduino.core/src/org/eclipse/cdt/arduino/core/internal/build/ArduinoBuildConfiguration.java?id=ffdb004e6711ddffc0174341f97dfc44d8619246#n329

The Arduino builder for Eclipse only looks for a very few, un-numbered properties. It looks like it's not a big deal to have it iterate over any numbered ones as well as stick prelink/etc. in there somewhere (assuming there sis some way to combine multiple buildModel.put()s

buildModel.put("recipe_cpp_o_pattern", resolveProperty("recipe.cpp.o.pattern", properties)); //$NON-NLS-1$ //$NON-NLS-2$
buildModel.put("recipe_c_o_pattern", resolveProperty("recipe.c.o.pattern", properties)); //$NON-NLS-1$ //$NON-NLS-2$
buildModel.put("recipe_S_o_pattern", resolveProperty("recipe.S.o.pattern", properties)); //$NON-NLS-1$ //$NON-NLS-2$
buildModel.put("recipe_ar_pattern", resolveProperty("recipe.ar.pattern", properties)); //$NON-NLS-1$ //$NON-NLS-2$
buildModel.put("recipe_c_combine_pattern", resolveProperty("recipe.c.combine.pattern", properties)); //$NON-NLS-1$ //$NON-NLS-2$
buildModel.put("recipe_objcopy_eep_pattern", resolveProperty("recipe.objcopy.eep.pattern", properties)); //$NON-NLS-1$ //$NON-NLS-2$
buildModel.put("recipe_objcopy_hex_pattern", resolveProperty("recipe.objcopy.hex.pattern", properties)); //$NON-NLS-1$ //$NON-NLS-2$
buildModel.put("recipe_objcopy_bin_pattern", resolveProperty("recipe.objcopy.bin.pattern", properties)); //$NON-NLS-1$ //$NON-NLS-2$
buildModel.put("recipe_size_pattern", resolveProperty("recipe.size.pattern", properties)); //$NON-NLS-1$ //$NON-NLS-2$

[grothag]

Any news on this ?

[d-a-v]

@grothag This is on eclipse, not us. Issues there are opened, see above post

You can however use the eclipse sloeber extension (which we do not support here but users like @Superfred1 (and @hreintke I think) use with no issue). What about trying it ?