![]() ![]() (cached) /bin/sedĬhecking for grep that handles long lines and -e. i686-pc-linux-gnuĬhecking for a sed that does not truncate output. i686-pc-linux-gnuĬhecking host system type. GNUĬhecking for a sed that does not truncate output. none neededĬhecking for style of include used by make. yesĬhecking for gcc option to accept ISO C89. noĬhecking whether we are using the GNU C compiler. a.outĬhecking whether we are cross compiling. yesĬhecking for C compiler default output file name. yesĬhecking whether the C compiler works. yesĬhecking whether make supports nested variables. bin/mkdir -pĬhecking whether make sets $(MAKE). usr/bin/install -cĬhecking whether build environment is sane. and shows up in the package manager as being there.Ĭhecking for a BSD-compatible install. but it goes a long way then hangs up on colord even though it You can try update-rbos again, but I am currently building an ISO now so I can actually test it. I tend to use the SVN as my backup, in case something goes wrong where I mess up a file as a fix, so it was unstable.Įdit: I think this latest commit should be stable, unless I made a big mistake with a missing } or fi or done. It will be the first ISO that will be a true Wayland LiveCD because it doesn't use X for the login manager. I'm just trying to tweak the autologin to work correctly (which I think I'm pretty close), and the switch user dialog hopefully should work soon. I'm so close to getting the loginmanager to work. Lately, I've been pushing many commits mostly with incremental changes to one file, /usr/bin/waylandloginmanager (unless you specify it to run the compile scripts with the build option, which takes hours) Update-rbos pretty much downloads the latest files off the SVN. Seems like the last update did something bad, when I try to login it just goes back to login screen ? This is more likely, since they already have already displayed interest and some level of experience in Android, not to mention Android is already on production devices, while Wayland isn't ready for that phase quite yet.Įither way, regardless of what direction Canonical goes in, the work on RBOS is still needed and greatly appreciated. The RBOS project may be the only easy means of using Wayland on Ubuntu. If Canonical decides to a fork of Android code: ![]() Since Wayland has largely been ignored by Cannonical, they'll need to see what works and doesn't work on their own distribution and come up with solutions to things that don't work. If Canonical decides to go with their own Wayland compositor: I don't really see any alternative, but I do see points in both cases that only strengthen the need for this very project that nerdopolis is working on. ![]() ![]() Yep, kinda looks like wayland will be on the back burner unless some one gets on the stick.:pįrom what I can piece together, either Canonical will be using Wayland with their own compositor, or they'll be using some type of Android display server fork. By the looks of it they have a login manager, and some apps. I'm soon to look for some more EFL 17 and SDL 2.0 apps as I build the toolkits.Īnd wow. I have GTK apps in there, and KDE apps (although none of the KDE apps run native under Wayland, except for a few test ones that come with KDE Frameworks 5 that builds against QT5, as KDE has to port more apps to KDE Frameworks 5.) I know they don't want to enable the Wayland backend for GTK because they don't want to have unused dependencies, but why not at least have an alternate GTK package with the Wayland backend enabled? That's great!! Since the CD is KDE based, which uses Qt, do you use GTK at all? Also, any thoughts on Green Island?Īnyway, after doing a bit of reading recently, I have once again concluded that that your CD will probably be the closest thing to an official Ubuntu/Wayland incarnation for the foreseeable future, since Ubuntu is currently dependent on Compiz for Unity, and the Compiz developer Sam Spilsbury left, not that he had any intentions of porting Compiz to Wayland anyway. Now that Wayland is a stable protocol everything is more likely to compile.Īnd as far as building my Live CD goes, I overhauled the build scripts on the last week of 2012 so that I do not have to recompile everything EVERY ISO build, cutting hours of build time down to 20 minutes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |