Hi Seth, I think it would be good if someone could check that everything works OK on Windows with non-ascii characters in the path. At the time I created the support for STEP a patch (an awful hack really) was needed for OCE and OCC just didn't work. I think OCC fixed the issues a few years later but I'm not 100% sure. There is also a possibility that a natively built OCC works fine but one built within MinGW won't be able to handle non-ASCII characters in paths.
Cirilo On Thu, Oct 14, 2021 at 4:07 AM Seth Hillbrand <s...@kipro-pcb.com> wrote: > Hi Folks- > > After a transition period, we are officially dropping support for the > OpenCascade Community Edition (OCE) fork. The official OpenCascade > releases (libocct for most *nix distros) fix a number of bugs in 3d model > loading and export. > > The effect of this in KiCad is that we are dropping the build flag > KICAD_USE_OCE. Developers should change their builds (if they haven't > already) to the flag KICAD_USE_OCC, which has been the default for the past > couple of months. > > Let us know if you have any questions or concerns. > > Seth > > -- > [image: KiCad Services Corporation Logo] > Seth Hillbrand > *Lead Developer* > +1-530-302-5483 > Long Beach, CA > www.kipro-pcb.com i...@kipro-pcb.com > _______________________________________________ > 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