[prev in list] [next in list] [prev in thread] [next in thread]
List: vbox-dev
Subject: Re: [vbox-dev] C++ COM Glue API
From: Sara Golemon <sara () platform ! sh>
Date: 2016-12-21 17:02:12
Message-ID: CALO+4aP7vmP-yNNF816TeetZ50WmzXhzQmt-K7vD6HS9oSpXUA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Wed, Dec 21, 2016 at 12:16 AM, Frank Mehnert <frank.mehnert@oracle.com>
wrote:
> On Dienstag, 20. Dezember 2016 10:02:17 CET Sara Golemon wrote:
> > I've been able to use the CAPI glue successfully, but as I'd prefer to
> use
> > C++, I'm hoping someone can point me to the right SDK.
>
> have a look at the VirtualBox base package tarball which you can download
> from here:
>
> https://www.virtualbox.org/wiki/Downloads
>
> The directory src/VBox/Frontends/VBoxManage contains the command line tool
> which is IMO an excellent example for a simple VirtualBox API client using
> the C++ bindings.
>
> The Downloads page refers to the binary packages as "Base Downloads", but
I infer from the path you listed that you mean the source (which I've
already cloned from SVN). That app does indeed seem to be using the C++
Glue, but it makes a number of assumptions about being built in-tree and it
doesn't look like the library is particularly reusable for third party apps.
Am I meant to copy all of include/ into my project? What parts of the
source do I need to build on various platforms to get the non-header
portions? Or are those portions all contained in VBox*.(so|dylib|dll)
shared objects in the binary distributions? I'm sure the answers are
obvious for someone working on the core of virtual box, but as an end user,
I'm left with something undocumented and terribly inobvious.
Don't get me wrong, VirtualBox seems to fit my needs quite well and I'm
super happy it's maintained and supported as an open source project, and if
the cross-platform C++ XPCOM/MSCOM part of the API just isn't ready for
prime-time, that's cool. I've actually started to build my own glue for the
narrow use-case I need and it's not that hard. I would however, recommend
either expanding that section of the PDF or just removing it entirely since
it's not actually part of the SDK.
All the best,
-Sara
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Dec 21, 2016 \
at 12:16 AM, Frank Mehnert <span dir="ltr"><<a \
href="mailto:frank.mehnert@oracle.com" \
target="_blank">frank.mehnert@oracle.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On Dienstag, 20. Dezember 2016 10:02:17 CET \
Sara Golemon wrote:<br>> I've been able to use the CAPI glue successfully, but \
as I'd prefer to use<br> > C++, I'm hoping someone can point me to the \
right SDK.<br> <br>
</span>have a look at the VirtualBox base package tarball which you can download<br>
from here:<br>
<br>
<a href="https://www.virtualbox.org/wiki/Downloads" rel="noreferrer" \
target="_blank">https://www.virtualbox.org/<wbr>wiki/Downloads</a><br> <br>
The directory src/VBox/Frontends/VBoxManage contains the command line tool<br>
which is IMO an excellent example for a simple VirtualBox API client using<br>
the C++ bindings.<br>
<br></blockquote><div>The Downloads page refers to the binary packages as "Base \
Downloads", but I infer from the path you listed that you mean the source (which \
I've already cloned from SVN). That app does indeed seem to be using the C++ \
Glue, but it makes a number of assumptions about being built in-tree and it \
doesn't look like the library is particularly reusable for third party \
apps.<br><br>Am I meant to copy all of include/ into my project? What parts of the \
source do I need to build on various platforms to get the non-header portions? Or \
are those portions all contained in VBox*.(so|dylib|dll) shared objects in the binary \
distributions? I'm sure the answers are obvious for someone working on the core \
of virtual box, but as an end user, I'm left with something undocumented and \
terribly inobvious.<br><br>Don't get me wrong, VirtualBox seems to fit my needs \
quite well and I'm super happy it's maintained and supported as an open \
source project, and if the cross-platform C++ XPCOM/MSCOM part of the API just \
isn't ready for prime-time, that's cool. I've actually started to build \
my own glue for the narrow use-case I need and it's not that hard. I would \
however, recommend either expanding that section of the PDF or just removing it \
entirely since it's not actually part of the SDK.<br><br>All the \
best,<br>-Sara</div></div></div></div>
_______________________________________________
vbox-dev mailing list
vbox-dev@virtualbox.org
https://www.virtualbox.org/mailman/listinfo/vbox-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic