xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com,
	samuel.thibault@ens-lyon.org
Subject: Re: [PATCH v2 2/4] tools: add pkg-config file for libxc
Date: Thu, 2 Mar 2017 13:35:54 +0100	[thread overview]
Message-ID: <bd21fb22-aab8-a269-b2c7-e9e8ba9a5ebf@suse.com> (raw)
In-Reply-To: <20170302122906.pntvanbphwk6qcsw@citrix.com>

On 02/03/17 13:29, Wei Liu wrote:
> On Thu, Mar 02, 2017 at 06:13:16AM +0100, Juergen Gross wrote:
>> When configuring the build of qemu the configure script is building
>> various test programs to determine the exact version of libxencontrol.
>>
>> Instead of a try and error approach needing updates for nearly each
>> new version of Xen just provide xencontrol.pc to be used via
>> pkg-config.
>>
>> In the end we need two different variants of that file: one for the
>> target system where eventually someone wants to build qemu, and one
>> for the local system to be used for building qemu as part of the Xen
>> build process.
>>
>> The local variant is created in a dedicated directory in order to be
>> able to collect more pkg-config files used for building tools there.
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
> 
> Please consider writing a follow-up patch to at least move
> libxenlight.pc and libxlutil.pc there, too. :-)

I'm planning to do this and more:

- add *.pc for all other Xen libraries
- add the library dependencies to the *.pc files
- use the pkg-config files for the Xen build process in order to get
  rid of the lib specific variables in tools/Rules.mk

When this has been done qemu can be switched to use pkg-config files
from Xen 4.9 on. After this (when Xen is using the enhanced qemu
version) we can drop passing the CFLAGS and LDFLAGS to qemu's
configure.


Juergen


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-03-02 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02  5:13 [PATCH v2 0/4] build enhancements related to qemu Juergen Gross
2017-03-02  5:13 ` [PATCH v2 1/4] stubdom: set xen interface version for stubdom apps using xenctrl.h Juergen Gross
2017-03-02 11:42   ` Ian Jackson
2017-03-02  5:13 ` [PATCH v2 2/4] tools: add pkg-config file for libxc Juergen Gross
2017-03-02 11:42   ` Ian Jackson
2017-03-02 12:29   ` Wei Liu
2017-03-02 12:35     ` Juergen Gross [this message]
2017-03-02 12:37       ` Wei Liu
2017-03-02  5:13 ` [PATCH v2 3/4] tools: use a dedicated build directory for qemu Juergen Gross
2017-03-02  5:13 ` [PATCH v2 4/4] tools: set pkg-config path when configuring qemu Juergen Gross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bd21fb22-aab8-a269-b2c7-e9e8ba9a5ebf@suse.com \
    --to=jgross@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).