-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Conversation
Hi, I've tried to install your version of anbox on archlinux too, and I've come across this error:
But then i adjusted this by editing the dbus-cpp line in CMakeList to dbus-c++-1, but it blocked at this:
I have installed gmock, and at /usr/src/gmock there is indeed no CMakeLists.txt file, but this error didn't come up with the normal version of anbox. |
That's strage - commit 1b6982e should make sure you don't need a globally installed dbus-cpp. You still need to checkout the source code of googletest and point the GMOCK_SOURCE_DIR variable to the correct path. One could include that as submodule, too, though. |
Google-test is now included as submodule; building is for me on archlinux nothing more than:
|
After installing lxc, boost, doxygen, and lcov, I'm now getting
|
You need the package lsb-release. |
That worked, but now a new issue What filesystem are you using? I'm getting an error under btrfs when creating |
Uh, quite strange - also btrfs. Note to myself due the failed check: It seems as if the gmock>est libs are not linked. |
Debian Stretch x64. CMake Error at /usr/share/cmake-3.7/Modules/FindPackageHandleStandardArgs.cmake:138 (message): And I do have libxml2 installed via apt-get. |
On Archlinux, I can compile by disabling tests and installing dbus-cpp from AUR. After that if I run /usr/local/bin/anbox container-manager --data-path=/var/lib/anbox/ --android-image=android.img.path as root and in another terminal Getting Also running scripts/start-container.sh lxc-start: log.c: log_open: 300 failed to open log file "/var/lib/anbox/containers/default/default.log" : Permission denied |
I did as pival81 and then this..
And it was able to build. I don't know but I noticed a CMakeList.txt in the Make gave me this however..
|
I was able to build and install 'anbox-git' (from AUR) if I changed the CMakeList.txt as I did above. I had to do it on 'process-cpp' (from AUR) too. |
so, installing from anbox-git aur package, do i have to download the android image too? if so, from where? I did get it installed but i'm not sure how to get it working due to the kernel modules being missing. How do i get that to work? |
@Mufeed20: |
to fetch android-image: |
Installing libxml2-dev allowed me to fully CMake.
Is there a way to get anbox to check for |
Can I ask your help guys? [EE 2017-04-13 16:41:24] [session_manager.cpp:119@operator()] Failed to start as either binder or ashmem kernel drivers are not loaded Does anybody else got the same problem ? |
@Tekercs dkms status (do you see the drivers) |
@oleid Thanks for these changes! I don't really like the use of submodules as they are nasty and hard to work with. If this is just to make packaging easier you can fetch dbus-cpp within you PKGBUILD instead. Mid term we may move away from dbus-cpp to use something which more widely available on other distributions. For google-test we could add an option first which disables building tests for you. I wonder why google-test isn't available on Arch. If it is not then someone should really package it as its a common thing widely used in many other software projects. A lot of these changes were also already merged with #44 Can you merge with master or rebase? Also the CI fails on this PR. |
@morphis google-test is available in Arch in AUR under the name 'gtest'.. |
Thanks guys! I managed to run everything is "fine" except the session manager keeps spaming the stdout with the following message: A but laggy but works, sometimes kills the KDE desktop. |
On Debian Stretch 64-bit, had to run:
before |
FYI: I just realized, that binder and anshmem are in upstream kernel sources, however not enabled by default. I just build linux-git with:
and it's running just fine :) |
@oleid What is the status of this? There are a few useful things in here which we want to integrate. However the submodules are not. Can you clean this PR so we can do a proper PR and get the other bits merged? |
Any news here? Otherwise I would like to close this PR. |
So pity there's no one to work on this, being Ubuntu-only is... weird. |
As we're delivering a snap, Anbox can run theoretically run everyhwere. So this isn't a big problem. Anyone who wants to improve the build situation on other distributions is welcome to contribute. |
@morphis of course, it's not a complain towards mainainters in any way, I believe this will get momentum and we'll see flatpak/e.t.c. from volunteers. |
Anbox cannot run everywhere. You are relying on kernel modules that are currently only installed by default on Ubuntu. If you wanted to run everywhere, you'd find a way to either install them during the snap deploy, or you'd use a non-Ubuntu base for development. |
Interested in contributing packaging bits for other distributions? Snaps are running fine on Fedora, openSUSE, Debian etc. these days and so does Anbox when the kernel modules are loaded. The only last bit which is missing to have the snap working well on these distributions is a official DKMS package we can ship through obs/copr/... As soon as somebody contributes a RPM spec file for this we can setup an official Anbox repository for this and use it inside the anbox-installer. If you're interested, please help to get this solved. I as a maintainer don't have the time to care about more than a single distribution. The free time I have for this doesn't permit much more. |
As I said, I am fine with Anbox being packaged in any other packaging format. However I personally will only focus on snaps. If you don't want to use snaps (and snaps are a cross-platform effort and not specific to Ubuntu, see https://snapcraft.io/), you're fine to use whatever you want. Changes to compile outside of Ubuntu are welcome but I don't have the time to test anything else at the moment. Changes to improve the CI to test PRs against other distributions and compile elsewhere are very welcome. |
That's great...but your code isn't. |
It's all open source so you're more than welcome to improve support for any other distribution which isn't well supported yet. |
@morphis Good Morning, I see that you work on anbox for SailfishOS port, if you want want I can help in test. write to me if you want to share you currently work. |
I'm in the midst of packaging this for Gentoo systems without the dreaded Can somebody with better knowledge of this project (perhaps @morphis) explain the Finally, some people in this thread have suggested using the more widely available |
Reading the source of dbus-cpp, it seems as it has no dependency on any C implementation of dbus. It's stand-alone, as you might say. But what does this have to do with the dreaded systemd init system, as you call it? |
Note: This branch is not to be merged at the moment. I merely want to share my progress of experimentation on a place others can find it easily.
This is what I need to be able to compile anbox on ArchLinux.
dbus-cpp and friends are not available there, hence I prepared dbus-cpp and properties-cpp as submodules (branches submodule) and added them to the project. Also, a few changes to -Werror and friends are included to actually build the submodules.
Since sailfish-os doesn't provide dbus-cpp and friends, too - AFAIK - it's probably of use there, too.
EDIT:
Google-test is now included as submodule; building is for me on archlinux nothing more than: