Nick Bastin wrote: > > I think we should actually just fix this, rather than removing locale > support for MacOS X builds. The trick is that we need to call > __setonlyClocaleconv() again, to remove the protection against calling > setlocale() in framework builds (why they did this in the first place is > beyond me). Seems like it should be an easy gate against darwin, and > then call that on startup. > I don't like that solution since that function is obviously not part of any public API. -Brett
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4