- Sun May 10, 2015 3:02 am
#17059
Well actually that part is already more or less ready! I am using the free esp sdk, which compiles a completegcc suite. After that, it appears to be simply compiling with the proper -I flags (include directory), -L flags (library locations), a linker script (which is supplied by the sdk) and the pre-build libraries of the sdk (.a files).
Last week I took the whole "standard" Makefile apart (which is used by "everybody" but is really far too complex for simple projects) and made a simple one from scratch that just the job and does it well. The standard makefile isn't good at detecting changes in source files, really the reason why'd want to use a makefile in the first place, otherwise you'd could just use a script as well. It also gets rid of the ridiculous subdirectories, submakefiles, etc.
What I really need now is proper documentation of the hardware, on "datasheet"-level.
Last week I took the whole "standard" Makefile apart (which is used by "everybody" but is really far too complex for simple projects) and made a simple one from scratch that just the job and does it well. The standard makefile isn't good at detecting changes in source files, really the reason why'd want to use a makefile in the first place, otherwise you'd could just use a script as well. It also gets rid of the ridiculous subdirectories, submakefiles, etc.
What I really need now is proper documentation of the hardware, on "datasheet"-level.
