[Pythonocc-users] First release of software that depends on PythonOCC

2014-03-06 Thread Kene Meniru
This is an announcement for buildes BIM located at http://sourceforge.net/projects/buildes/?source=navbar. This system is being created to assist designers in the building design and documentation process. I just succeeded in packaging it for the first time for a source only release! It is programm

Re: [Pythonocc-users] First release of software that depends on PythonOCC

2014-03-06 Thread jelle feringa
Hi Kene, Congratulations, that's quite an achievement! And excited to see more BIM / IFC related efforts. Wrt to issue of packaging, I've read your post on the pyinstaller forum with interest. Including a hook for distributing PythonOCC apps with pyinstaller is a good idea. What about generalizin

Re: [Pythonocc-users] First release of software that depends on PythonOCC

2014-03-06 Thread Kene Meniru
jelle feringa writes: > > > Hi Kene, > Congratulations, that's quite an achievement! > And excited to see more BIM / IFC related efforts. > > Wrt to issue of packaging, I've read your post on the pyinstaller forum with interest. > Including a hook for distributing PythonOCC apps with pyinstall

Re: [Pythonocc-users] First release of software that depends on PythonOCC

2014-03-06 Thread jelle feringa
> Sorry but I am totally clueless on what you mean by 'generalizing the > PythonOCC hook'. Gives me hope for perhaps a solution but please explain > more. Thanks. > For instance, the kivy project provides a "hook-kivy.py" [1] which makes including kivy in applications distributed with pyinstaller

Re: [Pythonocc-users] First release of software that depends on PythonOCC

2014-03-06 Thread Kene Meniru
jelle feringa writes: > For instance, the kivy project provides a "hook-kivy.py" [1] which makes > including kivy in applications distributed with pyinstaller very, very > easy [2] > > It would be great if we can provide something similar in PythonOCC as > well ( IMHO pyinstaller is the best w