Skip to content

Ensuring UTF-8 encoding for MSVC builds #5870

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

Closed
wants to merge 4 commits into from
Closed

Ensuring UTF-8 encoding for MSVC builds #5870

wants to merge 4 commits into from

Conversation

shellygr
Copy link
Contributor

Support for different locales in WIN compilation by setting /utf-8 flag in MSVC.

Build may otherwise fail with errors such as:
solidity\test\libdevcore\utf8.cpp : warning C4819: The file contains a character that cannot be represented in the current code page (1255). Save the file in Unicode format to prevent data loss

@codecov
Copy link

codecov bot commented Jan 26, 2019

Codecov Report

Merging #5870 into develop will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #5870   +/-   ##
========================================
  Coverage    88.36%   88.36%           
========================================
  Files          349      349           
  Lines        33446    33446           
  Branches      4006     4006           
========================================
  Hits         29553    29553           
  Misses        2535     2535           
  Partials      1358     1358
Flag Coverage Δ
#all 88.36% <100%> (ø) ⬆️
#syntax 28.32% <0%> (ø) ⬆️

@axic
Copy link
Member

axic commented Jan 26, 2019

@shellygr thanks, can you squash the commits into one?

What MSVC versions did required this flag?

@shellygr
Copy link
Contributor Author

Since it's a one line change I'll close this pull request and open another one.
Re. your question - it's VS2017. Not sure this option existed before that.

@axic
Copy link
Member

axic commented Jan 26, 2019

If you create PRs from branches it is usually easier to squash/rebase/.. work with them.

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.

4 participants