NSLU2-Linux
view · edit · print · history

HowTo.NativelyCompileUnslungPackages History

Hide minor edits - Show changes to markup

October 29, 2011, at 02:46 AM by SRS -- success on 10/28/2011
Added lines 5-9:

a success on 10/28/2011 http://www.nslu2-linux.org/wiki/HowTo/TransmissionCompileBuild

December 05, 2006, at 11:36 PM by BrianZhou --
Changed lines 1-2 from:

What used to be called unslung packages, are now called optware packages. Although currently nslu2 is the only platform that officially supports native feed, optware covers a couple more platforms, native build may work on other Optware.Platforms in the future.

to:

What used to be called unslung packages, are now called optware packages. Although currently nslu2 is the only platform that officially supports native feed, optware covers a couple more platforms, native build may work on other Optware.Platforms in the future.

Changed lines 17-18 from:
  1. Native build is much slower than cross build, but native configure is accurate. So lots of cross compilable packages start as native only package. To help speed up native build of packages written in C, see Optware.Distcc.
to:
  1. Native build is much slower than cross build, but native configure is accurate. So lots of cross compilable packages start as native only package. To help speed up native build of packages written in C, see Optware.Distcc.
December 05, 2006, at 11:34 PM by BrianZhou --
Changed lines 1-2 from:

What used to be called unslung packages, are now called optware packages. Although currently nslu2 is the only platform that officially supports native feed, optware covers a couple more platforms, native build may work on other Optware/Platforms in the future.

to:

What used to be called unslung packages, are now called optware packages. Although currently nslu2 is the only platform that officially supports native feed, optware covers a couple more platforms, native build may work on other Optware.Platforms in the future.

Changed lines 11-12 from:

NOTE : This requires in excess of 150 Mb of disk sapce.

to:

NOTE : This requires in excess of 150 Mb of disk space.

Changed lines 17-18 from:
  1. Native build is much slower than cross build, but native configure is accurate. So lots of cross compilable packages start as native only package. To help speed up native build of packages written in C, see Optware/Distcc.
to:
  1. Native build is much slower than cross build, but native configure is accurate. So lots of cross compilable packages start as native only package. To help speed up native build of packages written in C, see Optware.Distcc.
December 05, 2006, at 11:32 PM by BrianZhou -- mentions distcc
Changed lines 1-2 from:

What used to be called unslung packages, are now called optware packages. Although currently nslu2 is the only platform that officially supports native feed, optware covers a couple more platforms.

to:

What used to be called unslung packages, are now called optware packages. Although currently nslu2 is the only platform that officially supports native feed, optware covers a couple more platforms, native build may work on other Optware/Platforms in the future.

Changed lines 7-9 from:
  1. Install the following packages: autoconf, automake, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, groff, libdb, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl and then crosstool-native\\
to:
  1. Install the development packages

ipkg install optware-devel to have the slug install all the development packages automatically.\\

Deleted lines 10-13:

or

ipkg install optware-devel to have the slug install them all for you automatically.
\\

Changed lines 15-16 from:
  1. Follow the normal Optware package build instructions (AddAPackageToOptware), except do it on the slug and skip openembedded-related monotone stuff. Those packages in COMMON_NATIVE_PACKAGES will only build natively at the moment. Most packages COMMON_CROSS_PACKAGES should also buildable natively.
to:
  1. Follow the normal Optware package build instructions (AddAPackageToOptware), except do it on the slug. Those packages in COMMON_NATIVE_PACKAGES will only build natively at the moment. Most packages in COMMON_CROSS_PACKAGES should also buildable natively.
  2. Native build is much slower than cross build, but native configure is accurate. So lots of cross compilable packages start as native only package. To help speed up native build of packages written in C, see Optware/Distcc.
December 05, 2006, at 11:22 PM by BrianZhou -- bring it more up to date
Added lines 1-4:

What used to be called unslung packages, are now called optware packages. Although currently nslu2 is the only platform that officially supports native feed, optware covers a couple more platforms.


Changed line 11 from:

ipkg install unslung-devel to have the slug install them all for you automatically.\\

to:

ipkg install optware-devel to have the slug install them all for you automatically.\\

