Package Details: mingw-w64-cmake 1-12

Git Clone URL: https://aur.archlinux.org/mingw-w64-cmake.git (read-only)
Package Base: mingw-w64-cmake
Description: CMake wrapper for MinGW (mingw-w64)
Upstream URL: http://fedoraproject.org/wiki/MinGW
Licenses: GPL
Submitter: brcha
Maintainer: xantares
Last Packager: xantares
Votes: 25
Popularity: 1.083842
First Submitted: 2013-04-17 12:11
Last Updated: 2016-04-03 07:34

Required by (79)

Sources (3)

  • mingw-cmake.sh
  • mingw-wine.sh
  • toolchain-mingw.cmake

Latest Comments

xantares commented on 2016-04-03 07:36

@chenxiaolong, thanks!

chenxiaolong commented on 2016-04-03 00:45

@xantares: As an alternative to copying DLLs in mingw-wine.sh, you could simply set the WINEPATH environment variable to the bin directory.

For example, I run my CMake tests with:

WINEPATH="/usr/i686-w64-mingw32/bin;$(pwd)/libmblog" ctest -VV

Something similar should also work in your script.

Cloudef commented on 2015-12-10 00:16

@xantares

- You make good point of the native cflags. I did not consider those. It's weird fedora uses those weird flags as well (such as forcing exceptions, defining ssp parameter without enabling it, and just blatantly forcing -O2, -g, -Wall and -pipe, which are all situational options)

- Yeah I sort of assumed this. I'm not sure what implications with moving the variables to the toolchain file would be though. In theory it should work the same, just without the warnings.

Anyhow, thanks for your explanations.

xantares commented on 2015-12-08 13:10

https://fedoraproject.org/wiki/Packaging:MinGW?rd=Packaging/MinGW

xantares commented on 2015-12-08 13:07

@cloudef

- Native flags from makepkg should not be read, the option !buildflags should be set in every mingw package, as you may have something like march=... which is invalid for cross-compiling
I'm no expert in what those flags are and what they should be, I wanted to standardize the way mingw packages are built (see also mingw-w64-configure).
I just took them from Fedora, and maybe they even changed.

- I may have put them here because I had several packages relying on this behavior.
I also use the toolchain files for development, and setting these variables in the toolchain would maybe be more annoying than the cmake unused warning.

xan.

Cloudef commented on 2015-12-07 13:50

@xantares

I usually expect packages on arch / aur to be close to upstream / vanilla as possible so the CFLAGS and BUILD_SHARED_LIBS came as bit of surprise.

For example the CFLAGS looks quite similar to that of /etc/makepkg.conf default ones, but cmake _does_ read CFLAGS and CXXFLAGS first time cmake is ran, so it will actually work with /etc/makepkg.conf and you don't have to set them in the script, to avoid surprises for some. The fexceptions also makes no sense in the flags. nor the ssp buffer size without enabling ssp. -Wp, (while correct) is unneccessary. Also they set some defaults like -O2 with -g, this is all quite undesirable for people who simply assume it just handles cross-compilation using mingw but doesn't touch anything else.

For BUILD_SHARED_LIBS, while I agree there are many horrible cmake projects and they do weird things regarding this global variable, or weird things in general. I think these hacks should be handled at their respective PKGBUILDs.

CMAKE_INSTALL_LIBDIR
INCLUDE_INSTALL_DIR
LIB_INSTALL_DIR
SHARE_INSTALL_DIR
SYSCONF_INSTALL_DIR

These variables also aren't standard CMake variables, apart from CMAKE_INSTALL_LIBDIR, that is actually provided by GNUInstallDirs cmake module. Others are hacks by project developers who dint bother reading CMake documentation and find about GNUInstallDirs, or the project was done with very early before GNUInstallDirs was available.

While it's bit dirty, I don't propose removal of those variables. But you might be able to put them into toolchain file instead and avoid CMake warning about unused manually specified variables.

I think this package is highly useful and really nice, but these 2 certainly were surprising to me. Especially since I actually used this in development instead of building AUR packages.

xantares commented on 2015-12-07 12:38

@cloudef:
- these are CFLAGS that go well for mingw, I dont know the meaning of all flags, but you need at least to override native flags that would be invalid here
- BUILD_SHARED_LIBS is set to build shared libs by default, but not every packages honor this canonical way of deciding static/shared, some use another name or set the default value to OFF

Cloudef commented on 2015-12-07 09:46

Why do you specify CFLAGS and force BUILD_SHARED_LIBS in the wrapper?

Schala commented on 2013-05-08 21:49

Oooh I didn't see that.

brcha commented on 2013-04-17 15:28

Why? What's the difference? The names are symlinked. I can make the scripts be *-w64-mingw32-cmake and symlinks mingw{32,64}-cmake, but I see no difference between the two combinations.

All comments