Bug #58597 | CMake does not set -DWITH_EXTRA_CHARSETS=complex for mysql_release | ||
---|---|---|---|
Submitted: | 30 Nov 2010 16:21 | Modified: | 14 Jan 2011 18:23 |
Reporter: | Paul DuBois | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.5+ | OS: | Any |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
[30 Nov 2010 16:21]
Paul DuBois
[30 Nov 2010 21:05]
Sveta Smirnova
Thank you for the report. Verified as described.
[7 Dec 2010 0:11]
Omer Barnir
triage: setting tag to SR55MRU (do be done in the lifetime of 5.5)
[13 Jan 2011 13:47]
Vladislav Vaintroub
5.1 manual was wrong in this regard. On Windows, all charsets were always compiled in, and "all" is more than "complex".
[13 Jan 2011 14:37]
Paul DuBois
What is the default behavior supposed to be for CMake? Do we have a bug here?
[13 Jan 2011 14:45]
Paul DuBois
Build team: Is Wlad's comment of [13 Jan 14:47] also true for 5.0?
[13 Jan 2011 21:21]
Vladislav Vaintroub
Paul, on Windows all charsets were always compiled in, also in 5.0. There was no way to restrict charsets. I thought default=all is hence a good default, couple of extra charsets will not not hurt, right?
[14 Jan 2011 18:22]
Paul DuBois
I am recategorizing this as a docs bug and updating the page in question to note that Windows binaries before 5.5 are configured with "=all", and all binaries in 5.5 are configured with "=a".
[14 Jan 2011 18:23]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.