You are not logged in.
Hi all, I am trying to compile source code for the PCSX2 emulator, as I am hoping to contribute to the project. However, when I try to build, cmake gives me this error:
-- Could NOT find Threads (missing: Threads_FOUND)
-- Could NOT find wxWidgets (missing: wxWidgets_FOUND)
I have tried installing wxgtk2.8 and also the 32 bit version, but cmake does not seem to recognize it.
Last edited by krysto (2014-02-16 19:42:27)
Offline
Did you just download the source code and try to compile or are you using the PKGBUILD from the AUR?
At least the PKGBUILD from the AUR should give you an idea what needs to be done to get it to compile.
Offline
No, I just downloaded the source code from github. I will look at the pkgbuild though, thanks for the hint.
Offline
How exactly are you compiling PCSX2? Are you using ABS?
Offline
Did you just download the source code and try to compile or are you using the PKGBUILD from the AUR?
At least the PKGBUILD from the AUR should give you an idea what needs to be done to get it to compile.
PCSX2 is in the repos too: https://projects.archlinux.org/svntogit … ages/pcsx2
Offline
The team wrote a build script, build.sh. You can run that, which then runs cmake, which then in turn runs GNU make.
Offline
In Arch Linux we use pacman, our package manager to install packages and their dependencies and makepkg to build the packages using PKGBUILDs.
Offline
Yes, I have used pacman before to install software, but what if I want to contribute to the development of a project? Does pacman place the source code somewhere on my machine?
Offline
pacman installs packages, makepkg deals with source code. Read the wiki article about ABS.
Offline
Yes, I have used pacman before to install software, but what if I want to contribute to the development of a project?
Usually when you are developing software you don't install the package every time you compile it. You just make sure that you can run it from the location where you compiled it. That way you can keep the latest stable version that you can use for leisure time and the development version for testing. Also for contributing to a project you should directly interact with the project's repository (svn, git, ...). So I refer back to my first post here where the PKGBUILD can give you an idea how to go about compiling the source code yourself.
Just don't run "make install" because that will leave your system in a messy state, a simple "make" (with the proper configuration) should result in a locally build binary that you can run from where it was compiled.
Offline
So a good rule of thumb would be to use pacman to manage any shared libraries and packages that I don't need to touch, and keep all working source code and binaries seperate, like in /home/user/workspace?
Last edited by krysto (2014-02-16 19:28:29)
Offline
You can write a PKGBUILD for the code you're developing too.
Offline
After looking at the pkgbuild, I learned that you need to add flags to the build.sh script to tell cmake where to find wxwidgets:
-DwxWidgets_CONFIG_EXECUTABLE='/usr/bin/wx-config-2.8'
-DwxWidgets_wxrc_EXECUTABLE='/usr/bin/wxrc-2.8'
So... problem solved! I was able to compile and run the emulator in my git folder.
Last edited by krysto (2014-02-16 19:41:15)
Offline