Package Base Details: dolphin-emu-git

Git Clone URL: https://aur.archlinux.org/dolphin-emu-git.git (read-only, click to copy)
Keywords: dolphin emu emulator game gamecube gui nintendo remote revolution triforce wii wiimote
Submitter: None
Maintainer: dpeukert
Last Packager: dpeukert
Votes: 106
Popularity: 0.043056
First Submitted: 2011-08-20 13:05
Last Updated: 2021-01-10 20:26

Pinned Comments

dpeukert commented on 2020-04-10 12:34

The PKGBUILD for this package is hosted here (contributions are welcome!): https://gitlab.com/dpeukert/pkgbuilds/tree/main/dolphin-emu-git

Anonymous comment on 2012-03-04 08:43

@chenxiaolong
But dolphin is written in C++
It used to be
……
_gitname=dolphin-emu
CXXFLAGS="-fpermissive"

build() {
……
Although it override user-specific CXXFLAGS, it worked fine. No CFLAGS is needed.

chenxiaolong commented on 2012-03-04 07:26

Oh, crap. I forgot: bluez is written in C, not C++, so the following is also needed:

export CFLAGS="${CFLAGS} -fpermissive"

Anonymous comment on 2012-03-04 04:57

I had added -fpermissive in the PKGBUILD using the line from @chenxiaolong.

export CXXFLAGS="${CXXFLAGS} -fpermissive"

Uninstalling bluez fixed it for me though.

Anonymous comment on 2012-03-04 03:43

@rlipman
I can't figure out why adding -fpermissive to your CXXFLAGS don't work. How do you add it?
First, you can use that patch for bluez.
Or, simply uninstall bluez and compile dolphin. If you don't need to use a real wiimote, wiiuse and bluez isn't dependencies.

Anonymous comment on 2012-03-04 00:22

I have the same build problem as @peacememories, but adding -fpermissive to my CXXFLAGS didn't fix it. Is there a way to build it without bluez and avoid this issue in the meantime?

I also found out the issue is a bug in bluez, not in dolphin

http://marc.info/?l=linux-bluetooth&m=132843961422749&w=2

chenxiaolong commented on 2012-03-02 16:24

Ahhh...sorry. I should have looked at the PKGBUILD before speaking :) I agree with you on your point. It's pointless to make a copy since most build systems can build in a separate directory.

(when I first used Arch, I had no idea that /tmp was a ramfs. I tried to build chromium-git in /tmp and wondered why the computer froze...:D)

Anonymous comment on 2012-03-02 07:16

@chenxiaolong
What you do is in {_gitname}/build/ cmake..
What I do is in {_gitname}-build/ cmake ../{_gitname}
That's same. No copy is needed.
What it used to do is copy contents in {_gitname}/ to {_gitname}-build and in {_gitname}-build/build cmake ..
I found almost every PKGBUILD with git and cmake do the copy…… Some source can reach 1G+ and the copy is just a waste of time and space especially for those use yaourt's default build location and mount /tmp to ram……

chenxiaolong commented on 2012-03-02 05:55

@sgsdxzy: Actually, if you want you can just have ${_gitname}/ and then:

if [ -d build ]; then rm -rf build; fi
mkdir build
cmake ......

There's no need to make any copy, since building from a subdirectory does not modify the original code (with CMake). Also, it will not affect later builds :)

Anonymous comment on 2012-03-02 02:22

Thanks to chenxiaolong. Another thing to notify is that it now won't do a meaningless copy of the source code. It starts cmake in ${_gitname}-build instead of ${_gitname}-build/build.

chenxiaolong commented on 2012-03-01 18:29

For those who don't want to alter the global CXXFLAGS, the following can be added to the PKGBUILD (anywhere before the cmake line):

export CXXFLAGS="${CXXFLAGS} -fpermissive"