Currently, each time a new SDK is released we have to modify it to compile our code since the SDK insists on compiling only in the 'app' directory.
It would be very convenient if the SDK could be shipped to
a) compile a directory external to itself.
(Obviously other people have other preferences, but I think the concept is clear )
Then, just like we can do with other sdks, we'd add
in our project Makefile
b) the above should be _very_ consistently working between versions, so to encourage upgrades.
upgrades are painful ATM. Ideally, all that should be necessary is to download, unzip, change symlink: Done.
c) if there any requred flags, such as SPIspeed/flash-size etc. then they will be defined in our Makefile. They just need
to be documented very clearly by espressif.
d) the AT-Command set *must* be entirely optional, since it's usually of no use in applications
e) Generally, whilst it's great that it is meant to be userfriendly with windows click-and-drag tools, forcing the use of those tools actually makes harder for software development in teams. It should work well on linux (debian/ubuntu/centos) and with git - that's IMHO more-or-less the modern way . So the SDK should be more focused (or in addition to) on automated compilation during continous integration cycles.
btw: please get rid of the 76800 Baud rate when starting the cpu in rom. change it to 115200 or 57600 . It's annoying.
Keep up the good work,
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 5 guests
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
We also have a RTOS version and a MESH version too!
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!