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

xplat: Improve ICU fallback conditions #3135

Merged
merged 2 commits into from
Jun 13, 2017

Conversation

obastemur
Copy link
Collaborator

node-chakracore was silently falling back to no-icu. Couple of changes to be more proactive when a custom ICU path is given. Similarly, do not fallback to no-icu when custom ICU path is given.

Make sure ICU path exists and support relative paths. Keep build from no-icu fallback in case custom path is given
@obastemur
Copy link
Collaborator Author

@kfarnung @kunalspathak Thanks for the review

@chakrabot chakrabot merged commit 346fc90 into chakra-core:release/1.5 Jun 13, 2017
chakrabot pushed a commit that referenced this pull request Jun 13, 2017
Merge pull request #3135 from obastemur:dont_fall

node-chakracore was silently falling back to `no-icu`. Couple of changes to be more proactive when a custom ICU path is given. Similarly, do not fallback to `no-icu` when custom ICU path is given.
chakrabot pushed a commit that referenced this pull request Jun 13, 2017
…ions

Merge pull request #3135 from obastemur:dont_fall

node-chakracore was silently falling back to `no-icu`. Couple of changes to be more proactive when a custom ICU path is given. Similarly, do not fallback to `no-icu` when custom ICU path is given.
chakrabot pushed a commit that referenced this pull request Jun 13, 2017
…llback conditions

Merge pull request #3135 from obastemur:dont_fall

node-chakracore was silently falling back to `no-icu`. Couple of changes to be more proactive when a custom ICU path is given. Similarly, do not fallback to `no-icu` when custom ICU path is given.
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.

5 participants