Package Details: dolphin-emu-nogui-git 2409.r299.gd1ef4d5cc1-1

Git Clone URL: https://aur.archlinux.org/dolphin-emu-git.git (read-only, click to copy)
Package Base: dolphin-emu-git
Description: A Gamecube / Wii emulator - no GUI - git version
Upstream URL: https://dolphin-emu.org
Keywords: dolphin emu emulator game gamecube gui nintendo remote revolution triforce wii wiimote
Licenses: GPL-2.0-or-later
Conflicts: dolphin-emu-cli, dolphin-emu-nogui
Provides: dolphin-emu-cli, dolphin-emu-nogui
Submitter: None
Maintainer: dpeukert
Last Packager: dpeukert
Votes: 123
Popularity: 1.14
First Submitted: 2011-08-20 13:05 (UTC)
Last Updated: 2024-11-10 13:18 (UTC)

Dependencies (45)

Required by (0)

Sources (9)

Pinned Comments

dpeukert commented on 2020-04-10 12:34 (UTC) (edited on 2020-09-26 17:48 (UTC) by dpeukert)

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

Latest Comments

« First ‹ Previous 1 .. 36 37 38 39 40 41 42 43 44 45 46 .. 56 Next › Last »

delroth commented on 2014-05-22 21:51 (UTC)

Build issues with this package are caused by https://bugs.archlinux.org/task/40497 and https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61214 Motivated people might want to rebuild their wxgtk package from ABS using --disable-visibility as a ./configure option. Otherwise, wait and hope that the Arch bug report I made suggesting a workaround gets considered :)

flacs commented on 2014-05-15 10:12 (UTC)

@alucryd: The problem is caused by -finline-functions which is enabled by -O3, so to work around this you could just use "-O3 -fno-inline-functions".

alucryd commented on 2014-05-09 09:58 (UTC)

I removed -DCMAKE_BUILD_TYPE='Release' as release is the default anyway. Also I'm modifying CFLAGS and CXXFLAGS in the PKGBUILD now so you don't even have to edit makepkg.conf. Enjoy.

alucryd commented on 2014-05-09 09:14 (UTC)

mathieuI: I was thinking about adding it as a dep, so here it is. Also added a workaround for the link error. The problem was caused by -O3, which seems to be the default optimization level of a Release build type for cmake. Overriding it with -O2 does the trick, however please make sure that your CFLAGS and CXXFLAGS in /etc/makepkg.conf does not contain -O3, it seems that when 2 optimization flags are passed, the highest takes precedence.

mathieuI commented on 2014-05-09 08:32 (UTC)

Also, could you either add polarssl to the dependencies array, or make this package conflict with it?

alucryd commented on 2014-05-05 17:45 (UTC)

I encountered the linker issue last night on the nightly build server, GCC 4.9 is indeed most likely the culprit. Could somebody report this on dolphin's bug tracker? boogerlad: Any compiled code is built with the flags you specify in /etc/makepkg.conf, just put march=native instead of your current arch, and remove mtune=generic. As for running dolphin, the JIT recompiler will use every extension available. Also OpenMP texture decoding has had its checkbox for a long time, you might want to look at the GUI before looking at the code.

boogerlad commented on 2014-05-05 17:16 (UTC)

Is it possible to turn on openmp and sse if available on the host machine? I know at least https://github.com/dolphin-emu/dolphin/blob/master/Source/Core/VideoCommon/TextureDecoder_x64.cpp has optimizations there.

jakebailey commented on 2014-05-03 07:39 (UTC)

I have the same issue. I think this coincided with the upgrade of gcc to 4.9.

d7s2qmspe7q48 commented on 2014-05-02 13:17 (UTC)

I got a VERY strange problem when linking. I got the following message: Frame.cpp:(.text+0x61df): undefined reference to `wxCommandEvent::Clone() const' After some routine checks about having all dependencies installed correctly, I started playing with the code and found that removing the following lines from src/dolphin-emu/Source/Core/DolphinWX/Frame.cpp made the program link: else if (IsHotkey(event, HK_DECREASE_FRAME_LIMIT)) { if (--SConfig::GetInstance().m_Framelimit > 0x19) SConfig::GetInstance().m_Framelimit = 0x19; } However, I also noticed that (1) from the context, it doesn't make any sense that those lines are causing the problem, and (2) randomly playing with the file made the error return or go away, so it looks like a compiler or linker bug? I'm in testing BTW, maybe that's why. Just commenting in case someone else knows about this or is also affected by the same problem.

alucryd commented on 2014-04-05 13:53 (UTC)

Builds fine without indeed, nuked. Thx!