CrossCompilingOsX - Revision history

LiamW: build dyld

2014-06-05T20:49:47Z

build dyld

← Older revision		Revision as of 20:49, 5 June 2014
Line 10:		Line 10:


	== Making the chroot ==		= Making the chroot =

	I used Ubuntu 14.04 "Trusty Tahr" for doing the initial chroot. The process was as follows:		I used Ubuntu 14.04 "Trusty Tahr" for doing the initial chroot. The process was as follows:
Line 60:		Line 60:


	== Building clang ==		= Building clang =

	'''NOTE:''' There is a [http://llvm.org/bugs/show_bug.cgi?id=19945 bug] with building cross-compilers for OS X.		'''NOTE:''' There is a [http://llvm.org/bugs/show_bug.cgi?id=19945 bug] with building cross-compilers for OS X.
Line 106:		Line 106:


	== Installing dyld ==		= Installing dyld =

			dyld is the Mach-O loader for OS X, and will allow you to run many command line tools for OS X. We need to install the GNUStep sources as well as the binaries here, be careful!
			apt-get install git cmake clang nasm libxml2-dev libgnutls-dev libicu-dev libcairo-dev libjpeg-dev libpng-dev \
			libtiff-dev libbsd-dev libudev-dev liblcms-dev libkqueue-dev libssl-dev libbz2-dev uuid-dev libncurses-dev \
			libxrandr-dev libavcodec-dev libavformat-dev autoconf automake autopoint
			== Building gnustep-make ==
			cd /usr/src
			svn co http://svn.gna.org/svn/gnustep/tools/make/trunk/ gnustep-make
			cd gnustep-make
			CC=clang CXX=clang++ ./configure
			make install
			== Building gnustep-libobjc2 ==
			svn co http://svn.gna.org/svn/gnustep/libs/libobjc2/trunk/ gnustep-libobjc2
			cd gnustep-libobjc2
			OBJCFLAGS=-fblocks CC=clang CXX=clang++ cmake .
			rm GNUmakefile
			make; make install
			== Building gnustep-base ==
			svn co http://svn.gna.org/svn/gnustep/libs/base/trunk/ gnustep-base
			cd gnustep-base
			OBJCFLAGS=-fblocks CC=clang CXX=clang++ ./configure
			make; make install
			== Building gnustep-gui ==
			svn co http://svn.gna.org/svn/gnustep/libs/gui/trunk/ gnustep-gui
			cd gnustep-gui
			OBJCFLAGS=-fblocks CC=clang CXX=clang++ ./configure
			make; make install
			== Building libdispatch ==
			git clone git://github.com/nickhutchinson/libdispatch.git libdispatch
			cd libdispatch
			./configure
			make; make install
			== Building gnustep-corebase ==
			svn co http://svn.gna.org/svn/gnustep/libs/corebase/trunk/ gnustep-corebase
			cd gnustep-corebase
			'''NOTE: there seems to be a bug in the configure script.'''
			To work around this bug, comment out these lines in configure.ac:
			# AC_CHECK_LIB(dispatch, dispatch_get_main_queue_eventfd_np)
			# AS_IF([test "$ac_cv_lib_dispatch_dispatch_get_main_queue_eventfd_np" = "no"],
			# [AC_MSG_ERROR([Compatible libdispatch not found for GCD support! Use --disable-gcd to disable GCD support or install GCD.])])])
			Then run:
			autoconf configure.ac > configure

			OBJCFLAGS=-fblocks CC=clang CXX=clang++ ./configure
			make; make install

			== Building darling ==
			Finally!
			git clone https://github.com/LubosD/darling.git
			cd darling
			CC=clang CXX=clang++ cmake .
			There appears to be another bug here, in /usr/local/include/CoreFoundation/CFRunLoop.h:207.
			To fix it, just deactivate the code block like this:
			#if 0 && OS_API_VERSION(MAC_OS_X_VERSION_10_4, GS_API_LATEST)
			DEFINE_BLOCK_TYPE_NO_ARGS(PerformBlockType, void);
			CF_EXPORT void
			CFRunLoopPerformBlock (CFRunLoopRef rl, CFTypeRef mode, PerformBlockType block);
			#endif
			Then continue:
			make; make install

	More coming...		More coming...

LiamW: formatting

2014-06-05T20:30:05Z

formatting

← Older revision		Revision as of 20:30, 5 June 2014
Line 8:		Line 8:

	The following should be done on the ''host'' system first. Download the Xcode DMG, and use dmg2img to convert it to an IMG. Mount the IMG, and put the .pkg files into the chroot somewhere. I'm using /mnt/apple.		The following should be done on the ''host'' system first. Download the Xcode DMG, and use dmg2img to convert it to an IMG. Mount the IMG, and put the .pkg files into the chroot somewhere. I'm using /mnt/apple.


			== Making the chroot ==

	I used Ubuntu 14.04 "Trusty Tahr" for doing the initial chroot. The process was as follows:		I used Ubuntu 14.04 "Trusty Tahr" for doing the initial chroot. The process was as follows:
Line 56:		Line 59:
	This may take a while.		This may take a while.

	~~Next, we're going to build~~ clang~~, llvm, and libc++ that target OS X.~~
			== Building clang ==

	'''NOTE:''' There is a [http://llvm.org/bugs/show_bug.cgi?id=19945 bug] with building cross-compilers for OS X.		'''NOTE:''' There is a [http://llvm.org/bugs/show_bug.cgi?id=19945 bug] with building cross-compilers for OS X.
	cd /usr/src		cd /usr/src
Line 69:		Line 74:
	make install		make install

			== Getting Headers ==
	To tease the headers out of the Xcode so that we can compile anything, we need to install the xar archiver, which is not packaged in Trusty.		To tease the headers out of the Xcode so that we can compile anything, we need to install the xar archiver, which is not packaged in Trusty.
	wget https://xar.googlecode.com/files/xar-1.5.2.tar.gz		wget https://xar.googlecode.com/files/xar-1.5.2.tar.gz
Line 98:		Line 104:

	Next step: APSL headers for OSX, from Xcode, and then add libc++ compile instructions		Next step: APSL headers for OSX, from Xcode, and then add libc++ compile instructions


			== Installing dyld ==



	More coming...		More coming...

LiamW at 02:13, 5 June 2014

2014-06-05T02:13:56Z

← Older revision		Revision as of 02:13, 5 June 2014
Line 57:		Line 57:

	Next, we're going to build clang, llvm, and libc++ that target OS X.		Next, we're going to build clang, llvm, and libc++ that target OS X.
			'''NOTE:''' There is a [http://llvm.org/bugs/show_bug.cgi?id=19945 bug] with building cross-compilers for OS X.
	cd /usr/src		cd /usr/src
	svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm		svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
Line 88:		Line 88:
	cpio -idv < ../Payload		cpio -idv < ../Payload
	Okay, finally. Now we can figure out what's going where.		Okay, finally. Now we can figure out what's going where.

			./System and ./Library are fine. We can just copy those over:
			cp -R ./System /System
			cp -R ./Library /Library
			But ./usr is tricky — we might end up overwriting some sort of important file if we try just blatantly overwriting our /usr.
			So, what do we do?
			Scan the include paths for clang, and see what we can get away with, of course.


	Next step: APSL headers for OSX, from Xcode, and then add libc++ compile instructions		Next step: APSL headers for OSX, from Xcode, and then add libc++ compile instructions

LiamW: whoops

2014-06-04T19:07:30Z

whoops

← Older revision		Revision as of 19:07, 4 June 2014
Line 7:		Line 7:
	* a good processor and a lot of RAM		* a good processor and a lot of RAM

	The following should be done on the ''host'' system first. Download the Xcode DMG, and use dmg2img to convert it to an IMG. Mount the IMG~~, use Xarchiver to decompress the package files~~, and put the .pkg files into the chroot somewhere. I'm using /mnt/apple.		The following should be done on the ''host'' system first. Download the Xcode DMG, and use dmg2img to convert it to an IMG. Mount the IMG, and put the .pkg files into the chroot somewhere. I'm using /mnt/apple.

	I used Ubuntu 14.04 "Trusty Tahr" for doing the initial chroot. The process was as follows:		I used Ubuntu 14.04 "Trusty Tahr" for doing the initial chroot. The process was as follows:

LiamW: instructions to decompress a .pkg file

2014-06-04T19:06:58Z

instructions to decompress a .pkg file

← Older revision		Revision as of 19:06, 4 June 2014
Line 6:		Line 6:
	* root access to your build system		* root access to your build system
	* a good processor and a lot of RAM		* a good processor and a lot of RAM

			The following should be done on the ''host'' system first. Download the Xcode DMG, and use dmg2img to convert it to an IMG. Mount the IMG, use Xarchiver to decompress the package files, and put the .pkg files into the chroot somewhere. I'm using /mnt/apple.

	I used Ubuntu 14.04 "Trusty Tahr" for doing the initial chroot. The process was as follows:		I used Ubuntu 14.04 "Trusty Tahr" for doing the initial chroot. The process was as follows:
Line 66:		Line 68:
	make -j4		make -j4
	make install		make install

			To tease the headers out of the Xcode so that we can compile anything, we need to install the xar archiver, which is not packaged in Trusty.
			wget https://xar.googlecode.com/files/xar-1.5.2.tar.gz
			tar -xvf xar-1.5.2.tar.gz
			apt-get install libxml2-dev libssl-dev libbz2-dev
			cd xar-1.5.2; ./configure
			make; make install

			Now go to the location of your PKG files. Each one needs to be extracted, and then the payload needs to be extracted too.
			cd /mnt/apple
			mkdir DeveloperToolsCLI
			cd DeveloperToolsCLI
			xar -xvf ../DeveloperToolsCLI.pkg
			Extract the payload (gzip doesn't really like unnamed files)
			mv ./Payload ./Payload.gz
			gunzip ./Payload.gz
			The resulting file is a compressed CPIO archive. Extract that too:
			mkdir Contents; cd Contents
			cpio -idv < ../Payload
			Okay, finally. Now we can figure out what's going where.

	Next step: APSL headers for OSX, from Xcode, and then add libc++ compile instructions		Next step: APSL headers for OSX, from Xcode, and then add libc++ compile instructions

LiamW: man-db, groff

2014-06-04T18:33:49Z

man-db, groff

← Older revision		Revision as of 18:33, 4 June 2014
Line 40:		Line 40:

	Install some packages to start off with:		Install some packages to start off with:
	apt-get install sudo nano vim bzr subversion		apt-get install sudo nano vim bzr subversion groff man-db

	Edit your /etc/apt/sources.list to include the universe source and update:		Edit your /etc/apt/sources.list to include the universe source and update:

LiamW: fix a problem with --enable-targets

2014-06-04T15:53:03Z

fix a problem with --enable-targets

← Older revision		Revision as of 15:53, 4 June 2014
Line 61:		Line 61:
	svn co http://llvm.org/svn/llvm-project/cfe/trunk clang		svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
	cd ..; mkdir build; cd build		cd ..; mkdir build; cd build
	../configure --prefix=/usr/clang_3_4 --enable-optimized --enable-targets='''x86_64~~-apple-darwin11.4.2~~''' \		../configure --prefix=/usr/clang_3_4 --enable-optimized --enable-targets='''x86_64,x86''' \
	--disable-compiler-version-checks --host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu \		--disable-compiler-version-checks --host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu \
	--target='''x86_64-apple-darwin11.4.2'''		--target='''x86_64-apple-darwin11.4.2'''

LiamW at 13:53, 4 June 2014

2014-06-04T13:53:46Z

← Older revision		Revision as of 13:53, 4 June 2014
Line 40:		Line 40:

	Install some packages to start off with:		Install some packages to start off with:
	apt-get install sudo nano vim bzr		apt-get install sudo nano vim bzr subversion

	Edit your /etc/apt/sources.list to include the universe source and update:		Edit your /etc/apt/sources.list to include the universe source and update:
Line 51:		Line 51:
	Now install gnustep:		Now install gnustep:
	apt-get install gnustep gnustep-devel		apt-get install gnustep gnustep-devel

			This may take a while.

			Next, we're going to build clang, llvm, and libc++ that target OS X.

			cd /usr/src
			svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
			cd llvm/tools
			svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
			cd ..; mkdir build; cd build
			../configure --prefix=/usr/clang_3_4 --enable-optimized --enable-targets='''x86_64-apple-darwin11.4.2''' \
			--disable-compiler-version-checks --host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu \
			--target='''x86_64-apple-darwin11.4.2'''
			make -j4
			make install

			Next step: APSL headers for OSX, from Xcode, and then add libc++ compile instructions


	More coming...		More coming...

LiamW: add gnustep and universe

2014-06-04T13:38:27Z

add gnustep and universe

← Older revision		Revision as of 13:38, 4 June 2014
Line 36:		Line 36:
	(from https://help.ubuntu.com/community/BasicChroot)		(from https://help.ubuntu.com/community/BasicChroot)

	apt-get install sudo nano vim ~~gcc g++~~		To avoid pointless warnings about missing locales, do this:
			apt-get install language-pack-en

			Install some packages to start off with:
			apt-get install sudo nano vim bzr

			Edit your /etc/apt/sources.list to include the universe source and update:
			deb mirror.url.com/ubuntu/ trusty main
			deb-src mirror.url.com/ubuntu/ trusty main

			deb mirror.url.com/ubuntu/ trusty universe
			deb-src mirror.url.com/ubuntu/ trusty universe

			Now install gnustep:
			apt-get install gnustep gnustep-devel

	More coming...		More coming...

LiamW: Add bit about procfs, links, packages

2014-06-04T11:27:59Z

Add bit about procfs, links, packages

← Older revision		Revision as of 11:27, 4 June 2014
Line 21:		Line 21:

	Install a base system:		Install a base system:
	sudo debootstrap --variant=buildd --arch '''amd64''' trusty /var/chroot/ '''~~http://~~mirror.url.com/ubuntu/'''		sudo debootstrap --variant=buildd --arch '''amd64''' trusty /var/chroot/ '''mirror.url.com/ubuntu/'''
	where '''~~http://~~mirror.url.com/ubuntu/''' can be any of [https://launchpad.net/ubuntu/+archivemirrors these mirrors].		where '''mirror.url.com/ubuntu/''' can be any of [https://launchpad.net/ubuntu/+archivemirrors these mirrors].

	Now copy your resolv.conf for internet access (required):		Now copy your resolv.conf for internet access (required):
	sudo cp /etc/resolv.conf /var/chroot/etc/resolv.conf		sudo cp /etc/resolv.conf /var/chroot/etc/resolv.conf

			Bind your procfs into the chroot for gnustep:
			sudo mount -o bind /proc /var/chroot/proc

	Finally, chroot into your target:		Finally, chroot into your target:
Line 31:		Line 34:

	You should now have a working chroot, free for you to destroy as you see fit.		You should now have a working chroot, free for you to destroy as you see fit.
			(from https://help.ubuntu.com/community/BasicChroot)

	~~(from https://help.ubuntu.com/community/BasicChroot)~~		apt-get install sudo nano vim gcc g++

	More coming...		More coming...