I tried to bump to 0.18, but it does not build as is. I get som errors with "error: external linkage required for symbol" ...
2017-02-23 21:33 GMT+01:00 Cirilo Bernardo <cirilo.berna...@gmail.com>: > On Fri, Feb 24, 2017 at 2:08 AM, Nick Østergaard <oe.n...@gmail.com> wrote: >> 2017-02-23 14:53 GMT+01:00 Wayne Stambaugh <stambau...@gmail.com>: >>> On 2/22/2017 10:01 PM, Cirilo Bernardo wrote: >>>> Hi folks, >>>> >>>> I was looking into non-ASCII characters in file paths under Windows >>>> in hopes of at least fixing latent bugs in non-MCAD 3D plugins and >>>> IDF/VRML exports. Unfortunately the problem has proved much more >>>> difficult than I originally imagined. >>>> >>>> In MSVC, objects like std::fstream have an overloaded open() function >>>> which takes wchar_t and does the right thing. Since that overload is >>>> not part of the STL specification, it is not available in MSys2. >>>> >>>> It looks to me that the best path at the moment is to use some form >>>> of wxStream in place of std::ifstream/std::ofstream; however I would >>>> need to make some small test programs to verify that wxStream >>>> does the right thing; I suspect it does since richio does not demonstrate >>>> a non-ascii path problem. >>>> >>>> Features currently affected by non-ascii path problems include: >>>> 1. STEP export (won't be fixed until appropriate newer versions of >>>> OpenCascade or OCE are installed) >>> >>> I guess we will have to wait until newer versions of oce are packaged to >>> get this fix. Hopefully they will be readily available before the >>> stable 5 release so we don't have this bug in our stable release. >> >> Will OCE 0.18 fix the issue? >> > > OCE 0.18 uses OpenCascade 6.9 and the issue was supposedly fixed in > OpenCascade 6.8. I'm attempting to build OCE 0.18 to test this and I'll > post an update. > > - Cirilo > >>> >>>> 2. IDF and OCE 3D plugins (VRML plugins use richio and are not >>>> affected) >>>> 3. IDF export >>>> 4. All IDF command-line tools >>>> 5. VRML export >>>> >>>> Any comments/suggestions? Should I add this job to my list of things >>>> to do or do we just wait and hope this is all magically fixed within >>>> MSys2/Windows API? >>> >>> Please add this to your list of things to do. I don't think waiting for >>> msys2/windows api is wise. I'm fine with fixing the one at at a time if >>> you don't have time to get to it all at once. Thanks for looking into this. >>> >>> Cheers, >>> >>> Wayne >>> >>>> >>>> - Cirilo >>>> >>>> _______________________________________________ >>>> Mailing list: https://launchpad.net/~kicad-developers >>>> Post to : kicad-developers@lists.launchpad.net >>>> Unsubscribe : https://launchpad.net/~kicad-developers >>>> More help : https://help.launchpad.net/ListHelp >>>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : kicad-developers@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
