Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » CDT-Arduino Problem with extra make targets(CDT-Arduino Problem with extra make targets)
CDT-Arduino Problem with extra make targets [message #1824079] Tue, 07 April 2020 09:54
Eclipse UserFriend
I am running into some problems with the latest Eclipse/Adruino Version
(4.15 / 9.11 CDT/Arduino)

In order to flash a filesystem onto the target I have an additional build target (called flash_spiffs) which I also have in my makefile.ini.
With older versions I could just click on that build target and make generated and flashed the spiffs file System onto my target board.

With the lastest version by default there are no extra build targets enabled (build targets is grey).
OK, this is probably because the Project has "only" C, C++ and Arduino natures.
I tried adding the CDT Make nature, which enabled the make targets, but it did not find make(.exe). So I adjusted the $PATH variable to find it, but now it compains about not being able to find the make target. So apprently it does not look at my makefile.ini... Here nothing else is configurable.
So how to resolve this? (Besides writing a script to do this outside eclipse)

My build target is set to stop on first error, and running all builders is off.

My makefile.ini
vecho := @echo
Q := @

ARDUINO_BASE      = C:/daten/.arduinocdt
ESP32_TOOLS		  = $(ARDUINO_BASE)/packages/esp32/tools

flash_spiffs:
	$(vecho) Starting mkspiffs...
	
# TODO make spiffs images
# Upload image via esptool
	$(ESP32_TOOLS)/mkspiffs/0.2.3/mkspiffs.exe -c "../data" -s 196608 -p 3997696 mkspiffs.bin
	$(ESP32_TOOLS)/esptool_py/2.6.1/esptool.exe --chip esp32 --port COM13 --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dout --flash_freq 40m --flash_size detect 0x3D0000 D:\Dropbox\source\workspace\sbiot/Release/mkspiffs.bin 


The output on the console is:
16:47:06 **** Build of project sbiot ****
make flash_spiffs 
make: *** No rule to make target 'flash_spiffs'.  Stop.
"make flash_spiffs" terminated with exit code 2. Build might be incomplete.


Previous Topic:Remote debugging from Mac to Docker
Next Topic:[SOLVED] "Unresolved inclusion: <stdio.h>" in C project!!
Goto Forum:
  


Current Time: Thu Jul 17 09:26:30 EDT 2025

Powered by FUDForum. Page generated in 0.06916 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top