Re: SDK Layout & use in other projects

2015-07-21T18:15:34+08:00

I think these are all very sensible suggestions - I'd also love to see less patching and just do more regular versioned releases. There's a lot of room for error with patching. Given that you already have code on GitHub, maybe just keep all development of the SDK there and just use their releases functionality to do distribution. It's better than doing this through a web forum and makes it easier to see a list of previous versions with release notes, etc. and being able to see what has changed in the code. Just a thought
Keep up the good work,
Ben

Statistics: Posted by bjpirt — Tue Jul 21, 2015 6:15 pm

SDK Layout & use in other projects

2015-07-21T17:10:30+08:00

We use the espressif SDK to compile an application. The applications source code is managed in a git repository.
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.
For example:
/opt/espressif/sdk/sdk1.2XXXX
/opt/espressif/sdk/current ->/opt/espressif/sdk/sdk1.2XXXX
/home/username/git/myapp/Makefile
/home/username/git/myapp/src/user.c
(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
-I/opt/espressif/sdk/current/include
-l/opt/espressif/sdk/current/lib
/opt/espressif/sdk/current/src/*.c
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.

Statistics: Posted by SingingCat — Tue Jul 21, 2015 5:10 pm

ESP8266 Developer Zone

Re: SDK Layout & use in other projects

SDK Layout & use in other projects