virtualbox is perfectly usable without the qt interface, via VBoxManage and VBoxSDL. With the diff posted below the gui is only built if the qt use flag is active, but it could be easily changed so that the gui is always built unless an local use variable is used (disable_qt_gui, or something like that). Reproducible: Always
Created attachment 151231 [details, diff] diff for virtualbox-1.5.6.ebuild
The USE flag should be "qt3" instead.
(In reply to comment #0) > virtualbox is perfectly usable without the qt interface, via VBoxManage and > VBoxSDL. With the diff posted below the gui is only built if the qt use flag is > active, but it could be easily changed so that the gui is always built unless > an local use variable is used (disable_qt_gui, or something like that). Hi, the --enable-qt / --disable-qt switch is not recognized by the VirtualBox build system, the only way to totally disable the build of the (qt) graphic frontend is to use the --build-headless switch a version bump of VirtualBox 1.6.0 is available on jokey's overlay[1] with this new use flag implemented. [1] http://overlays.gentoo.org/dev/jokey/browser/trunk
(In reply to comment #3) > the --enable-qt / --disable-qt switch is not recognized by the VirtualBox > build system, the only way to totally disable the build of the (qt) graphic > frontend is to use the --build-headless switch Maybe in 1.6.0. In 1.5.6: $ grep -A 2 disable-qt configure --disable-qt) WITH_QT=0 ;; And I assure you, it works; I don't have any VirtualBox executable or qt libraries in my system :) Of course there is a disable-headless too, but that also disables SDL: $ grep -A 5 build-headless configure --build-headless) HEADLESS=1 WITH_SDL=0 WITH_SDL_TTF=0 WITH_X11=0 WITH_QT=0 So NO frontend is built (i.e., it makes it quite useless).
Seems this was overlooked during last version bump round Fixed now :)
