

pkgname=dolphin-emu-fresh

pkgver=0

pkgrel=1

pkgdesc='A GameCube / Wii / Triforce emulator'

arch=('x86_64')

url='http://www.dolphin-emu.org/'

license=('GPL')

depends=('alsa-lib' 'bluez-libs' 'cairo' 'enet' 'gcc-libs' 'gdk-pixbuf2'

'glib2' 'glibc' 'gtk2' 'hidapi' 'libevdev' 'libgl' 'libpng' 'libpulse'

'libsm' 'libx11' 'libxi' 'libxrandr' 'libxxf86vm' 'lzo' 'mbedtls'

'miniupnpc' 'pango' 'sfml' 'zlib' 'pulseaudio' 'ffmpeg' 'pugixml'

'bluez' 'bluez-utils-compat' 'bluez-firmware' 'bluez-plugins'

'bluez-libs' 'bluez-qt' 'bluez-tools' 'bluez-openrc' 'curl' 'xorg-xinput'

'libeudev' 'libusb' 'libgusb' 'libusb-compat' 'lib32-libusb' 'libtiger'

'pangomm' 'pangox-compat' 'libglvnd' 'sndio' 'alsa-plugins' 'alsa-firmware'

'alsa-utils' 'alsa-lib' 'pulseaudio-alsa' 'alsa-oss')



makedepends=('cmake' 'git' 'qt5-base' 'pango' 'fakeroot')

source=('dolphin-emu::git+https://github.com/dolphin-emu/dolphin.git')

sha256sums=('SKIP')



build() {

git clone https://github.com/dolphin-emu/dolphin.git

mkdir -p dolphin/build

cd dolphin/build



cmake -DOpenGL_GL_PREFERENCE=GLVND -DUSE_X11=1 -DUSE_EGL=1 -DCMAKE_INSTALL_PREFIX=/usr -DENABLE_QT2=TRUE -DCMAKE_BUILD_TYPE=Release ..

make -j48

}



package() {

cd dolphin/build



make DESTDIR="${pkgdir}" install

install -Dm 644 ../Data/51-usb-device.rules -t "${pkgdir}"/usr/lib/udev/rules.d/

}





# make install

# install -Dm 644 ../Data/51-usb-device.rules -t "${pkgdir}"/usr/lib/udev/rules.d/



# vim: ts=2 sw=2 et:





Hey man I just made my first 3 PKGBUILD's, I made them out of git repos instead of them being like actual packages with version numbers/etc, all I really need to learn is how to give it a version number & how to make it automate its own updates...like... when there's a new package available to be packaged, how do we know? Do the packages just update themselves or do we need to alter the PKGBUILD to make it update in the package manager? I can start with gaming emulators, I have so far done Dolphin-emu, Citra-emu & Medusa-emu, once I am more experienced I'll be able to do other packages. Maybe in a few months I'll have enough experience to do more packages but I would prefer to start with stuff that requires cmake, qmake or ./configureInbox me if you don't mind & just teach me a few of the things I have mentioned here that I don't understand & I'll be good-to-go for the simple packages, and you guys can look over the first ones I make to make sure I am doing everything right & give me tips about what I am doing wrong. This is the first one I made, I made a similar one for citra-emu & medusa-emu.