All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Olaf Hering <olaf@aepfle.de>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	jfehlig@suse.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] libxl: provide xenlight.pc
Date: Tue, 13 Jan 2015 14:25:38 +0000	[thread overview]
Message-ID: <1421159138.19103.84.camel@citrix.com> (raw)
In-Reply-To: <20150113125628.GK4226@zion.uk.xensource.com>

On Tue, 2015-01-13 at 12:56 +0000, Wei Liu wrote:
> On Tue, Jan 13, 2015 at 01:19:05PM +0100, Olaf Hering wrote:
> > On Tue, Jan 13, Ian Campbell wrote:
> > 
> > > On Fri, 2015-01-09 at 14:32 +0000, Wei Liu wrote:
> > > > A pkg-config file for libxl. It also contains two variables
> > > > (xenfirmwaredir and libexec_bin) so that tools that are very keen on
> > > > knowing the locations of Xen binaries (say, libvirt) can use them to
> > > > determine the location of the binaries.
> > > > 
> > > > Please rerun autogen.sh after applying this patch.
> > 
> > Forgot to reply to this earlier:
> > 
> > Should there really be another file.in.in.in.in mess? I think the
> > major/minor values could be placed into some m4 file so that they can be
> > substituted properly by configure.
> > 
> 
> I was two minded when I wrote this path. On one hand I didn't want to
> place a m4 file here, on the other I didn't want to leak library version
> numbers to top level m4 directory. Finally I decided to do the .in.in
> trick.
> 
> So if you have an argument for either of these please convince me...
> Or you have other idea about file placement please tell me.

I think the library SONAME belongs in the relevant Makefile, not hidden
in the m4 somewhere. Which I think necessitates .in.in. I think we can
live with that.

Ian.

  reply	other threads:[~2015-01-13 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 14:32 [PATCH] libxl: provide xenlight.pc Wei Liu
2015-01-13 12:11 ` Ian Campbell
2015-01-13 12:19   ` Olaf Hering
2015-01-13 12:56     ` Wei Liu
2015-01-13 14:25       ` Ian Campbell [this message]
2015-01-14 16:58   ` Ian Jackson
2015-01-15  9:33     ` Ian Campbell
2015-01-19 17:00     ` Ian Campbell

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=1421159138.19103.84.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jfehlig@suse.com \
    --cc=olaf@aepfle.de \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.