Presuming that at its core lies a normal Debian-style system with glibc et al that just happens to run on ARM, you should be able to do it even more easily than with Android.
But then you run into Mir or whatever Canonical happens to use for a display server there, and suddenly you see that this would demand a completely new backend for gnustep-gui, or another way to display content that has nothing to do with gnustep-gui. If you want just -base, it shouldn't be hard. Please document your steps starting from a newly installed desktop operating system, and provide a sample program for Ubuntu Touch that can be used to reproduce your steps and deploy some Objective-C code to a UT-running device. Thanks :-) On 25 Dec 2013 05:07, "Patryk Laurent" <[email protected]> wrote: > > Does anyone have a sense of whether Ubuntu "Touch" (the Ubuntu for phones) > is an easily-achievable environment for building GNUStep? > > Patryk > > > On Dec 24, 2013, at 20:35, a b <[email protected]> wrote: > > looks very interesting. I hope you are able to fill in the missing parts. > > Thanks for sharing the information. > > ------------------------------ > From: [email protected] > Date: Tue, 24 Dec 2013 18:37:48 +0000 > Subject: Re: new to group, request clarifications > To: [email protected]; [email protected]; [email protected] > > On Tue Dec 24 2013 at 8:38:59 AM, Dr. H. Nikolaus Schaller < > [email protected]> wrote: > > > 3) The Droidstep thing sounded interesting. I assume it was designed to > let you > use GNUstep to write applications for Android smartphones. Too bad > it appears > to be dead. Has anyone done any experimentation in this area? Any > ideas on how > difficult it would be to do such a thing? > > > I think nobody did know about it and since there was never any source > published by the initiator nobody has > done any tests. > > Generally, since Android is Linux + some user space apps (some parts > written in C++ and apps written in Java), > you would need to develop/install at least: > > * libobj for Android > * base + GUI > * a backend that harmonizes with the frame buffer based Android graphics > (e.g. toolbar, popup menus etc,) > * find a mechanism to deploy apps not packed as .apk > > So it might be easier to install a Debian on your Android device and then > use what already exists. > > > Last time I worked on an Android one-command build script was in May 2013, > so the situation may have changed, but we need a few patches. > > See: > http://bitbucket.org/ivucica/gnustep-android > > I have not completed my work, though, so some work on this is still needed. > > I planned to play only with gnustep-make and gnustep-base, as anything > more would require writing a gnustep-gui backend and would probably not > result in very useful applications. For porting games that don't use AppKit > apart from NSOpenGLView and UIKit apart from CAEAGLLayer (or use them > minimally), and that could be transitioned to OpenGL ES easily, having at > least gnustep-base could help. > > _______________________________________________ > Discuss-gnustep mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnustep > > > _______________________________________________ > Discuss-gnustep mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnustep > >
_______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
