-
Notifications
You must be signed in to change notification settings - Fork 13.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to SDK 1.0.0 #1
Comments
Sorry. I didn't see that issue before I added mine BTW. I did briefly try replacing the 0.9 SDK in the repo with the 1.0 SDK but got lots of errors, missing at least 1 header and also missing some internal functions that were in 0.9 |
No problem. |
OK. Looks like quite a few things are different C:\Users\rclark\Documents\Arduino\hardware\arduino-esp8266/tools/xtensa-lx106-elf/bin/xtensa-lx106-elf-g++ -D__ets__ -DICACHE_FLASH -IC:\Users\rclark\Documents\Arduino\hardware\arduino-esp8266/tools/sdk//include -c -Os -mlongcalls -mtext-section-literals -fno-exceptions -fno-rtti -std=c++11 -MMD -DF_CPU=80000000L -DARDUINO=10601 -DARDUINO_ESP8266_ESP01 -DARDUINO_ARCH_ESP8266 -IC:\Users\rclark\Documents\Arduino\hardware\arduino-esp8266\esp8266\cores\esp8266 -IC:\Users\rclark\Documents\Arduino\hardware\arduino-esp8266\esp8266\variants\esp01 C:\Users\rclark\AppData\Local\Temp\build5447791988060577372.tmp\sketch_mar29a.cpp -o C:\Users\rclark\AppData\Local\Temp\build5447791988060577372.tmp\sketch_mar29a.cpp.o Unfortunatly its getting really late here (almost 10:30pm) and I'm not a night owl, so I will need to call it a day and take another look tomorrow about why there seems to be so many issues with typedefs PS. I better check I have a clean version of the 1.0SDK as I got it from www.arduinoesp.com and his build for Arduino (which was instantly made redundant when you released your much better version ;0) Thanks Roger |
Will post the link to the new bundle when build completes. |
Many thanks I'll clone your whole repo to my local machine and copy the necessary hardware files to my local repo and then push my hardware files only stuff back to my repo Cheers Actually, when I get time I will just be able to set parts of your hardware folder as a sub module But just to get this working today, I'll just clone and then do a local copy. |
@rogerclarkmelbourne Why do we need a separate repository? Wouldn't it be easier to add a simple shell script which would package the necessary files, and then run this as a build script? Every commit is built on Travis CI and Appveyor, so it should be easy to build the right package there. |
I agree We don't need a separate repo. Where are your Xtensia compilor exe files kept? I can't see them in you repo. :-( I'd need to build the script to bundle the compilor files into the tools/xtensa-lx106-elf folder etc But I'm currently using a different set of compilor files, because of the issue in your initial Windows 1.6.1-p1 release with libiconv-2.dll not being found by gcc PS. |
If you check the build.xml you'll see that during the build the archives are downloaded from the following URLs: http://download.igrr.me/osx-xtensa-lx106-elf.tgz This looks like a good layout for all the tools: https://github.com/sandeepmistry/esp8266-Arduino |
@rogerclarkmelbourne |
Thanks. I'll take a look at those links. Please close this one ;-) |
Skip ':' inside SHA1 signatures in WiFiClientSecure.cpp .
Rewrite the request handling in the DNSServer code to address the following issues: Compatibility with EDNS esp8266#1: RFC6891 says that "Responders that choose not to implement the protocol extensions defined in this document MUST respond with a return code (RCODE) of FORMERR to messages containing an OPT record in the additional section and MUST NOT include an OPT record in the response" If we have any additional records in the request, then we need to return a FORMERR, and not whatever custom error code the user may have set. Compatibility with EDNS esp8266#2: If we're returning an error, we need to explicitly zero all of the record counters. In the existing code, if there is an additional record present in the request, we return an ARCOUNT of 1 in the response, despite including no additional records in the payload. Don't answer non-A requests If we receive an AAAA request (or any other non-A record) requests, we shouldn't respond to it with an A record. Don't answer non-IN requests If we receive a request for a non-IN type, don't answer it (it's unlikely that we'd see this in the real world) Don't read off the end of malformed packets If a packet claims to have a query, but then doesn't include one, or includes a query with malformed labels, don't read off the end of the allocated data structure.
* DNSServer: Handle examplewww.com correctly Just replacing 'www.' with the empty string when we assign the domainname will remove all occurrences of 'www.', not just those at the start of the string. Change this to a startsWith check so that only "www." at the beginning of the string is removed. * DNSServer: Rework request handling Rewrite the request handling in the DNSServer code to address the following issues: Compatibility with EDNS #1: RFC6891 says that "Responders that choose not to implement the protocol extensions defined in this document MUST respond with a return code (RCODE) of FORMERR to messages containing an OPT record in the additional section and MUST NOT include an OPT record in the response" If we have any additional records in the request, then we need to return a FORMERR, and not whatever custom error code the user may have set. Compatibility with EDNS #2: If we're returning an error, we need to explicitly zero all of the record counters. In the existing code, if there is an additional record present in the request, we return an ARCOUNT of 1 in the response, despite including no additional records in the payload. Don't answer non-A requests If we receive an AAAA request (or any other non-A record) requests, we shouldn't respond to it with an A record. Don't answer non-IN requests If we receive a request for a non-IN type, don't answer it (it's unlikely that we'd see this in the real world) Don't read off the end of malformed packets If a packet claims to have a query, but then doesn't include one, or includes a query with malformed labels, don't read off the end of the allocated data structure. * DNSServer: Clarify and tidy writing the answer record Modify the code used to write the answer record back to the server so that it is clearer that we are writing network byte order 16-bit quantities, and to clarify what's happening with the pointer used at the start of the answer.
Making pasted compile logs less painful to the eyes
Need to update from SDK 0.9.5 to SDK 1.0.0
The text was updated successfully, but these errors were encountered: