From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: "xen-devel@lists.sourceforge.net" <xen-devel@lists.sourceforge.net>
Subject: Re: dynamic libraries
Date: Wed, 23 Feb 2005 16:46:35 -0800 [thread overview]
Message-ID: <421D23EB.7090603@diku.dk> (raw)
In-Reply-To: <794420537adac1b4f01e86b86acd4ff1@cl.cam.ac.uk>
Keir Fraser wrote:
> Another option is not to bother building dynamic libraries but to
> statically link libxc and
> libxutil. Avoids versioning problems and it's not like there's some big
> sharing win to
> be had. Any strong opinions on this?
Sounds like a good idea, I have been doing similar stuff for a while, it
saves some installation/versioning headaches, though I guess the real
win here is if/when the python stuff goes away.
Jacob
-------------------------------------------------------
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_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-24 0:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 21:28 dynamic libraries Andrei Petrov
2005-02-23 23:08 ` Keir Fraser
2005-02-23 23:14 ` Adam Heath
2005-02-23 23:19 ` Keir Fraser
2005-02-23 23:26 ` Adam Heath
2005-02-23 23:43 ` Keir Fraser
2005-02-24 0:00 ` Adam Heath
2005-02-24 0:09 ` smohekey
2005-02-24 0:12 ` Adam Heath
2005-02-24 1:40 ` [Xen-devel][PATCH] " Vincent Hanquez
2005-02-24 7:33 ` Keir Fraser
2005-02-24 0:23 ` Andrei Petrov
2005-02-24 0:46 ` Jacob Gorm Hansen [this message]
2005-02-24 0:18 ` Andrei Petrov
-- strict thread matches above, loose matches on Subject: below --
2005-02-24 0:20 Charles Coffing
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=421D23EB.7090603@diku.dk \
--to=jacobg@diku.dk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.