Skip to content
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

[win] removed exported zlib symbols #6

Open
wants to merge 34 commits into
base: nw17
Choose a base branch
from

Conversation

ghostoy
Copy link
Member

@ghostoy ghostoy commented Aug 18, 2016

Checklist
  • make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)
Description of change

zlib symbols was exported in c843e58 with zlib 1.2.8. Node.js in NW
was built with chromium zlib 1.2.5 + google's patches, which didn't
exported those symbols.

rogerwang and others added 30 commits August 18, 2016 08:40
run nw as node

decouple node dll

add g_dom_context
fixup! chromium-integration

fixup! new mac loop
Or we'll have loop in the list when the async req
is inserted again by uv_async_send_nw

Fix nwjs/nw.js#2332
src\third_party\node\src\node_revert.cc(15) : warning C4065: switch statement contains 'default' but no 'case' labels
Strings in DOM may be converted to two bytes representation, which
should be processed as array of `uint16_t` when decoding hex or
base64.

base64 decoding in Node.js can fallback to a slow implementation
to skip invalid characters (i.e. `\0` in this case). This patch
can also keep base64 decoding running under the fast implementation.

fixed nwjs/nw.js#5069
GnorTech and others added 4 commits August 18, 2016 08:40
zlib symbols was exported in c843e58 with zlib 1.2.8. Node.js in NW
was built with chromium zlib 1.2.5 + google's patches, which didn't
exported those symbols.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants