Enable PlatformIO

.gitignore

@@ -4,7 +4,9 @@ build/
 buildcache/
 arduino.json
 c_cpp_properties.json
-.vscode
 
-/platformio-override.ini
-/release/
+/.vscode/
+/release
+/platformio_override.ini
+/.pio/
+/esp8266-fastled-webserver/esp8266-fastled-webserver.ino.cpp

esp8266-fastled-webserver/common.h

@@ -31,10 +31,6 @@
   #include <FastLED.h>
   FASTLED_USING_NAMESPACE
 
-  extern "C" {
-  #include "user_interface.h"
-  }
-
   #include <LittleFS.h>
   #define MYFS LittleFS
 

esp8266-fastled-webserver/config.h

@@ -24,18 +24,21 @@
 // When compiling from Arduino, you can edit this file.
 // When compiling from PlatformIO, this is a reference for compiler flags.
 
-#define PRODUCT_DEFAULT
-// #define PRODUCT_FIBONACCI512
-// #define PRODUCT_FIBONACCI256
-// #define PRODUCT_FIBONACCI128
-// #define PRODUCT_FIBONACCI64_FULL  // 86mm, WS2812B-5050, ~60mA/pixel
-// #define PRODUCT_FIBONACCI64_MINI  // 64mm, WS2812B-3535, ~60mA/pixel
-// #define PRODUCT_FIBONACCI64_MICRO // 40mm, WS2812C-2020,  ~5mA/pixel
-// #define PRODUCT_FIBONACCI64_NANO  // 33mm, SK6805-EC15,   ~5mA/pixel
-// #define PRODUCT_FIBONACCI32
-// #define PRODUCT_KRAKEN64
-// #define PRODUCT_ESP8266_THING // aka parallel (6-output)
-// #define PRODUCT_1628_RINGS
+#if !defined(BUILDING_USING_PLATFORMIO)
+    #define PRODUCT_DEFAULT
+    // #define PRODUCT_FIBONACCI512
+    // #define PRODUCT_FIBONACCI256
+    // #define PRODUCT_FIBONACCI128
+    // #define PRODUCT_FIBONACCI64_FULL  // 86mm, WS2812B-5050, ~60mA/pixel
+    // #define PRODUCT_FIBONACCI64_MINI  // 64mm, WS2812B-3535, ~60mA/pixel
+    // #define PRODUCT_FIBONACCI64_MICRO // 40mm, WS2812C-2020,  ~5mA/pixel
+    // #define PRODUCT_FIBONACCI64_NANO  // 33mm, SK6805-EC15,   ~5mA/pixel
+    // #define PRODUCT_FIBONACCI32
+    // #define PRODUCT_KRAKEN64
+    // #define PRODUCT_ESP8266_THING // aka parallel (6-output)
+    // #define PRODUCT_1628_RINGS
+#endif /// !defined(BUILDING_USING_PLATFORMIO)
+
 
 // ////////////////////////////////////////////////////////////////////////////////////////////////////
 // Additional configuration options ... defaults shown

esp8266-fastled-webserver/esp8266-fastled-webserver.ino

@@ -110,6 +110,9 @@ const PatternAndName patterns[] = {
 #endif
 
   { colorWaves,             "Color Waves" },
+#if IS_FIBONACCI
+  { colorWavesFibonacci,               "Color Waves Fibonacci" },
+#endif
 
 #if HAS_COORDINATE_MAP // really a wrong name... and likely doing way more computation than necessary
   { radarSweepPalette, "Radar Sweep Palette" },
@@ -132,8 +135,6 @@ const PatternAndName patterns[] = {
 #endif
 
 #if IS_FIBONACCI
-  { colorWavesFibonacci,               "Color Waves Fibonacci" },
-
   { pridePlayground,                   "Pride Playground" },
   { pridePlaygroundFibonacci,          "Pride Playground Fibonacci" },
 

include/README

@@ -0,0 +1,39 @@
+
+This directory is intended for project header files.
+
+A header file is a file containing C declarations and macro definitions
+to be shared between several project source files. You request the use of a
+header file in your project source file (C, C++, etc) located in `src` folder
+by including it, with the C preprocessing directive `#include'.
+
+```src/main.c
+
+#include "header.h"
+
+int main (void)
+{
+ ...
+}
+```
+
+Including a header file produces the same results as copying the header file
+into each source file that needs it. Such copying would be time-consuming
+and error-prone. With a header file, the related declarations appear
+in only one place. If they need to be changed, they can be changed in one
+place, and programs that include the header file will automatically use the
+new version when next recompiled. The header file eliminates the labor of
+finding and changing all the copies as well as the risk that a failure to
+find one copy will result in inconsistencies within a program.
+
+In C, the usual convention is to give header files names that end with `.h'.
+It is most portable to use only letters, digits, dashes, and underscores in
+header file names, and at most one dot.
+
+Read more about using header files in official GCC documentation:
+
+* Include Syntax
+* Include Operation
+* Once-Only Headers
+* Computed Includes
+
+https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html

lib/README

@@ -0,0 +1,46 @@
+
+This directory is intended for project specific (private) libraries.
+PlatformIO will compile them to static libraries and link into executable file.
+
+The source code of each library should be placed in a an own separate directory
+("lib/your_library_name/[here are source files]").
+
+For example, see a structure of the following two libraries `Foo` and `Bar`:
+
+|--lib
+|  |
+|  |--Bar
+|  |  |--docs
+|  |  |--examples
+|  |  |--src
+|  |     |- Bar.c
+|  |     |- Bar.h
+|  |  |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
+|  |
+|  |--Foo
+|  |  |- Foo.c
+|  |  |- Foo.h
+|  |
+|  |- README --> THIS FILE
+|
+|- platformio.ini
+|--src
+   |- main.c
+
+and a contents of `src/main.c`:
+```
+#include <Foo.h>
+#include <Bar.h>
+
+int main (void)
+{
+  ...
+}
+
+```
+
+PlatformIO Library Dependency Finder will find automatically dependent
+libraries scanning project source files.
+
+More information about PlatformIO Library Dependency Finder
+- https://docs.platformio.org/page/librarymanager/ldf.html

pio-scripts/obj-dump.py

@@ -0,0 +1,9 @@
+# Little convenience script to get an object dump
+
+Import('env')
+
+def obj_dump_after_elf(source, target, env):
+    print("Create firmware.asm")
+    env.Execute("xtensa-lx106-elf-objdump "+ "-D " + str(target[0]) + " > "+ "${PROGNAME}.asm")
+
+env.AddPostAction("$BUILD_DIR/${PROGNAME}.elf", [obj_dump_after_elf])

pio-scripts/strip-floats.py

@@ -0,0 +1,15 @@
+Import('env')
+
+#
+# Dump build environment (for debug)
+#print env.Dump()
+#
+
+flags = " ".join(env['LINKFLAGS'])
+flags = flags.replace("-u _printf_float", "")
+flags = flags.replace("-u _scanf_float", "")
+newflags = flags.split()
+
+env.Replace(
+  LINKFLAGS=newflags
+)