I agree with Walter, We should not bulkify the activity with gcc wrapped within it for different arch. I will look into all the possible options for installing gcc before activity is used(maybe on activity launch as suggested by walter). Also I will take into suggestions provided by Tony to make this activity lot easier and fun to use. I will also provide option for children to select appropriate library for which an option gets added during compilation/execution. Regards, Kartik Perisetla <div class="gmail_quote">On Jan 22, 2013 7:06 AM, "Walter Bender" <<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> As per Tony's suggestion, I had been discussing with Kartik about using an alert to explain that gcc is needed rather than including it in the bundle. Especially considering multiple arch., it would make the bundle too large. I don't know what the general solution is, but in the case of learning C, I don't think it is so onerous to expect some knowledge of Terminal. -walter On Mon, Jan 21, 2013 at 8:30 PM, <<a href="mailto:forster@ozonline.com.au">forster@ozonline.com.au</a>> wrote: > Thanks James > > If I understand, > > A developer makes a version of gcc that can run from ~/Activities/oopsy.activity , this is included in oopsy.xo bundle(maybe 2 versions x86 and ARM), at install time (optionally oopsy checks for the presence of gcc and if not present then) oopsy installs gcc at ~/Activities/oopsy.activity . > > There is a 30MB bloat of oopsy.xo bundle and a possible 30MB bloat of the installed Activity. > > Right? > Tony > >> On Mon, Jan 21, 2013 at 09:11:08PM +1100, <a href="mailto:forster@ozonline.com.au">forster@ozonline.com.au</a> wrote: >> > > On Mon, Jan 21, 2013 at 05:17:02PM +1100, <a href="mailto:forster@ozonline.com.au">forster@ozonline.com.au</a> wrote: >> > > > Is there any way for them to install gcc? >> > > >> > > I've had a quick look at gcc 4.7.2 sources and they appear to support >> > > the usual --prefix method of configuring, so that they might be >> > > installed in the directories of a non-root user. >> > >> > Thanks James, good news if I understand. gcc would be recompiled? >> > Still installed with yum? Can simple instructions be written that >> > beginners could follow? >> >> Yes, gcc would be compiled by the person making a Sugar activity. >> >> Yes, yum would be needed by the person making a Sugar activity, but >> not the person installing the activity. >> >> Yes, instructions can always be simplified so that beginners could >> follow, but the investment in such work might not be warranted. For >> an activity developer, the instructions can be scripted in the >> setup.py file. >> >> An activity that requires root should be clearly marked so that people >> without root won't waste their time downloading it. >> >> -- >> James Cameron >> <a href="http://quozl.linux.org.au/" target="_blank">http://quozl.linux.org.au/</a> >> _______________________________________________ >> Sugar-devel mailing list >> <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> >> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> >> >> _____________________________________________________ >> This mail has been virus scanned by Australia On Line >> see <a href="http://www.australiaonline.net.au/mailscanning" target="_blank">http://www.australiaonline.net.au/mailscanning</a> > > _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> -- Walter Bender Sugar Labs <a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a> </blockquote></div>