See overview here:
And their new home page:
The project borrows a lot of code from Ubuntu Touch, apparently, but uses Wayland instead of Mir. Wayland already has some history on phones, as I think Sailfish OS uses it.
Plasma Mobile is intended to run many apps, including Android, Ubuntu Touch, and yes, even GTK apps.
1 Comment I have modified my Quirky build system, also known as woofQ, to optionally merge the 'devx' into the main filesystem.
That is, there will no longer be a devx PET as all of the files needed for compiling, git, svn, etc., are already in the main build of Quirky.
For me, this is convenient, as I always install the 'devx' PET anyway. Now, the proposed "Appril" app-developer build of Quirky is up-front for developing Linux and Android applications, so I want everything built-in ready-to-go out-of-the-box.
woofQ has a file 'build-choices', with a new variable BUILD_CHOICE_MERGE_DEVX, which, when set to "yes', will cause the merge to occur.
This required modifications to '2createpackages' and '3builddistro'.
The proposed "Appril" build is looking good. It is going to be big though, very big.
No comments As I am planning to include QtCreator in my proposed "developers April" -- "Appril" (cringe) -- I have compiled Qt 5.5.0.
I had attempted this recently, and failed. This time, persisted, and got there. A bit of a saga.
Right now, I am doing what I hope is the final compile, with this configuration:
# ./configure -android-sdk /root/Android/Sdk -gstreamer 1.0 -no-directfb -no-pulseaudio -L /usr/X11R7/lib -I /usr/X11R7/include -no-sse2 -no-sse3 -no-ssse3 -no-sse4.1 -no-sse4.2 -system-sqlite -opensource -confirm-license -prefix /usr -sysconfdir /etc/xdg -nomake examples -R /usr/X11R7/lib -qt-xcb -dbus-linked -examplesdir /usr/share/doc/qt5/examples -datadir /usr/share/qt5 -archdatadir /usr/share/qt5 -libexecdir /usr/libexec -headerdir /usr/include/qt5 -docdir /usr/share/doc/qt5 -system-harfbuzz -skip qtwebengine
There were fun and games getting to this point, of a successful compile! Here are some notes:
This is the version in Quirky April, which is good, as Qt wants v2.7. However, Qt compile fails, reporting something wrong with Python. I googled around, and found that Python configuration checks something in a running kernel and configures the build appropriately -- well, my Python is compiled in T2, and this environment builds Python wrong, at least as far as Qt is concerned.
So, I compiled Python in Quirky April:
patches from t2:
# patch -p1 < ../dont-force-rebuild-all.patch
# patch -p1 < ../fix_readline.patch
# patch -p1 < ../python-setup.patch
# LDFLAGS='-L /usr/X11R7/lib' CPPFLAGS='-I /usr/X11R7/include' CFLAGS='-I /usr/X11R7/include' ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-pc-linux-gnu --with-system-ffi --with-system-expat --enable-shared --with-threads --enable-ipv6
Peculiar, but "make install" did not install libpci.so and libpci.pc in the T2 build. They have to be installed manually. This caused a Qt compile fail. This should be fixed in T2, but anyway, I fixed it manually, and ploughed on.
After compiling for hours, Qt build failed, in the "qtwebengine" module, a dbus-related bug. I googled, could not find a patch to fix it, however, Linux From Scratch have simply avoided the problem, with configure option "-skip qtwebengine". So I did that too, and got a successful compile.
Installing Qt5 into /usr, get some things going into odd places, so following guidance at Linux From Scratch, I have added some explicit paths. Recompiling now!
3Comments Just a quick report. I posted about AI2 here:
I have compiled AI2 from source, and successfully run it locally. That is, I can start the local server and point the browser at it, and develop apps.
I have not yet tested connecting a phone.
This is happening in Quirky April. I plan to create PETs and build a special developers edition of Quirky, for creating apps. At first, the target will be for Android.
Starting AI2 should be as simple as selecting it from the menu. Lots of fun, but it is getting on to 1am here. have to sleep!
2Comments I have made the JDK7 and Android Studio into PETs.
Android Studio (246.2M):
These should work on all pups, not just Quirky. They run on a 32-bit distro, or a 64-bit with 32-bit libs.
Installation is into /opt/android. A menu entry is created in the Utilities category, to run Android Studio.
I might not do it this way in future, instead might just create a download script to fetch them (that is, not have PETs).
I also created a PET for the Android NDK, but it is 901MB, so backed off.
Pages:      ...