Environment » Historial » Versió 17
Jorge L. Florit, 19-07-2013 15:49
| 1 | 12 | Victor Oncins | h1. Development Environment |
|---|---|---|---|
| 2 | 1 | Pau Escrich | |
| 3 | 14 | Pau Escrich | h3. Get the needed software |
| 4 | |||
| 5 | 15 | Simó Albert i Beltran | First of all you should take a look on the system requirements: |
| 6 | |||
| 7 | 2 | Pau Escrich | In a Debian based distributions (like Ubuntu), a set of packages are needed, you should install them: |
| 8 | 6 | Pau Escrich | |
| 9 | <pre> |
||
| 10 | 17 | Jorge L. Florit | sudo aptitude install \ |
| 11 | 10 | Simó Albert i Beltran | git subversion zlib1g-dev gawk flex unzip bzip2 gettext build-essential \ |
| 12 | 16 | Simó Albert i Beltran | libncurses5-dev libncursesw5-dev binutils cpp psmisc docbook-to-man |
| 13 | 1 | Pau Escrich | </pre> |
| 14 | 17 | Jorge L. Florit | |
| 15 | And if your machine is x86_64 you will need 32 bit development files. |
||
| 16 | In Debian/Ubuntu: |
||
| 17 | <pre>sudo aptitude install gcc-multilib</pre> |
||
| 18 | |||
| 19 | In CentOS/Fedora/RHEL the packets: |
||
| 20 | <pre>gcc.i686, libgcc.i686, and glibc-devel.i686</pre> |
||
| 21 | |||
| 22 | |||
| 23 | |||
| 24 | 14 | Pau Escrich | |
| 25 | h3. Get the code and compile |
||
| 26 | 1 | Pau Escrich | |
| 27 | 15 | Simó Albert i Beltran | * [Recomended] Get the qMp firmware generator using git: <pre>git clone git://qmp.cat/qmpfw.git qmpfw</pre> |
| 28 | 1 | Pau Escrich | |
| 29 | 15 | Simó Albert i Beltran | * [Outdated] Or get the code using http: <pre>wget -c -q -O - "http://qmp.cat/gitrevision_download?project_id=7&rev=anonymous" | tar zxvf -</pre> |
| 30 | |||
| 31 | 1 | Pau Escrich | * Then enter to source directory: <pre>cd qmpfw</pre> |
| 32 | |||
| 33 | 15 | Simó Albert i Beltran | * [Advanced] Do a checkout specifying the branch: <pre>make .checkout_qmp QMP_GIT_BRANCH=branch_name</pre> |
| 34 | |||
| 35 | Example for testing branch: <pre>make .checkout_qmp QMP_GIT_BRANCH=testing</pre> |
||
| 36 | 14 | Pau Escrich | |
| 37 | * And compile it specifying the target: <pre>make build T=alix</pre> |
||
| 38 | |||
| 39 | You can find available targets by executing: <pre>make list_targets</pre> |
||
| 40 | |||
| 41 | If you have more than one core in your computer you can use J=N: <pre>make build T=alix J=4</pre> |
||
| 42 | |||
| 43 | After that, you will find the images ready to install in your devices inside directory images/ |