| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] [PATCH] libxen-3.0 (libxc rewrite)
> I've been doing a lot of work on libxc. I've got it to the
> point that
> I'm ready to share. Below are the major changes. Feedback
> is greatly
> appreciated, especially with respect to things that would be required
> for it to be integrated into the xen-unstable tree.
>
> o Rename libxc => libxen
> o Use pkg-config to control versioning and parallel installs
> o Use autoconf to detect dependencies, provide separate build
> directory, cross-compile
> o Use doxygen to autogenerate HTML documentation
> o Organize hypercalls by groups in separate headers (dom.h,
> evtchn.h,
> etc.).
> o Provide consistent error semantics for all functions (-errno is
> returned on error).
> o Use pyrex to autogenerate python bindings
> o Provide high-level python interface (Xen() and Domain() classes
> instead of direct hypercalls)
Is there a good place to get pyrexc from? I couldn't obviously spot an
RPM in FC2 or FC3.
I've built the C stuff and will look through it. There are a bunch of
semantic changes we want to make to the dom0 op interface (SMP and misc
cleanups, finer grained access control etc), but it might make sense to
integrate your stuff first.
Do you reckon you could get xend and friends building against the pyrex
wrapped libraries?
Ian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
|
|
| |
|
Home