<div class="gmail_quote">2009/8/25 Conrad Parker <span dir="ltr"><<a href="mailto:conrad@metadecks.org">conrad@metadecks.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> 2009/8/25 cee1 <<a href="mailto:fykcee1@gmail.com">fykcee1@gmail.com</a>>:<br> <div class="im">> oil is focused on "be lightweigh in use of oil-based applications" and "be<br> > extensible in development(test) stage of oil-based applications". To achieve<br> > these, liboil is split into three modules, and glib dependence is introduced<br> > in one of these three modules -- oiltest.<br> > Module oiltest is a test framework, which is typically used to write test<br> > tools in development stage. It should be more considered to be something in<br> > the toolchain.<br> > These are big difference with liboil, so doing a fork will be necessary.<br> <br> </div>Do you intend for oil to be a drop-in replacement for liboil where it<br> is used in other free software projects? Are you intending to do that<br> kind of maintenance and integration work (ie. helping other projects<br> with the migration to modified libraries)?<br> </blockquote><div><br></div><div>The equivalent of liboil's stable API in oil is the submodule oilfuncs. Functions in oilfuncs will have the same names as their equivalent in liboil except for initialize functions.</div> <div>Currently I've filled oilfuncs with a "oil_copy8x8_u8" (see <a href="http://dev.lemote.com/files/document/oildocs/oilfuncs/index.html">http://dev.lemote.com/files/document/oildocs/oilfuncs/index.html</a>)</div> <div><br></div><div>oil is still in early stage <span class="Apple-style-span" style="font-family: arial, sans-serif; line-height: 19px; ">development, I will try to <span class="Apple-style-span" style="font-family: arial; line-height: normal; ">integrate it with some applications to see whether it works fine.</span></span></div> <div><font class="Apple-style-span" face="arial, sans-serif"><br></font></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br> The goals you have are useful, so perhaps the existing liboil<br> developers could help ensure your modifications can be used by other<br> projects. In particular, things like the hashtable optimization you<br> have could be merged incrementally.<br> <div class="im"><br> > Also, oil can cooperate with ORC. Since ORC concerns "How to generate<br> > assembly code for each arch automatically", and oil concerns "How to<br> > validate/profile these assembly code automatically".<br> <br> </div>sounds like it's an interesting branch you're working on :)<br> <font color="#888888"><br> Conrad.<br> </font><div class="im"><br> ><br> > Regards,<br> > cee1<br> > 2009/8/25 David Schleef <<a href="mailto:ds@entropywave.com">ds@entropywave.com</a>><br> >><br> >> On Mon, Aug 24, 2009 at 07:31:36PM +0800, cee1 wrote:<br> >> > Hi all,I'm doing a fork (rewrite) of liboil.<br> >><br> >> You *could* just send patches.<br> >><br> >><br> >><br> >> dave...<br> >><br> ><br> ><br> </div><div><div></div><div class="h5">> _______________________________________________<br> > Liboil mailing list<br> > <a href="mailto:Liboil@lists.freedesktop.org">Liboil@lists.freedesktop.org</a><br> > <a href="http://lists.freedesktop.org/mailman/listinfo/liboil" target="_blank">http://lists.freedesktop.org/mailman/listinfo/liboil</a><br> ><br> ><br> </div></div></blockquote></div><br>