[prev in list] [next in list] [prev in thread] [next in thread]
List: olpc-sugar
Subject: Re: [Sugar-devel] Porting task - Can we use Mac OS and Virtual Box ?
From: James Simmons <nicestep () gmail ! com>
Date: 2019-12-18 22:24:04
Message-ID: CAN6VRWzFg66u8=3DC-PALPwkemLFBAJ=MpS8Bt43YSoSSi3i=A () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Abhay,
The Floss manual for *Make Your Own Sugar Activities!* is a bit out of
date, but does have some thoughts on setting up a development environment,
including using Virtual Box:
http://write.flossmanuals.net/make-your-own-sugar-activities/setting-up-a-development-environment/
It also recommends what I do, which is to get a cheap reconditioned
computer and put Linux on that. It doesn't take much hardware to develop
Sugar activities. There are also suggestions for development tools.
James Simmons
On Wed, Dec 18, 2019 at 1:43 PM James Cameron <quozl@laptop.org> wrote:
> G'day,
>
> Thanks for asking. Your scenario is familiar. Yes, in your situation
> you must use a virtualisation software, such as Parallels, vmWare, or
> VirtualBox.
>
> Then, for our Port to Python 3 tasks, the only viable choice is to
> install our Sugar Live Build into a virtual machine.
>
> You can iterate through this until comfortable;
>
> 1. install the first or next virtualisation software; most of us
> would use VirtualBox, but there are other choices,
>
> 2. create a virtual machine, connect the virtual CD drive to the
> ISO9660 image of Sugar Live Build, and start the virtual machine,
>
> 3. at the prompt, select the default, and this will run the guest
> operating system in a way that does not make any permanent change to
> the virtual machine disk; then test the features of Sugar as you will
> find in our documentation https://help.sugarlabs.org/ ... when this is
> complete just turn off the virtual machine.
>
> 4. start the virtual machine again with the Sugar Live Build image,
> and this time select an installation option, then go through the
> guided installation process, and when it is complete eject the virtual
> CD and reboot; this will run the guest operating system from a virtual
> disk, and any changes you make are kept. To restart this step, you
> can just turn off the virtual machine.
>
> 5. install an integrated development environment on your macOS
> system, one that supports Python and editing over SSH. (I don't have
> any specific recommendations, and can't suggest you use what I use,
> because of the extra knowledge required to use it. emacs and magit.)
>
> 6. set up inbound SSH on the virtual machine, e.g. sudo apt install
> openssh-server,
>
> 7. connect from a macOS Terminal to the virtual machine using SSH, to
> test, and for any system administration,
>
> 8. clone sources on the virtual machine using git, test the activity
> on the virtual machine, then edit the sources over SSH using your IDE,
> test the modified activity on the virtual machine, and commit the
> changes, etc, as per the usual GitHub workflow.
>
> Hope that helps!
>
> On Wed, Dec 18, 2019 at 05:48:44PM +0530, Abhay Malik wrote:
> > Hey,
> > After quite some time, I found out sugar runs on a different
> operating system fedora, initially to run on my Mac book air I used virtual
> box to run sugar desktop. I am successfully able to run sugar on a stick on
> my Mac.
> >
> > I asked my mom wether I can install fedora on my Mac but she said I
> can't :(
> >
> > Also It looks hard to install a different OS.
> >
> > Is there any other specific way of trying out a sugar activity from a
> code locally on my Mac machine using Mac OS and virtual box?
> >
> >
> > Thanks,
> > Abhay
> > _______________________________________________
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
> --
> James Cameron
> http://quozl.netrek.org/
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
[Attachment #5 (text/html)]
<div dir="ltr">Abhay,<div><br></div><div>The Floss manual for <i>Make Your Own Sugar \
Activities!</i> is a bit out of date, but does have some thoughts on setting up a \
development environment, including using Virtual Box:</div><div><br></div><div><a \
href="http://write.flossmanuals.net/make-your-own-sugar-activities/setting-up-a-develo \
pment-environment/">http://write.flossmanuals.net/make-your-own-sugar-activities/setting-up-a-development-environment/</a> \
</div><div><br></div><div>It also recommends what I do, which is to get a cheap \
reconditioned computer and put Linux on that. It doesn't take much hardware to \
develop Sugar activities. There are also suggestions for development \
tools.<br></div><div><br></div><div>James Simmons</div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 18, 2019 at 1:43 PM \
James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">G'day,<br> <br>
Thanks for asking. Your scenario is familiar. Yes, in your situation<br>
you must use a virtualisation software, such as Parallels, vmWare, or<br>
VirtualBox.<br>
<br>
Then, for our Port to Python 3 tasks, the only viable choice is to<br>
install our Sugar Live Build into a virtual machine.<br>
<br>
You can iterate through this until comfortable;<br>
<br>
1. install the first or next virtualisation software; most of us<br>
would use VirtualBox, but there are other choices,<br>
<br>
2. create a virtual machine, connect the virtual CD drive to the<br>
ISO9660 image of Sugar Live Build, and start the virtual machine,<br>
<br>
3. at the prompt, select the default, and this will run the guest<br>
operating system in a way that does not make any permanent change to<br>
the virtual machine disk; then test the features of Sugar as you will<br>
find in our documentation <a href="https://help.sugarlabs.org/" rel="noreferrer" \
target="_blank">https://help.sugarlabs.org/</a> ... when this is<br> complete just \
turn off the virtual machine.<br> <br>
4. start the virtual machine again with the Sugar Live Build image,<br>
and this time select an installation option, then go through the<br>
guided installation process, and when it is complete eject the virtual<br>
CD and reboot; this will run the guest operating system from a virtual<br>
disk, and any changes you make are kept. To restart this step, you<br>
can just turn off the virtual machine.<br>
<br>
5. install an integrated development environment on your macOS<br>
system, one that supports Python and editing over SSH. (I don't have<br>
any specific recommendations, and can't suggest you use what I use,<br>
because of the extra knowledge required to use it. emacs and magit.)<br>
<br>
6. set up inbound SSH on the virtual machine, e.g. sudo apt install<br>
openssh-server,<br>
<br>
7. connect from a macOS Terminal to the virtual machine using SSH, to<br>
test, and for any system administration,<br>
<br>
8. clone sources on the virtual machine using git, test the activity<br>
on the virtual machine, then edit the sources over SSH using your IDE,<br>
test the modified activity on the virtual machine, and commit the<br>
changes, etc, as per the usual GitHub workflow.<br>
<br>
Hope that helps!<br>
<br>
On Wed, Dec 18, 2019 at 05:48:44PM +0530, Abhay Malik wrote:<br>
> Hey,<br>
> After quite some time, I found out sugar runs on a different operating \
system fedora, initially to run on my Mac book air I used virtual box to run sugar \
desktop. I am successfully able to run sugar on a stick on my Mac.<br> > <br>
> I asked my mom wether I can install fedora on my Mac but she said I can't \
:(<br> > <br>
> Also It looks hard to install a different OS.<br>
> <br>
> Is there any other specific way of trying out a sugar activity from a code \
locally on my Mac machine using Mac OS and virtual box?<br> > <br>
> <br>
> Thanks,<br>
> Abhay<br>
> _______________________________________________<br>
> Sugar-devel mailing list<br>
> <a href="mailto:Sugar-devel@lists.sugarlabs.org" \
target="_blank">Sugar-devel@lists.sugarlabs.org</a><br> > <a \
href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" \
target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> <br>
-- <br>
James Cameron<br>
<a href="http://quozl.netrek.org/" rel="noreferrer" \
target="_blank">http://quozl.netrek.org/</a><br> \
_______________________________________________<br> Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" \
target="_blank">Sugar-devel@lists.sugarlabs.org</a><br> <a \
href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" \
target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> \
</blockquote></div>
[Attachment #6 (text/plain)]
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic