qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Just a thought (high level API)
Date: Fri, 11 Feb 2005 17:14:16 +0100	[thread overview]
Message-ID: <pan.2005.02.11.16.14.15.602280@reply.to> (raw)
In-Reply-To: 1108136136.8032.4.camel@localhost.localdomain

Hi,

Le Fri, 11 Feb 2005 10:35:36 -0500, Nathaniel McCallum a écrit :

> On Fri, 2005-02-11 at 10:07 -0500, Jim C. Brown wrote:
>>glib is mainly a library used for portability (such as a cross platform
>>libdl interface or platform independent fixed-size types) and can be used
>>w/o having to bring in all the code used for a graphical interface.
> 
> It also provides all kind of data types (linked lists, autosizing
> vectors), error reporting (like exceptions), main loops, os independant
> threading, queues, message logging, and all kinds of other really useful
> stuff that most people just impliment in C in most projects anyway. glib
> actually has nothing to do with GTK other than the fact that several of
> the same people work on it and GTK uses glib.  glib is used in all kinds
> of other utilities and is usually part of a base linux system.  Its
> generally a dependency that most people have.  In addition, it saves a lot
> of #ifdef _WIN32 type stuff, as it is platform independant.
> 
> Nathaniel

>From my point of view having a dependancy on glib may cause much trouble
for specific build, windows one to be precise. glib introduce a few other
dependancies like libintl, libiconv and (not sure) libxml2, so even when
building in native environment you'll have to have a lot of prerequisite
to be able to build qemu.

  reply	other threads:[~2005-02-11 20:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 15:09 [Qemu-devel] Just a thought (high level API) Nathaniel McCallum
2005-02-09 15:52 ` McMullan, Jason
2005-02-10  0:02 ` Jim C. Brown
2005-02-10  1:28   ` Nathaniel McCallum
2005-02-10  2:34     ` Jim C. Brown
2005-02-10  3:47       ` Nathaniel McCallum
2005-02-10 19:59 ` Fabrice Bellard
2005-02-10 20:32   ` Nathaniel McCallum
2005-02-10 21:21     ` Fabrice Bellard
2005-02-10 22:16     ` Magnus Damm
2005-02-11 11:07     ` Jan Marten Simons
2005-02-11 12:20       ` Johannes Schindelin
2005-02-11 15:07         ` Jim C. Brown
2005-02-11 15:35           ` Nathaniel McCallum
2005-02-11 16:14             ` Ronald [this message]
2005-02-11 23:02               ` [Qemu-devel] " Nathaniel McCallum
2005-02-11 23:39                 ` [Qemu-devel] " Ronald
2005-02-11 18:27         ` [Qemu-devel] " Jan Marten Simons
2005-02-11 18:30           ` Paul Brook
2005-02-11 20:03             ` Nathaniel McCallum
2005-02-11 22:55               ` art yerkes
2005-02-11 23:04                 ` Nathaniel McCallum

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=pan.2005.02.11.16.14.15.602280@reply.to \
    --to=look@reply.to \
    --cc=daimon55@free.fr \
    --cc=qemu-devel@nongnu.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).