[libvirt] Re: remote_protocol.{c,h} ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 3, 2008 at 1:00 PM, Jun Koi <junkoi2004@xxxxxxxxx> wrote:
> Hi,
>
> Is it really true that qemud/remote_protocol.{c,h} are created by
> rpcgen? If so, why dont we have them created at compile time? I still
> see them in the source code.
>
> I modified remote_protocol.x a bit, and when recompiling,
> remote_protocol.{c,h} are not reflected at all. So it is expected that
> developers must recompile with rpcgen themself??

I looked again, and see that we can generate remote_protocol.c from
rpcgen. Currently it seems remote_protocol.c is hacked a bit to remove
some unused stack variables? Why do we need to do such a thing, while
compiler can optimize that for us?

So I guess it is better to have rpcgen does all the job, and leave
everything as it is. We can rename remote_protocol_xdr.c to
remote_protocol.c if you still insist that (but I see no good reason
to do so).

Thanks,
Jun

--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]