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

56 lines
2.1 KiB
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 linux
set(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_SYSTEM_PROCESSOR i686)
# It could be i?86-*linux-gnu, x86_64-*linux-gnu, x86_64-*linux-gnux32, etc.
# Leave it generic to only support amd64 or x32 to i386 with any compiler.
cmake: always set -m32 for 32 bits build It fixes cross-compilition issue when users/env set CC/CXX variables
2015-02-22 21:14:26 +00:00
if ("$ENV{CC}" STREQUAL "")
Respect the CC and CXX environment variables when cross building.
2015-01-04 05:56:47 +00:00
set(CMAKE_C_COMPILER cc -m32)
cmake: improve previous commit Avoid to set -m32 two times Fix issue #463
2015-02-27 09:02:38 +00:00
elseif(NOT "$ENV{CC}" MATCHES "-m32")
cmake: always set -m32 for 32 bits build It fixes cross-compilition issue when users/env set CC/CXX variables
2015-02-22 21:14:26 +00:00
set(CMAKE_C_COMPILER $ENV{CC} -m32)
endif()
if ("$ENV{CXX}" STREQUAL "")
Respect the CC and CXX environment variables when cross building.
2015-01-04 05:56:47 +00:00
set(CMAKE_CXX_COMPILER c++ -m32)
cmake: improve previous commit Avoid to set -m32 two times Fix issue #463
2015-02-27 09:02:38 +00:00
elseif(NOT "$ENV{CXX}" MATCHES "-m32")
cmake: always set -m32 for 32 bits build It fixes cross-compilition issue when users/env set CC/CXX variables
2015-02-22 21:14:26 +00:00
set(CMAKE_CXX_COMPILER $ENV{CXX} -m32)
Respect the CC and CXX environment variables when cross building.
2015-01-04 05:56:47 +00:00
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
Be really strict about dependencies. The obtained binaries before and after this commit are identical (sha1sum) when compiled in Debian/Ubuntu/Fedora/ArchLinux. . The linker will always pick the 32bit libraries the only thing this does is make sure we have all the 32bit dependencies installed. Basically we avoid detecting the 64bit libraries and telling the users the 32bit libraries were found. We always link with 32bit libraries therefore this avoids having to wait 5-10min to just be told -lXXX is missing. . The only thing really needed are set(CMAKE_LIBRARY_ARCHITECTURE "../lib32") set(CMAKE_LIBRARY_ARCHITECTURE ".") . which basically ensures we don't pick 64bit headers since CMAKE_LIBRARY_ARCHITECTURE always gets tested first and for some reason FindGTK2 test searches lib64 first then lib32/lib. These values are hardcoded. Right now these arch specific headers are not used but can't say this will always be true. . FIND_LIBRARY_USE_LIB64_PATHS is not needed for native builds and it's covered by CMAKE_SYSTEM_IGNORE_PATH. . NOTE: We filter out lib32 because multilib is not compatible with multiarch.
2014-12-27 20:37:00 +00:00
# cmake 2.8.5 correctly sets CMAKE_LIBRARY_ARCHITECTURE for Debian multiarch.
# Be really strict about what gets used.
if(EXISTS /usr/lib/i386-linux-gnu)
set(CMAKE_SYSTEM_IGNORE_PATH
/lib /lib64 /lib32
/usr/lib /usr/lib64 /usr/lib32
/usr/local/lib /usr/local/lib64 /usr/local/lib32)
list(APPEND CMAKE_LIBRARY_PATH /usr/local/lib/i386-linux-gnu)
list(APPEND CMAKE_LIBRARY_PATH /usr/lib/i386-linux-gnu)
list(APPEND CMAKE_LIBRARY_PATH /lib/i386-linux-gnu)
elseif(EXISTS /usr/lib32)
set(CMAKE_SYSTEM_IGNORE_PATH
/lib /lib64
/usr/lib /usr/lib64
/usr/local/lib /usr/local/lib64)
set(CMAKE_LIBRARY_ARCHITECTURE "../lib32")
list(APPEND CMAKE_LIBRARY_PATH /usr/local/lib32)
list(APPEND CMAKE_LIBRARY_PATH /usr/lib32)
list(APPEND CMAKE_LIBRARY_PATH /lib32)
else()
set(CMAKE_SYSTEM_IGNORE_PATH
/lib64
/usr/lib64
/usr/local/lib64)
set(CMAKE_LIBRARY_ARCHITECTURE ".")
list(APPEND CMAKE_LIBRARY_PATH /usr/local/lib)
list(APPEND CMAKE_LIBRARY_PATH /usr/lib)
list(APPEND CMAKE_LIBRARY_PATH /lib)
endif()
list(REMOVE_DUPLICATES CMAKE_LIBRARY_PATH)
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)