Changed lines 17-18 from:
  1. Follow the normal Optware package build instructions (AddAPackageToOptware), except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment (i.e. the ones in CROSS_ONLY_PACKAGES will not build for the reasons documented in the Makefile, and the ones in UNSORTED_PACKAGES haven't really been tried yet). Failure to build natively is usually because there is some tool (like python) required to build the package, and that tool is not available on the slug yet.
to:
  1. Follow the normal Optware package build instructions (AddAPackageToOptware), except do it on the slug and skip openembedded-related monotone stuff. Those packages in COMMON_NATIVE_PACKAGES will only build natively at the moment. Most packages COMMON_CROSS_PACKAGES should also buildable natively.
November 16, 2006, at 01:55 AM by fcarolo -- reorganizing information about Optware packages
Changed lines 13-14 from:
  1. Follow the normal Unslung package build instructions (AddAPackageToUnslung), except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment (i.e. the ones in CROSS_ONLY_PACKAGES will not build for the reasons documented in the Makefile, and the ones in UNSORTED_PACKAGES haven't really been tried yet). Failure to build natively is usually because there is some tool (like python) required to build the package, and that tool is not available on the slug yet.
to:
  1. Follow the normal Optware package build instructions (AddAPackageToOptware), except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment (i.e. the ones in CROSS_ONLY_PACKAGES will not build for the reasons documented in the Makefile, and the ones in UNSORTED_PACKAGES haven't really been tried yet). Failure to build natively is usually because there is some tool (like python) required to build the package, and that tool is not available on the slug yet.
January 03, 2006, at 02:36 PM by akauppi -- made my mark on appweb
Changed lines 42-49 from:

All this came about to try and build php for appweb. I would also like to get appweb 2.0.0 building natively (or indeed cross).

to:

All this came about to try and build php for appweb. I would also like to get appweb 2.0.0 building natively (or indeed cross).


Also into building natively, and appWeb + PHP as the target (have it working now, v.2.0.3, just add export LD_LIBRARY_PATH=/opt/lib and it does load the modules).

Anyways, a nice, clean "ipkg install appweb" 2.0.4 version would be Nice to Have. Help appreciated.

-aka

May 24, 2005, at 07:39 PM by barrym --
Changed lines 1-3 from:
  1. Install Unslung 3.18-beta or later.
  2. Install the following packages: autoconf, automake, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, groff, libdb, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl\\
to:
  1. Install Unslung 4.20-beta or later.
  2. Install the following packages: autoconf, automake, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, groff, libdb, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl and then crosstool-native\\
Changed lines 7-11 from:

ipkg install unslung-devel to have the slug install them all for you automatically.

Is it worth pointing people that the ln-s hack to get more space in /opt?

  1. ipkg install crosstool-native (make sure that it installs 117MB of files)
to:

ipkg install unslung-devel to have the slug install them all for you automatically.

NOTE : This requires in excess of 150 Mb of disk sapce.

May 24, 2005, at 07:13 PM by barrym --
Changed lines 3-4 from:
  1. Install the following packages: autoconf, automake, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, groff, libdb, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl
to:
  1. Install the following packages: autoconf, automake, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, groff, libdb, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl

    or

    ipkg install unslung-devel to have the slug install them all for you automatically.
May 08, 2005, at 06:05 AM by MattMcNeill --
Changed line 36 from:
  • php - needed -lssl adding to the PHP_LDFLAGS in the make file since it wasn't being pulled up automatically. (this is currently compiling)
to:
  • php - needed -lssl adding to the PHP_LDFLAGS in the make file since it wasn't being pulled up automatically.
May 07, 2005, at 10:34 PM by MattMcNeill -- A list of packages compiled natively and any issues
Changed lines 10-39 from:
  1. Follow the normal Unslung package build instructions (AddAPackageToUnslung), except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment (i.e. the ones in CROSS_ONLY_PACKAGES will not build for the reasons documented in the Makefile, and the ones in UNSORTED_PACKAGES haven't really been tried yet). Failure to build natively is usually because there is some tool (like python) required to build the package, and that tool is not available on the slug yet.
to:
  1. Follow the normal Unslung package build instructions (AddAPackageToUnslung), except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment (i.e. the ones in CROSS_ONLY_PACKAGES will not build for the reasons documented in the Makefile, and the ones in UNSORTED_PACKAGES haven't really been tried yet). Failure to build natively is usually because there is some tool (like python) required to build the package, and that tool is not available on the slug yet.

I have been (perhaps a little eccentric) using the slug as my development linux box. For various reasons I have ended up compiling quite a few packages on it and thought I'd keep notes where I have come across issues:

  • openldap - ok
  • cyrus-sasl - ok
  • imap - ok
  • mysql - had to add a configure flag --with-low-memory to enable yacc components to build. Took about 18 hours in total.
  • readline - ok
  • ncurses - ok
  • libxslt - ok
  • libxml2 - ok
  • libgd - ok
  • fontconfig - ok
  • expat - ok
  • freetype - ok
  • libjpeg - ok
  • libpng - ok
  • libdb - ok
  • gdbm - ok
  • bzip2 - ok
  • libstdc++ - ok
  • openssl - ok
  • zlib - ok
  • php - needed -lssl adding to the PHP_LDFLAGS in the make file since it wasn't being pulled up automatically. (this is currently compiling)
  • appweb - the make file was messy for 1.2.3 and needed cleaning up. See the mailing list archives for details.

All this came about to try and build php for appweb. I would also like to get appweb 2.0.0 building natively (or indeed cross).

February 17, 2005, at 03:42 PM by rwhitby --
Changed line 3 from:
  1. Install the following packages: autoconf, automake, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, groff, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl
to:
  1. Install the following packages: autoconf, automake, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, groff, libdb, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl
February 06, 2005, at 07:33 AM by rwhitby --
Changed line 3 from:
  1. Install the following packages: autoconf, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, groff, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl
to:
  1. Install the following packages: autoconf, automake, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, groff, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl
February 03, 2005, at 01:08 PM by rwhitby --
Changed line 1 from:
  1. Install Unslung 3.18-beta or later (this should work with 3.17-beta as long as you have uname installed.)
to:
  1. Install Unslung 3.18-beta or later.
January 31, 2005, at 09:05 PM by paulhar --
Changed line 8 from:
  1. Make sure you are logged in as a normal user (you may need to create a new user). This is so an errant makefile cannot clobber your system files. Make sure that the user's shell is set to /opt/bin/bash, and add "export CVS_RSH=ssh" to that user's .bashrc
to:
  1. Make sure you are logged in as a normal user (you may need to create a new user). This is so an errant makefile cannot clobber your system files. Make sure that the user's shell is set to /opt/bin/bash, and add "export CVS_RSH=ssh" to that user's .profile
January 31, 2005, at 11:37 AM by rwhitby --
Changed line 10 from:
  1. Follow the normal Unslung package build instructions (AddAPackageToUnslung?), except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment (i.e. the ones in CROSS_ONLY_PACKAGES will not build for the reasons documented in the Makefile, and the ones in UNSORTED_PACKAGES haven't really been tried yet). Failure to build natively is usually because there is some tool (like python) required to build the package, and that tool is not available on the slug yet.
to:
  1. Follow the normal Unslung package build instructions (AddAPackageToUnslung), except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment (i.e. the ones in CROSS_ONLY_PACKAGES will not build for the reasons documented in the Makefile, and the ones in UNSORTED_PACKAGES haven't really been tried yet). Failure to build natively is usually because there is some tool (like python) required to build the package, and that tool is not available on the slug yet.
January 31, 2005, at 11:35 AM by rwhitby --
Deleted lines 0-3:

Is this line correct? i.e. if it's native compilation, then why do we need to cross compile?

[This HowTo is only for developers who are able to cross compile Unslung packages from source. If you can't do this, then don't bother reading any further. Until 3.18-beta is released, you will also have to build that from source too.]

Changed lines 8-12 from:

Why do you need to be a normal user? What is wrong with poor old root?

  1. Make sure you are logged in as a normal user (you may need to create a new user). Make sure that the user's shell is set to /opt/bin/bash, and add "export CVS_RSH=ssh" to that user's .bashrc

What "normal package build instructions"? Where why won't other packages work? What about programs just from source? More info here please!

to:
  1. Make sure you are logged in as a normal user (you may need to create a new user). This is so an errant makefile cannot clobber your system files. Make sure that the user's shell is set to /opt/bin/bash, and add "export CVS_RSH=ssh" to that user's .bashrc
Changed line 10 from:
  1. Follow the normal Unslung package build instructions, except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment.
to:
  1. Follow the normal Unslung package build instructions (AddAPackageToUnslung?), except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment (i.e. the ones in CROSS_ONLY_PACKAGES will not build for the reasons documented in the Makefile, and the ones in UNSORTED_PACKAGES haven't really been tried yet). Failure to build natively is usually because there is some tool (like python) required to build the package, and that tool is not available on the slug yet.
January 31, 2005, at 11:30 AM by rwhitby --
Changed line 7 from:
  1. Install the following packages: autoconf, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl
to:
  1. Install the following packages: autoconf, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, groff, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl
January 30, 2005, at 09:03 PM by rwhitby --
Changed line 7 from:
  1. Install the following packages: autoconf, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, libstdc++, m4, make, ncurses, openssh, patch, perl, tar, wget-ssl
to:
  1. Install the following packages: autoconf, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, libstdc++, m4, make, ncurses, openssh, patch, perl, sed, tar, wget-ssl
January 30, 2005, at 02:54 PM by rwhitby --
Changed line 7 from:
  1. Install the following packages: autoconf, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, libstdc++, m4, make, ncurses, openssl, patch, perl, tar, wget-ssl
to:
  1. Install the following packages: autoconf, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, libstdc++, m4, make, ncurses, openssh, patch, perl, tar, wget-ssl
January 29, 2005, at 06:16 PM by paulhar --
Added line 9:

Is it worth pointing people that the ln-s hack to get more space in /opt?

Added lines 11-12:

Why do you need to be a normal user? What is wrong with poor old root?

January 29, 2005, at 06:13 PM by paulhar --
Added lines 1-2:

Is this line correct? i.e. if it's native compilation, then why do we need to cross compile?

Changed line 5 from:
  1. Install Unslung 3.18-beta or later
to:
  1. Install Unslung 3.18-beta or later (this should work with 3.17-beta as long as you have uname installed.)
Added lines 12-13:

What "normal package build instructions"? Where why won't other packages work? What about programs just from source? More info here please!

January 27, 2005, at 12:36 PM by rwhitby --
Changed line 5 from:
  1. Install the following packages: autoconf, bash, bison, bzip2, coreutils, cvs, diffutils, findutils, flex, gawk, grep, m4, make, ncurses, openssl, patch, perl, tar, wget-ssl
to:
  1. Install the following packages: autoconf, bash, bison, bzip2, coreutils, cvs, diffutils, ed, findutils, flex, gawk, grep, libstdc++, m4, make, ncurses, openssl, patch, perl, tar, wget-ssl
January 27, 2005, at 09:24 AM by rwhitby --
Changed line 5 from:
  1. Install the following packages: bash, bison, bzip2, coreutils, cvs, diffutils, findutils, flex, gawk, grep, m4, make, ncurses, openssl, patch, tar, wget-ssl
to:
  1. Install the following packages: autoconf, bash, bison, bzip2, coreutils, cvs, diffutils, findutils, flex, gawk, grep, m4, make, ncurses, openssl, patch, perl, tar, wget-ssl
January 26, 2005, at 11:23 AM by rwhitby --
Changed line 7 from:
  1. Build and install crosstool-native.ipk
to:
  1. ipkg install crosstool-native (make sure that it installs 117MB of files)
January 19, 2005, at 09:57 AM by rwhitby --
Changed line 5 from:
  1. Install the following packages: bash, bison, bzip2, coreutils, cvs, diffutils, findutils, flex, gawk, grep, m4, make, ncurses, patch, tar
to:
  1. Install the following packages: bash, bison, bzip2, coreutils, cvs, diffutils, findutils, flex, gawk, grep, m4, make, ncurses, openssl, patch, tar, wget-ssl
January 17, 2005, at 12:30 PM by rwhitby --
Changed line 5 from:
  1. Install the following packages: bash, bison, bzip2, coreutils, cvs, diffutils, findutils, flex, gawk, grep, m4, make, patch, tar
to:
  1. Install the following packages: bash, bison, bzip2, coreutils, cvs, diffutils, findutils, flex, gawk, grep, m4, make, ncurses, patch, tar
January 17, 2005, at 10:52 AM by rwhitby --
Changed line 5 from:
  1. Install the following packages: bash, bison, bzip2, coreutils, cvs, diffutils, findutils, flex, gawk, grep, make, patch, tar
to:
  1. Install the following packages: bash, bison, bzip2, coreutils, cvs, diffutils, findutils, flex, gawk, grep, m4, make, patch, tar
January 17, 2005, at 09:01 AM by bobtm --
Changed line 1 from:

[This HowTo is only for developers who are able to cross compile Unslung packages from source. If you can't do this, then don't bother reading any further. Until 3.18-beta is released, you will also have to build that from source too.]

to:

[This HowTo is only for developers who are able to cross compile Unslung packages from source. If you can't do this, then don't bother reading any further. Until 3.18-beta is released, you will also have to build that from source too.]

January 17, 2005, at 04:59 AM by jacques --
Changed line 5 from:
  1. Install the following packages: bash, bzip2, coreutils, cvs, diffutils, findutils, gawk, grep, make, patch, tar
to:
  1. Install the following packages: bash, bison, bzip2, coreutils, cvs, diffutils, findutils, flex, gawk, grep, make, patch, tar
January 15, 2005, at 12:45 PM by rwhitby --
Changed line 5 from:
  1. Install the following packages: bash, coreutils, cvs, diffutils, findutils, gawk, grep, make, patch, tar
to:
  1. Install the following packages: bash, bzip2, coreutils, cvs, diffutils, findutils, gawk, grep, make, patch, tar
January 15, 2005, at 12:42 PM by rwhitby --
Added lines 5-6:
  1. Install the following packages: bash, coreutils, cvs, diffutils, findutils, gawk, grep, make, patch, tar
Deleted lines 7-8:
  1. Install the following packages: bash, coreutils, cvs, diffutils, findutils, gawk, grep, make, patch
January 15, 2005, at 10:55 AM by rwhitby --
Added lines 1-2:

[This HowTo is only for developers who are able to cross compile Unslung packages from source. If you can't do this, then don't bother reading any further. Until 3.18-beta is released, you will also have to build that from source too.]

January 15, 2005, at 10:53 AM by rwhitby --
Added line 2:
Changed lines 4-13 from:
  1. Install the following packages:
 * bash
 * coreutils
 * cvs
 * diffutils
 * findutils
 * gawk
 * grep
 * make
 * patch
to:
  1. Install the following packages: bash, coreutils, cvs, diffutils, findutils, gawk, grep, make, patch
Added line 8:
January 15, 2005, at 10:38 AM by rwhitby --
Changed lines 4-12 from:
  • bash
  • coreutils
  • cvs
  • diffutils
  • findutils
  • gawk
  • grep
  • make
  • patch
to:
 * bash
 * coreutils
 * cvs
 * diffutils
 * findutils
 * gawk
 * grep
 * make
 * patch
January 15, 2005, at 10:38 AM by rwhitby --
Deleted line 1:
Deleted line 2:
Deleted line 3:
Deleted line 12:
Deleted line 13:
January 15, 2005, at 10:37 AM by rwhitby --
Changed line 1 from:

+ Install Unslung 3.18-beta or later

to:
  1. Install Unslung 3.18-beta or later
Changed line 3 from:

+ Build and install crosstool-native.ipk

to:
  1. Build and install crosstool-native.ipk
Changed line 5 from:

+ Install the following packages:

to:
  1. Install the following packages:
Added line 10:
  • diffutils
Changed line 17 from:

+ Make sure you are logged in as a normal user (you may need to create a new user). Make sure that the user's shell is set to /opt/bin/bash, and add "export CVS_RSH=ssh" to that user's .bashrc

to:
  1. Make sure you are logged in as a normal user (you may need to create a new user). Make sure that the user's shell is set to /opt/bin/bash, and add "export CVS_RSH=ssh" to that user's .bashrc
Changed line 19 from:

+ Follow the normal Unslung package build instructions, except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment.

to:
  1. Follow the normal Unslung package build instructions, except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment.
January 15, 2005, at 10:08 AM by rwhitby --
Changed lines 1-18 from:
to:

+ Install Unslung 3.18-beta or later

+ Build and install crosstool-native.ipk

+ Install the following packages:

  • bash
  • coreutils
  • cvs
  • findutils
  • gawk
  • grep
  • make
  • patch

+ Make sure you are logged in as a normal user (you may need to create a new user). Make sure that the user's shell is set to /opt/bin/bash, and add "export CVS_RSH=ssh" to that user's .bashrc

+ Follow the normal Unslung package build instructions, except do it on the slug. Only those packages in CROSS_AND_NATIVE_PACKAGES or NATIVE_ONLY_PACKAGES will build natively at the moment.

view · edit · print · history · Last edited by SRS.
Based on work by BrianZhou, fcarolo, akauppi, barrym, MattMcNeill, rwhitby, paulhar, bobtm, and jacques.
Originally by rwhitby.
Page last modified on October 29, 2011, at 02:46 AM