All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/6] pixman: add output dir to include path
Date: Tue, 13 Nov 2012 18:57:57 +0100	[thread overview]
Message-ID: <50A28A25.6050500@weilnetz.de> (raw)
In-Reply-To: <1352796133-956-2-git-send-email-kraxel@redhat.com>

Am 13.11.2012 09:42, schrieb Gerd Hoffmann:
> Needed to make sure the (generated) pixman-version.h file is found.
> Based on a patch from Blue Swirl.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
>   configure |    6 +++---
>   1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/configure b/configure
> index 7290f50..18faded 100755
> --- a/configure
> +++ b/configure
> @@ -2121,8 +2121,9 @@ else
>       echo "      git submodule update --init pixman"
>       exit 1
>     fi
> -  pixman_cflags="-I${source_path}/pixman/pixman"
> -  pixman_libs="-Lpixman/pixman/.libs -lpixman-1"
> +  mkdir -p pixman/pixman
> +  pixman_cflags="-I${source_path}/pixman/pixman -I$(pwd)/pixman/pixman"
> +  pixman_libs="-L$(pwd)/pixman/pixman/.libs -lpixman-1"

I'd prefer \$(BUILD_DIR) instead of $(pwd) for cflags and libs
because it allows moving the build directory.

\$(SRC_PATH) could be used instead of $(source_path).
This would also avoid hardcoded paths in the generated
Makefile code and match better to other include parameters.

>   fi
>   QEMU_CFLAGS="$QEMU_CFLAGS $pixman_cflags"
>   libs_softmmu="$libs_softmmu $pixman_libs"
> @@ -4154,7 +4155,6 @@ DIRS="$DIRS pc-bios/optionrom pc-bios/spapr-rtas"
>   DIRS="$DIRS roms/seabios roms/vgabios"
>   DIRS="$DIRS qapi-generated"
>   DIRS="$DIRS libcacard libcacard/libcacard libcacard/trace"
> -DIRS="$DIRS pixman"
>   FILES="Makefile tests/tcg/Makefile qdict-test-data.txt"
>   FILES="$FILES tests/tcg/cris/Makefile tests/tcg/cris/.gdbinit"
>   FILES="$FILES tests/tcg/lm32/Makefile libcacard/Makefile"

  reply	other threads:[~2012-11-13 17:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  8:42 [Qemu-devel] [PULL 0/6] pixman build fixes Gerd Hoffmann
2012-11-13  8:42 ` [Qemu-devel] [PATCH 1/6] pixman: add output dir to include path Gerd Hoffmann
2012-11-13 17:57   ` Stefan Weil [this message]
2012-11-14  8:40     ` Gerd Hoffmann
2012-11-14 12:33       ` Gerd Hoffmann
2012-11-13  8:42 ` [Qemu-devel] [PATCH 2/6] pixman: pass tools to configure Gerd Hoffmann
2012-11-13 17:50   ` Stefan Weil
2012-11-14  8:42     ` Gerd Hoffmann
2012-11-13  8:42 ` [Qemu-devel] [PATCH 3/6] pixman: disable gtk Gerd Hoffmann
2012-11-13 18:27   ` Peter Maydell
2012-11-13  8:42 ` [Qemu-devel] [PATCH 4/6] pixman: add pass cflags, add -fPIC Gerd Hoffmann
2012-11-13 18:28   ` Peter Maydell
2012-11-13  8:42 ` [Qemu-devel] [PATCH 5/6] pixman: build internal version early Gerd Hoffmann
2012-11-13 18:29   ` Peter Maydell
2012-11-13 18:41     ` Johnson, Eric
2012-11-14 12:41       ` Gerd Hoffmann
2012-11-14 18:42         ` Johnson, Eric
2012-11-13  8:42 ` [Qemu-devel] [PATCH 6/6] pixman: add licensing info Gerd Hoffmann
2012-11-13 17:31 ` [Qemu-devel] [PULL 0/6] pixman build fixes Peter Maydell
2012-11-13 18:07   ` Stefan Weil
2012-11-14 16:27 ` Anthony Liguori

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=50A28A25.6050500@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 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.