ShuriZma
/
pcsx2
mirror of https://github.com/PCSX2/pcsx2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
pcsx2/cmake/darwin-compiler-i386-generi...

18 lines
668 B
CMake
Raw Normal View History

Include some rather simple CMAKE_TOOLCHAIN_FILE. - Update the build.sh and fix some typos. + Don't add the OSX ones because I have not tested them and it won't even build anyway due to the libaio dependency. Needs to use POSIX AIO or something else. - They are rather simple and all the magic happens in two lines. + First line tells cmake to get ready to compile FOR linux or darwin. It also sets CMAKE_CROSSCOMPILING to true which is the only way to let cmake known that we are using stuff not from the host. + CMAKE_C_COMPILER/CMAKE_CXX_COMPILER are basically used to detect the architecture of the target. Since I used generic cc/c++ the hardcoded -m32 is needed to ensure we get TARGET=i386. Also since I hardcode -m32 and use c++/cc it's to be noted that we can only do i386->i386 (trivial), amd64 -> i386, and x32->i386. . Using something like i586-linux-gnu-{gcc,g++} would also work and enable arm -> i386, etc but it's infeasible and impractical to do all the combinations. File is simple enough that a distro or user can create their own and cross compiling is rather tedious compared to using a chroot to compile it. - I tested it in Debian with "dpkg-buildpackage -ai386" but installing the build dependencies was rather tedious.
2014-12-24 23:15:55 +00:00
# Tell cmake we are cross compiling and targeting darwin
set(CMAKE_SYSTEM_NAME Darwin)
set(CMAKE_SYSTEM_PROCESSOR i686)
# Leave it generic since it could be clang, gnu, etc.
Respect the CC and CXX environment variables when cross building.
2015-01-04 05:56:47 +00:00
if("$ENV{CC}" STREQUAL "" OR "$ENV{CXX}" STREQUAL "")
set(CMAKE_C_COMPILER cc -m32)
set(CMAKE_CXX_COMPILER c++ -m32)
endif()
Include some rather simple CMAKE_TOOLCHAIN_FILE. - Update the build.sh and fix some typos. + Don't add the OSX ones because I have not tested them and it won't even build anyway due to the libaio dependency. Needs to use POSIX AIO or something else. - They are rather simple and all the magic happens in two lines. + First line tells cmake to get ready to compile FOR linux or darwin. It also sets CMAKE_CROSSCOMPILING to true which is the only way to let cmake known that we are using stuff not from the host. + CMAKE_C_COMPILER/CMAKE_CXX_COMPILER are basically used to detect the architecture of the target. Since I used generic cc/c++ the hardcoded -m32 is needed to ensure we get TARGET=i386. Also since I hardcode -m32 and use c++/cc it's to be noted that we can only do i386->i386 (trivial), amd64 -> i386, and x32->i386. . Using something like i586-linux-gnu-{gcc,g++} would also work and enable arm -> i386, etc but it's infeasible and impractical to do all the combinations. File is simple enough that a distro or user can create their own and cross compiling is rather tedious compared to using a chroot to compile it. - I tested it in Debian with "dpkg-buildpackage -ai386" but installing the build dependencies was rather tedious.
2014-12-24 23:15:55 +00:00
# If given a CMAKE_FIND_ROOT_PATH then
# FIND_PROGRAM ignores CMAKE_FIND_ROOT_PATH (probably can't run)
# FIND_{LIBRARY,INCLUDE,PACKAGE} only uses the files in CMAKE_FIND_ROOT_PATH.
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_PACKAGE ONLY)