qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: quintela@redhat.com
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] [RFC PATCH 0/6] Generate config_h from config.mak
Date: Wed, 15 Jul 2009 17:26:28 +0200	[thread overview]
Message-ID: <cover.1247670419.git.quintela@redhat.com> (raw)

From: Juan Quintela <quintela@redhat.com>

Hi

This patches apply on top of my previous series.
I generate $target_dir/config.h from $target_dir/config.mak

ToDo:
- generate config-host.h from config-host.mak
- USE_NPTL -> can I rename it to CONFIG_USE_NPTL?
- TARGET_ABI_MIPS{O32,N32,N64}.  Rest of architectures use names like:
  TARGET_ABI_MIPSN32 -> TARGET_MIPSN32
  TARGET_ABI_MIPSN64 -> TARGET_MIPSN64
  not sure how to do the TARGET_ABI_MIPSO32
  This one is only to have coherent options names, rest of architectures have
  enough with TARGET_ARCH, TARGET_ARCH2, TARGET_BASE_ARCH, TARGET_$ARCH_NAME
  TARGET_$BASE_ARCH_NAME

- TARGET_ARCH2 -> can we rename it to TARGET_SUBARCH or something more
  descriptive
- do we want TARGET_BASE_ARCH defined for .h files?
- move all CPPFLAGS/CFLAGS/LDFLAGS/LIBS to configure and export only this 4
  variables (both for config.mak and config-host.mak).  I don't think that
  this only 4 vars will be enough, but I am sure that we can export less
  than we have now.
- remove rest of intelligence (also known as ifs) possible from Makefile*
  and moved it back to ./configure
- once previous steps are done, be able to configure the devices using this
  (or similar mechanism)

Comments?

Later, Juan.


Juan Quintela (6):
  simplify TARGET_BASE_ARCH generation
  simplify TARGET_ARCH2 generation
  simplify TARGET_ABI_DIR generation
  rename s/config_mak/config_host_mak/ and s/config_h/config_host_h/
  Refactor config_softfloat selection in another list
  Generate $target_dir/config.h from $target_dir/config.mak

 Makefile.target |   11 --
 configure       |  391 ++++++++++++++++++++++++++-----------------------------
 create_config   |   55 ++++++++
 3 files changed, 242 insertions(+), 215 deletions(-)
 create mode 100755 create_config

             reply	other threads:[~2009-07-15 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 15:26 quintela [this message]
2009-07-15 15:26 ` [Qemu-devel] [PATCH 1/6] simplify TARGET_BASE_ARCH generation quintela
2009-07-15 15:26 ` [Qemu-devel] [PATCH 2/6] simplify TARGET_ARCH2 generation quintela
2009-07-15 15:26 ` [Qemu-devel] [PATCH 3/6] simplify TARGET_ABI_DIR generation quintela
2009-07-15 15:26 ` [Qemu-devel] [PATCH 4/6] rename s/config_mak/config_host_mak/ and s/config_h/config_host_h/ quintela
2009-07-15 15:26 ` [Qemu-devel] [PATCH 5/6] Refactor config_softfloat selection in another list quintela
2009-07-15 15:26 ` [Qemu-devel] [PATCH 6/6] Generate $target_dir/config.h from $target_dir/config.mak quintela
2009-07-15 15:32   ` [Qemu-devel] " Juan Quintela

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=cover.1247670419.git.quintela@redhat.com \
    --to=quintela@redhat.com \
    --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).