Porting to python3
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: Porting to python3
may be a Py2 Py3 problem ? https://forum.freecadweb.org/viewtopic.php?f=38&t=29236
Re: Porting to python3
the bundled conda-packages for FreeCAD are huge.triplus wrote:To be honest it's working out without the mentioned feature being available. Sure. It would be great to have that in the future. But highly likely we aren't talking about a deal breaker.
docs? Yes absolutely necessary, but first I need to work on the "never ending todo list".triplus wrote:I see. Adding the Conda instructions here would therefore make some sense?
+1triplus wrote:P.S. We could i guess be more aggressive and flip the Py3 flags on for Trusty builds. And let that propagate to AppImage. If we decide and do that Py3 related reports will for sure start to come after.
Re: Porting to python3
I also need to set boost-python
https://forum.freecadweb.org/viewtopic. ... 50#p178969
Git needs to be available only when Cmake is run.
I was/am working on an update scheme with my builds using Conda as a dependency package manager
https://forum.freecadweb.org/viewtopic.php?f=4&t=27514
There is a package available on the releases page https://forum.freecadweb.org/viewtopic.php?f=4&t=27514
There are no recent updates because I am having trouble compiling, right now my problem is with pybind11 in CMake.
I can build an 14.04 x86_64 on my PPA https://launchpad.net/~clhclh/+archive/ ... /+packages
But this breaks the i386 build.
"fight the good fight"
Re: Porting to python3
hmm somehow, I removed this dependency. I guess this was the problem. Hopefully the next build will be fixed.sgrogan wrote:Git needs to be available only when Cmake is run.
Can you post the error? For conda I am using now external smesh and pybind11 as new dependencies. Both are available from conda-forge channel. Also there is a bug in cmake 3.11 so better use 3.10.sgrogan wrote: There are no recent updates because I am having trouble compiling, right now my problem is with pybind11 in CMake.
Re: Porting to python3
And how much extra work does that come down to on your side (PPA maintenance)? That is if we decide and try to reuse it to provide additional daily Py3 and 64-bit oriented AppImage from it?sgrogan wrote: ↑Mon Jun 11, 2018 9:14 pm I can build an 14.04 x86_64 on my PPA https://launchpad.net/~clhclh/+archive/ ... /+packages
But this breaks the i386 build.
Re: Porting to python3
@sgrogan Question: What about creating an appImage that is Py3/Qt5 enabled and that way folks could quickly test without needing to compile themselves?
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Re: Porting to python3
Qt5 on Trusty is too old to be useful. And there is no PySide2 in the repositories.
Re: Porting to python3
Not much at all for 14.04 x86_64
I think it's a start.
My goal is a FreeCAD-testing FreeCAD PPA where we can work on the PY3/QT5/External SMSH ports. A lot will depend on Kurt's GSoC work.
Maybe you could try the package in a 14.04 virtual machine? If you have the time. There is still work to do, but I think it is worth it.
I can't even do a QT5 build locally yet, so this will take some time. we're gonna have to package a bunch of stuff on the PPA to get QT5 working for all the supported releases. Again Kurt's work will be foundational.
"fight the good fight"
Re: Porting to python3
OK then i will try to create an AppImage from it (likely tomorrow) and see how that goes. Maybe i will take a look in the delta updates possibility (if it won't turn out to be too complex).