Package Details: sfml-git 2.6.1.r975.gf05baef52-1

Git Clone URL: https://aur.archlinux.org/sfml-git.git (read-only, click to copy)
Package Base: sfml-git
Description: A simple, fast, cross-platform, and object-oriented multimedia API
Upstream URL: http://www.sfml-dev.org/
Licenses: zlib
Conflicts: sfml
Provides: libsfml-audio.so, libsfml-graphics.so, libsfml-network.so, libsfml-system.so, libsfml-window.so, sfml
Submitter: None
Maintainer: oi_wtf
Last Packager: oi_wtf
Votes: 29
Popularity: 0.000000
First Submitted: 2011-04-07 21:07 (UTC)
Last Updated: 2024-06-20 09:17 (UTC)

Required by (107)

Sources (1)

Latest Comments

1 2 3 Next › Last »

oi_wtf commented on 2024-05-15 07:40 (UTC) (edited on 2024-05-15 07:49 (UTC) by oi_wtf)

Simple packages ending in -git are always expected to follow master, main or whatever the project calls their main branch, or sometimes feature branches for more specific -feature-git packages. There should be no need to indicate that this package follows master, it is implied by -git.

The pkgver of the package is updated by the pkgver() function accordingly while building, the version of the built package should be the current updated version number. AUR still has an outdated pkgver, because the PKGBUILD did not need any changing since then. And I'm not pushing a new PKGBUILD every week just to keep the pkgver up to date when it auto-updates when building anyway.

If you need 2.6, use [extra]/sfml: https://archlinux.org/packages/extra/x86_64/sfml/

Or just add #tag=2.6.1 or #branch=2.6.x to the source-url and build. The pkgver() function should even update the pkgver correctly in this case.

See https://wiki.archlinux.org/title/VCS_package_guidelines for details on how this works.

trustytrojan commented on 2024-05-10 23:30 (UTC)

Just installed sfml-git and it cloned and installed the master branch, and not 2.6.0 as the package is versioned. Is this version label intended? If not, please change it to 3.0 (the next SFML release) or indicate master branch. It's quite confusing otherwise.

oi_wtf commented on 2023-06-14 16:28 (UTC) (edited on 2023-06-14 16:29 (UTC) by oi_wtf)

Nope.

SFML_USE_SYSTEM_DEPS only matters for Windows, Android or iOS. Not generic linux.

And you'd have to set it to TRUE to link system libs on the platforms above, quoting CMakeLists.txt:

sfml_set_option(SFML_USE_SYSTEM_DEPS FALSE BOOL "TRUE to use system dependencies, FALSE to use the bundled ones.")

I double checked with ldd /usr/lib/libsfml-*.so and pacman -Ql sfml-git. Bundled libs are not part of the package and the sfml libs are linked against the systems libs.

No action on this package required, IMHO. If you think otherwise: Proof please.

MarsSeed commented on 2023-06-14 13:41 (UTC) (edited on 2023-06-14 13:41 (UTC) by MarsSeed)

It seems you need to set cmake option SFML_USE_SYSTEM_DEPS=FALSE, otherwise the build will use the source-included external libraries instead of the ones installed on the system or build environment.

<deleted-account> commented on 2013-07-18 13:20 (UTC)

This should be updated to use a pkgver() function.

shackra commented on 2012-08-04 02:44 (UTC)

There was a problem with a CMakeLists.txt, here is the new PKGBUILD http://ompldr.org/vZXo5aQ

<deleted-account> commented on 2012-05-08 11:02 (UTC)

Fixed

<deleted-account> commented on 2012-05-03 23:28 (UTC)

Thanks for the comments guys, I'll get to updating the package during the weekend.

<deleted-account> commented on 2012-05-03 09:31 (UTC)

Why is it flagged as outdated ? There are still updates on the repo !

CruzR commented on 2012-04-24 21:38 (UTC)

The cmake option for building the docs is SFML_BUILD_DOC and the option for building the examples is SFML_BUILD_EXAMPLES. Source: http://www.sfml-dev.org/tutorials/2.0/compile-with-cmake.php