Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] package/ogre: bump to version 1.12.9
Date: Tue, 29 Dec 2020 23:22:19 +0100	[thread overview]
Message-ID: <20201229232219.77ab5e2f@windsurf> (raw)
In-Reply-To: <20201207204821.3588178-1-romain.naour@gmail.com>

Hello Romain,

On Mon,  7 Dec 2020 21:48:17 +0100
Romain Naour <romain.naour@gmail.com> wrote:

> Remove upstream patch [1].
> 
> tinyxml has been replaced by pugixml [2].
> 
> Switch to git download method since github release without
> the complete source code in the tarball [3].
> 
> Update indentation of hash file (two spaces).
> 
> The sdl2-config.cmake generated by sdl2 package is broken for
> cross-compilation since it add /usr/include/SDL2 in CFLAGS.
> 
> Such flags are unsafe for cross-compilation since it mixes
> headers for the host and target.
> 
> sdl2-config.cmake must be removed from staging since
> we are using autotools build system to build sdl2 package
> [4][5].

I'm confused by all these explanations about sdl2-config.cmake, because
they appear here in this patch... but there's nothing related to that
in the patch. And in fact your sdl2-config.cmake fix has already been
merged in commit d59261836a2ae2d024645b1e286540dd4269b6c8.

> ogre 1.12.7 only include <sys/sysctl.h> for iOS in order to
> build with glibc >= 2.32 [6].

And? So what?


> +OGRE_VERSION = v1.12.9

We don't want the leading "v" in the version variable. I'm not sure how
we handle that for git-based downloads. With <pkg>_DL_VERSION ?

> +OGRE_SITE = https://github.com/OGRECave/ogre
> +OGRE_SITE_METHOD = git
> +OGRE_LICENSE = MIT (main library, DeferredShadingMedia samples), Public Domain (samples and plugins)
>  OGRE_LICENSE_FILES = LICENSE
>  OGRE_INSTALL_STAGING = YES
>  
> -# Ogre use a bundled version of tinyxml
> +# Download with imgui submodule (https://github.com/ocornut/imgui

Missing closing parenthesis.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2020-12-29 22:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 20:48 [Buildroot] [PATCH 1/5] package/ogre: bump to version 1.12.9 Romain Naour
2020-12-07 20:48 ` [Buildroot] [PATCH 2/5] support/scripts/gen-bootlin-toolchains: riscv32 use a pre-2.33 glibc version without RPC support Romain Naour
2020-12-07 21:50   ` Thomas Petazzoni
2020-12-07 22:30     ` Romain Naour
2020-12-08 10:55       ` Thomas Petazzoni
2020-12-29 21:05   ` Thomas Petazzoni
2020-12-07 20:48 ` [Buildroot] [PATCH 3/5] toolchain/toolchain-external/toolchain-external-bootlin: regenerate for riscv32 toolchain Romain Naour
2020-12-29 21:05   ` Thomas Petazzoni
2020-12-07 20:48 ` [Buildroot] [PATCH 4/5] support/{config-fragments, testing}: select INET_RPC option for custom glibc external toolchains Romain Naour
2020-12-07 21:52   ` Thomas Petazzoni
2020-12-07 22:33     ` Romain Naour
2020-12-29 21:06   ` Thomas Petazzoni
2020-12-07 20:48 ` [Buildroot] [PATCH 5/5] package/glibc: bump to version 2.32-23-g050022910be1d1f5c11cd5168f1685ad4f9580d2 Romain Naour
2020-12-29 22:34   ` Yann E. MORIN
2020-12-29 22:37     ` Thomas Petazzoni
2020-12-29 22:22 ` Thomas Petazzoni [this message]
2021-01-04 21:02   ` [Buildroot] [PATCH 1/5] package/ogre: bump to version 1.12.9 Romain Naour

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=20201229232219.77ab5e2f@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox