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

Added option to use char and string when generating atoms.cc #7784

Merged
merged 3 commits into from
Nov 29, 2019

Conversation

TriciaCrichton
Copy link
Contributor

fixes #7783
Add utf8 parameter for gen_file.py to enable creating atoms.cc and atoms.h with char* and std::string types. The default is True to preserve the prior behaviour, using char_t* and std::wstring.

ChromeDriver atoms BUILD was updated to set utf8 to False.

Previous build structure allowed javascript atoms to be built with char_t and
wstring or char and string. This restores that option, with
char_t/wstring as the default. Adds utf8 parameter.
@CLAassistant
Copy link

CLAassistant commented Nov 23, 2019

CLA assistant check
All committers have signed the CLA.

@TriciaCrichton
Copy link
Contributor Author

I don't believe the build failures are related to this change, the first references unresolveable dependencies on @platforms//os. The second is a classpath error while generating javadocs. Those definitions were not modified by this PR.

@shs96c
Copy link
Member

shs96c commented Nov 29, 2019

Ah! Nice. Merging this now. Thank you for the patch!

@shs96c shs96c merged commit 3950338 into SeleniumHQ:master Nov 29, 2019
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.

Enable use of char and string when generating atoms.cc
3 participants