So, we want this MacOS standalone version right? We really REALLY want it.
And I think I've made some progress towards it. I haven't arranged access to a Mac yet. But I've managed to make a standalone executable for linux using cx-freeze: http://cx-freeze.sourceforge.net/ Now, cx-freeze should also work for MacOS according to the documentation, but as I don't have access to a Mac yet, I cannot test that part.
Now, I've found out that packaging Cura is not an easy job. And it's no wonder nobody managed to do it so far. I needed to patch Skeinforge, patch my Gui code, and figure out a bunch of missing imports before it worked. I won't go into boring details, but Skeinforge really is a odd piece of code. My dependency on PyPy did not make it easier, so I'm partially to blame.
So, where are we now? Now we need to see if this script works for MacOS. If someone is feeling adventurous, then they could try. Requirements are: 1) Having Cura working on your Mac. For cx-freeze to work you need all the proper libraries up and running. 2) Install cx-freeze (will require commandline magic, and maybe even other things to install) 3) Get the latest sources from git. 4) Run "python setup.py build" in the Cura directory of the latest sources 5) If there are no errors then it should make a "frozen_build" directory containing a bunch of files including a "cura.app". This cura.app should work now. I hope.
Note, this work will not only help the MacOS version, but will also make the Linux version easier to use for the next release. And the frozen build is smaller then the windows build, so it will reduce the download size for the next Windows version I hope.
On Friday, June 1, 2012 6:32:14 AM UTC-4, Daid wrote:
> So, we want this MacOS standalone version right? We really REALLY want it.
> And I think I've made some progress towards it. I haven't arranged access > to a Mac yet. But I've managed to make a standalone executable for linux > using cx-freeze: http://cx-freeze.sourceforge.net/ > Now, cx-freeze should also work for MacOS according to the documentation, > but as I don't have access to a Mac yet, I cannot test that part.
> Now, I've found out that packaging Cura is not an easy job. And it's no > wonder nobody managed to do it so far. I needed to patch Skeinforge, patch > my Gui code, and figure out a bunch of missing imports before it worked. I > won't go into boring details, but Skeinforge really is a odd piece of code. > My dependency on PyPy did not make it easier, so I'm partially to blame.
This is an absolutely fantastic piece of news! Knowing that you are not there yet, but seeing your roadmap is very encouraging. Kliment commented earlier that he was never able to compile/package SF into an application under OS X, so I am really wishing you all the best achieving this.
I can understand that Kliment did not manage to package Skeinforge. I've already stripped out significant amounts of useless code from Skeinforge. Even then, I had to really understand what the packaging process does, and then patch a bunch of functions in Skeinforge so it worked with the changes, and I had to force the packaging to include a whole bunch of files that it did not autodetect.
On Friday, June 1, 2012 3:53:24 PM UTC+2, Joergen Geerds wrote:
> On Friday, June 1, 2012 6:32:14 AM UTC-4, Daid wrote:
>> So, we want this MacOS standalone version right? We really REALLY want it.
>> And I think I've made some progress towards it. I haven't arranged access >> to a Mac yet. But I've managed to make a standalone executable for linux >> using cx-freeze: http://cx-freeze.sourceforge.net/ >> Now, cx-freeze should also work for MacOS according to the documentation, >> but as I don't have access to a Mac yet, I cannot test that part.
>> Now, I've found out that packaging Cura is not an easy job. And it's no >> wonder nobody managed to do it so far. I needed to patch Skeinforge, patch >> my Gui code, and figure out a bunch of missing imports before it worked. I >> won't go into boring details, but Skeinforge really is a odd piece of code. >> My dependency on PyPy did not make it easier, so I'm partially to blame.
> This is an absolutely fantastic piece of news! Knowing that you are not > there yet, but seeing your roadmap is very encouraging. Kliment commented > earlier that he was never able to compile/package SF into an application > under OS X, so I am really wishing you all the best achieving this.
On Fri, Jun 1, 2012 at 6:09 PM, Daid <daid...@gmail.com> wrote:
> I can understand that Kliment did not manage to package Skeinforge. I've
> already stripped out significant amounts of useless code from Skeinforge.
> Even then, I had to really understand what the packaging process does, and
> then patch a bunch of functions in Skeinforge so it worked with the
> changes, and I had to force the packaging to include a whole bunch of files
> that it did not autodetect.
> On Friday, June 1, 2012 3:53:24 PM UTC+2, Joergen Geerds wrote:
>> On Friday, June 1, 2012 6:32:14 AM UTC-4, Daid wrote:
>>> So, we want this MacOS standalone version right? We really REALLY want
>>> it.
>>> And I think I've made some progress towards it. I haven't arranged
>>> access to a Mac yet. But I've managed to make a standalone executable for
>>> linux using cx-freeze: http://cx-freeze.sourceforge.**net/<http://cx-freeze.sourceforge.net/>
>>> Now, cx-freeze should also work for MacOS according to the
>>> documentation, but as I don't have access to a Mac yet, I cannot test that
>>> part.
>>> Now, I've found out that packaging Cura is not an easy job. And it's no
>>> wonder nobody managed to do it so far. I needed to patch Skeinforge, patch
>>> my Gui code, and figure out a bunch of missing imports before it worked. I
>>> won't go into boring details, but Skeinforge really is a odd piece of code.
>>> My dependency on PyPy did not make it easier, so I'm partially to blame.
>> This is an absolutely fantastic piece of news! Knowing that you are not
>> there yet, but seeing your roadmap is very encouraging. Kliment commented
>> earlier that he was never able to compile/package SF into an application
>> under OS X, so I am really wishing you all the best achieving this.
> --
> You received this message because you are subscribed to the Google Groups
> "Ultimaker" group.
> There are also forums, which are the official gathering place for
> Ultimaker operators:
> http://forum.ultimaker.com/
> If you still want to post to this group, send email to
> ultimaker@googlegroups.com
> To unsubscribe from this group, send email to
> ultimaker+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/ultimaker?hl=en
With OSX Lion 10.7.4 you get XCode 4.2.1, which dropped support for gcc4.2.
But this is needed for cx_freeze. So can't run the app compile step,
because cx_freeze ist not properly installed.
Via macports I've installed apple-gcc42. How can I tell the install routine
(python setup.py build,
python setup.py install) of cx-freeze, that it should use apple-gcc42
instead of the missing gcc42.
Any tipps?
Thanks
Florian
On Fri, Jun 1, 2012 at 6:26 PM, Florian Horsch <florianhor...@googlemail.com
> wrote:
> I'll give this a dedicated try later tonight.
> Stay tuned! Probably somebody with more Terminal experience than myself
> can chime in from time to time when I get stuck.
> Hope for the best!
> Flo
> On Fri, Jun 1, 2012 at 6:09 PM, Daid <daid...@gmail.com> wrote:
>> I can understand that Kliment did not manage to package Skeinforge. I've
>> already stripped out significant amounts of useless code from Skeinforge.
>> Even then, I had to really understand what the packaging process does, and
>> then patch a bunch of functions in Skeinforge so it worked with the
>> changes, and I had to force the packaging to include a whole bunch of files
>> that it did not autodetect.
>> On Friday, June 1, 2012 3:53:24 PM UTC+2, Joergen Geerds wrote:
>>> On Friday, June 1, 2012 6:32:14 AM UTC-4, Daid wrote:
>>>> So, we want this MacOS standalone version right? We really REALLY want
>>>> it.
>>>> And I think I've made some progress towards it. I haven't arranged
>>>> access to a Mac yet. But I've managed to make a standalone executable for
>>>> linux using cx-freeze: http://cx-freeze.sourceforge.**net/<http://cx-freeze.sourceforge.net/>
>>>> Now, cx-freeze should also work for MacOS according to the
>>>> documentation, but as I don't have access to a Mac yet, I cannot test that
>>>> part.
>>>> Now, I've found out that packaging Cura is not an easy job. And it's no
>>>> wonder nobody managed to do it so far. I needed to patch Skeinforge, patch
>>>> my Gui code, and figure out a bunch of missing imports before it worked. I
>>>> won't go into boring details, but Skeinforge really is a odd piece of code.
>>>> My dependency on PyPy did not make it easier, so I'm partially to blame.
>>> This is an absolutely fantastic piece of news! Knowing that you are not
>>> there yet, but seeing your roadmap is very encouraging. Kliment commented
>>> earlier that he was never able to compile/package SF into an application
>>> under OS X, so I am really wishing you all the best achieving this.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Ultimaker" group.
>> There are also forums, which are the official gathering place for
>> Ultimaker operators:
>> http://forum.ultimaker.com/
>> If you still want to post to this group, send email to
>> ultimaker@googlegroups.com
>> To unsubscribe from this group, send email to
>> ultimaker+unsubscribe@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/ultimaker?hl=en
What I've done when I needed an older version of XCode is to find the OSX install CD. It usually contains the oldest XCode that'll run on that machine.
This is not strictly regarding a standalone OS X app, but for those having difficulties installing the long way, I've installed the Cura reqs using brew and pip successfully.
brew install python --framework --universal # then set up PATH and PYTHONPATH appropriately easy_install pip # if necessary pip install PyOpenGL pip install pyserial brew install wxmac --python --devel
And you should be good to go! Works on 64-bit python (the --devel flag is necessary on wxmac, prior to the dev version wxmac is 32-bit). I don't know how to make a brew package, but it would be really nice if some day we could get the install formula down to:
On Saturday, June 2, 2012 7:20:38 AM UTC+8, Jensa wrote:
> What I've done when I needed an older version of XCode is to find the OSX > install CD. It usually contains the oldest XCode that'll run on that > machine.
Actually, since it works on 64-bit, that --universal flag probably isn't necessary. I used it because at the time I thought I was going to need 32-bit. I haven't tested the install process without it.
On Saturday, June 23, 2012 10:35:41 PM UTC+8, Mark Huetsch wrote:
> This is not strictly regarding a standalone OS X app, but for those having > difficulties installing the long way, I've installed the Cura reqs using > brew and pip successfully.
> brew install python --framework --universal > # then set up PATH and PYTHONPATH appropriately > easy_install pip # if necessary > pip install PyOpenGL > pip install pyserial > brew install wxmac --python --devel
> And you should be good to go! Works on 64-bit python (the --devel flag is > necessary on wxmac, prior to the dev version wxmac is 32-bit). I don't know > how to make a brew package, but it would be really nice if some day we > could get the install formula down to:
> brew install cura
> On Saturday, June 2, 2012 7:20:38 AM UTC+8, Jensa wrote:
>> What I've done when I needed an older version of XCode is to find the OSX >> install CD. It usually contains the oldest XCode that'll run on that >> machine.
On Saturday, June 23, 2012 10:35:41 AM UTC-4, Mark Huetsch wrote:
> This is not strictly regarding a standalone OS X app, but for those having > difficulties installing the long way, I've installed the Cura reqs using > brew and pip successfully.
putting on my hat as normal mac user, I would suggest that you go back at least 2 steps, and explain how people install brew, and what it actually is, before suggesting that this would actually help installing cura.
@Joergen: :D hold your position! i want to see the *.app, too ;)
@Daid: Erik gave your last instructions with cx_freeze a shot but couldn't
complete it before going to holidays. I could also provide you VNC access
to my MacBook Air for a couple of days. It's bored to hell anyways...
We need this app... everything else is just too hard for the normal guy.
It's quite amazing how many UM operators have a Mac.
On Sat, Jun 23, 2012 at 8:06 PM, Joergen Geerds <jgee...@gmail.com> wrote:
> On Saturday, June 23, 2012 10:35:41 AM UTC-4, Mark Huetsch wrote:
>> This is not strictly regarding a standalone OS X app, but for those
>> having difficulties installing the long way, I've installed the Cura reqs
>> using brew and pip successfully.
> putting on my hat as normal mac user, I would suggest that you go back at
> least 2 steps, and explain how people install brew, and what it actually
> is, before suggesting that this would actually help installing cura.
> --
> You received this message because you are subscribed to the Google Groups
> "Ultimaker" group.
> There are also forums, which are the official gathering place for
> Ultimaker operators:
> http://forum.ultimaker.com/
> If you still want to post to this group, send email to
> ultimaker@googlegroups.com
> To unsubscribe from this group, send email to
> ultimaker+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/ultimaker?hl=en
> putting on my hat as normal mac user, I would suggest that you go back at > least 2 steps, and explain how people install brew, and what it actually > is, before suggesting that this would actually help installing cura.
Homebrew (brew) is a commonly encountered package manager for OS X, akin to macports or fink, or apt-get on a Debian-based Linux system.
On Sunday, June 24, 2012 6:00:59 AM UTC+2, Mark Huetsch wrote:
> putting on my hat as normal mac user, I would suggest that you go back at >> least 2 steps, and explain how people install brew, and what it actually >> is, before suggesting that this would actually help installing cura.
> Homebrew (brew) is a commonly encountered package manager for OS X, akin > to macports or fink, or apt-get on a Debian-based Linux system.
On Sun, Jun 24, 2012 at 2:44 PM, Daid <daid...@gmail.com> wrote:
> I found wxWidgets the hardest to get working for MacOS (when I tried) so
> if this brew makes that a bit easier. Then that is great.
> It would also make the "build from source" steps easier, once we have a
> working build.
> @Florian: Any idea if he got cx_freeze itself to compile already? That
> might be the hardest step.
> On Sunday, June 24, 2012 6:00:59 AM UTC+2, Mark Huetsch wrote:
>> putting on my hat as normal mac user, I would suggest that you go back at
>>> least 2 steps, and explain how people install brew, and what it actually
>>> is, before suggesting that this would actually help installing cura.
>> Homebrew (brew) is a commonly encountered package manager for OS X, akin
>> to macports or fink, or apt-get on a Debian-based Linux system.
>> It does require proficiency with the command-line, so for reaching a
>> larger audience a standalone app is definitely still the way to go.
> --
> You received this message because you are subscribed to the Google Groups
> "Ultimaker" group.
> There are also forums, which are the official gathering place for
> Ultimaker operators:
> http://forum.ultimaker.com/
> If you still want to post to this group, send email to
> ultimaker@googlegroups.com
> To unsubscribe from this group, send email to
> ultimaker+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/ultimaker?hl=en
