PyMaemo/How to build - Revision history

imported_>amigadave: use `and tidy`


2010-06-23T12:46:36Z
use <code> and tidy

				
				
				
				
				
				← Older revision
				Revision as of 12:46, 23 June 2010
				
Line 1:
Line 1:
= How to build PyMaemo packages = 

== Introduction == 

To build PyMaemo packages from the source, you'll need: To build PyMaemo packages from the source, you'll need:



Line 45:
Line 41:
This will create the directory pymaemo-tools under $BASE. This will create the directory pymaemo-tools under $BASE.



Edit the fremantle-i386.cfg and fremantle-arm.cfg under $BASE/pymaemo-tools/sbdmock, Edit the <code>fremantle-i386.cfg</code> and <code>fremantle-arm.cfg</code> under $BASE/pymaemo-tools/sbdmock, putting the rootstrap path correspondent to each in the following key:
putting the rootstrap path correspondent to each in the following key: 
* i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz" * i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz"
* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz" * armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"



If you do not use the default FREMANTLE_ARMEL and FREMANTLE_X86 target names, you also need to change that on the .cfg files, in the config_opts['sbtarget'] entry. If you do not use the default <code>FREMANTLE_ARMEL</code> and <code>FREMANTLE_X86</code> target names, you also need to change that on the .cfg files, in the <code>config_opts['sbtarget']</code> entry.



You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files: You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files:
Line 56:
Line 51:
  deb http://repository.maemo.org/ fremantle/<token> nokia-binaries   deb http://repository.maemo.org/ fremantle/<token> nokia-binaries



As Maemo SDK needs some components from Nokia binaries repository, you probably already have a token in /etc/apt/sources.list inside Scratchbox. If you don't have a token, though, go to http://tablets-dev.nokia.com/eula/index.php and get one. As Maemo SDK needs some components from Nokia binaries repository, you probably already have a token in <code>/etc/apt/sources.list</code> inside Scratchbox. If you don't have a token, though, go to http://tablets-dev.nokia.com/eula/index.php and get one.



== Building == == Building ==
Line 64:
Line 59:
  $ ./build_packages.sh sbdmock:fremantle-i386 packages-fremantle.ini   $ ./build_packages.sh sbdmock:fremantle-i386 packages-fremantle.ini



The same can be done to ARMEL target, just replacing "i386" with "arm". The file packages_fremantle.ini contains all data necessary for obtaining the sources.   The same can be done to ARMEL target, just replacing "i386" with "arm". The file <code>packages_fremantle.ini</code> contains all data necessary for obtaining the sources.  



You can build individual packages too, specifying them as parameters. If you want to build only, let's say, pyopenssl and pycurl for the ARMEL target, run: You can build individual packages too, specifying them as parameters. If you want to build only, let's say, pyopenssl and pycurl for the ARMEL target, run:
Line 72:
Line 67:
Be advised that any PyMaemo dependency for these packages must be built first, as build_packages.sh will attempt to build only the packages provided at the command line. Be advised that any PyMaemo dependency for these packages must be built first, as build_packages.sh will attempt to build only the packages provided at the command line.



There are other options for the build; for more information, run build_packages.sh   There are other options for the build; for more information, run build_packages.sh with no parameters or refer to the README file inside pymaemo-tools.
with no parameters or refer to the README file inside pymaemo-tools. 



When the build finishes the resultant Debian packages will be placed at   When the build finishes the resultant Debian packages will be placed at $BASE/pymaemo-tools/workdir/fremantle_<target>/repo, where <target> is i386 or armel,and the build logs placed in $BASE/pymaemo-tools/workdir/fremantle_<target>/logs. From that point on, they can be installed on the targets and the ARMEL ones can be copied to the device to be installed there.
$BASE/pymaemo-tools/workdir/fremantle_<target>/repo, where <target> is i386 or armel,and the build logs placed in $BASE/pymaemo-tools/workdir/fremantle_<target>/logs. 
From that point on, they can be installed on the targets and the ARMEL ones 
can be copied to the device to be installed there. 



=== Directories created === === Directories created ===
Line 87:
Line 78:
== Adding your own packages to the build == == Adding your own packages to the build ==



If you want to add your own package to the build process, you just have to edit one file, packages-fremantle.ini. Just add an entry at the end of the file depending on how your package is organized. If you want to add your own package to the build process, you just have to edit one file, <code>packages-fremantle.ini</code>. Just add an entry at the end of the file depending on how your package is organized.



* If all the files of your package are contained in a single SVN or GIT repository, you just have to point to this repository, as the example below for python-conic: * If all the files of your package are contained in a single SVN or Git repository, you just have to point to this repository, as the example below for python-conic:
       
  [python-conic]   [python-conic]
Line 116:
Line 107:



# Create a clone of the repository at Gitorious for the package you want to modify, and git-clone it; # Create a clone of the repository at Gitorious for the package you want to modify, and git-clone it;
# Modify the packages-fremantle.ini entry of the package to point to the full path of the repository directory; # Modify the <code>packages-fremantle.ini</code> entry of the package to point to the full path of the repository directory;
# Modify the package and run build_packages.sh to build it; # Modify the package and run <code>build_packages.sh</code> to build it;
## Don't forget to erase your package files from $BASE/download_cache, $BASE/workdir and $BASE/workdir/fremantle_<target>/repo before the build; ## Don't forget to erase your package files from $BASE/download_cache, $BASE/workdir and $BASE/workdir/fremantle_<target>/repo before the build;
# Install on Scratchbox and on the device, if possible, and run all available unit tests for the package - needless to say, your modifications must not introduce regressions of any type; # Install on Scratchbox and on the device, if possible, and run all available unit tests for the package - needless to say, your modifications must not introduce regressions of any type;
Line 123:
Line 114:
# When you are satisfied with the results, push your local changes to your Gitorious clone and file a merge request. # When you are satisfied with the results, push your local changes to your Gitorious clone and file a merge request.



  If you want to modify a package that lives entirely on the Git repository, you can do anything you want, as all the files are under your control. However, if the package is taken from upstream, the only changes you can make will be located in the packaging - you'll have to use patches to actually modify any upstream file in build time.
If you want to modify a package that lives entirely on the GIT repository, you can do anything you want, as all the files are under your control. However, if the package is taken from upstream, the only changes you can make will be located in the packaging - you'll have to use patches to actually modify any upstream file in build time. 



== Tips == == Tips ==
Line 130:
Line 120:
=== Create a Debian repository with one line === === Create a Debian repository with one line ===



If you want to quickly make a Debian repository for easy installation,   If you want to quickly make a Debian repository for easy installation, run the following command at $BASE/pymaemo-tools/workdir/fremantle_<target>/repo:
run the following command at $BASE/pymaemo-tools/workdir/fremantle_<target>/repo: 



  $ apt-ftparchive packages . | gzip -9c > Packages.gz     $ apt-ftparchive packages . | gzip -9c > Packages.gz  



Now you have to expose the packages' path to the Web server and add the repository Now you have to expose the packages' path to the Web server and add the repository in the target machine accordingly.
in the target machine accordingly. 



=== Tracking build in real time === === Tracking build in real time ===



imported_>lizardo: /* Introduction */
2010-02-05T13:08:34Z
Introduction

				
				
				
				
				
				← Older revision
				Revision as of 13:08, 5 February 2010
				
Line 7:
Line 7:
* Maemo 5 SDK   * Maemo 5 SDK  
* Rootstraps for X86 and ARMEL targets * Rootstraps for X86 and ARMEL targets
* grep-dctrl * pymaemo-tools and its dependencies (listed on the README file)
* pymaemo-tools 



The scripts from pymaemo-tools are used to download packages' sources and build them using sbdmock, one at a time. sbdmock, in turn, uses the SDK and the rootstraps to create a clean environment for building every package. More information about sbdmock can be obtained [[Building_packages_with_sbdmock|here]], although pymaemo-tools uses a slightly modified of sbdmock - see pymaemo-tools README if you want to know which modifications were made. The scripts from pymaemo-tools are used to download packages' sources and build them using sbdmock, one at a time. sbdmock, in turn, uses the SDK and the rootstraps to create a clean environment for building every package. More information about sbdmock can be obtained [[Building_packages_with_sbdmock|here]], although pymaemo-tools uses a slightly modified of sbdmock - see pymaemo-tools README if you want to know which modifications were made.



imported_>lizardo: /* Configuration */
2010-02-05T13:02:39Z
Configuration

				
				
				
				
				
				← Older revision
				Revision as of 13:02, 5 February 2010
				
Line 51:
Line 51:
* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz" * armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"



If you do not use the default FREMANTLE_ARMEL and FREMANTLE_X86 target names, you need to also change that on the .cfg files, in the config_opts['sbtarget'] entry. If you do not use the default FREMANTLE_ARMEL and FREMANTLE_X86 target names, you also need to change that on the .cfg files, in the config_opts['sbtarget'] entry.



You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files: You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files:



imported_>lizardo: /* Configuration */
2010-02-05T13:01:38Z
Configuration

				
				
				
				
				
				← Older revision
				Revision as of 13:01, 5 February 2010
				
Line 50:
Line 50:
* i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz" * i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz"
* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz" * armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"

If you do not use the default FREMANTLE_ARMEL and FREMANTLE_X86 target names, you need to also change that on the .cfg files, in the config_opts['sbtarget'] entry.



You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files: You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files:



imported_>dneary: PyMaemo/HowToBuild moved to PyMaemo/How to build: Naming convention - no CamelCase
2010-01-29T16:08:47Z
PyMaemo/HowToBuild moved to PyMaemo/How to build: Naming convention - no CamelCase

				
				← Older revision
				Revision as of 16:08, 29 January 2010
				
(No difference)



imported_>bruno_araujo at 15:25, 28 January 2010
2010-01-28T15:25:15Z


				
				
				
				
				
				← Older revision
				Revision as of 15:25, 28 January 2010
				
Line 145:
Line 145:
* Build:   * Build:  
  $ tail -F $BASE/workdir/fremantle_<target>/repo/build.log   $ tail -F $BASE/workdir/fremantle_<target>/repo/build.log

[[Category:Python]]





imported_>bruno_araujo: /* Configuration */
2010-01-20T15:51:54Z
Configuration

				
				
				
				
				
				← Older revision
				Revision as of 15:51, 20 January 2010
				
Line 55:
Line 55:
  deb http://repository.maemo.org/ fremantle/<token> nokia-binaries   deb http://repository.maemo.org/ fremantle/<token> nokia-binaries



As Maemo SDK needs the Nokia binaries repository for some of its components, you probably already have a token in /etc/apt/sources.list inside Scratchbox. If you don't have a token, though, go to http://tablets-dev.nokia.com/eula/index.php and get one. As Maemo SDK needs some components from Nokia binaries repository, you probably already have a token in /etc/apt/sources.list inside Scratchbox. If you don't have a token, though, go to http://tablets-dev.nokia.com/eula/index.php and get one.



== Building == == Building ==



imported_>bruno_araujo: /* Configuration */
2010-01-20T15:40:38Z
Configuration

				
				
				
				
				
				← Older revision
				Revision as of 15:40, 20 January 2010
				
Line 50:
Line 50:
* i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz" * i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz"
* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz" * armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"

You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files:
 
 deb http://repository.maemo.org/ fremantle/<token> nokia-binaries

As Maemo SDK needs the Nokia binaries repository for some of its components, you probably already have a token in /etc/apt/sources.list inside Scratchbox. If you don't have a token, though, go to http://tablets-dev.nokia.com/eula/index.php and get one.



== Building == == Building ==



imported_>bruno_araujo at 21:56, 19 January 2010
2010-01-19T21:56:43Z


				
				
				
				
				
				← Older revision
				Revision as of 21:56, 19 January 2010
				
Line 1:
Line 1:
<b style="color: red">DRAFT</b> 

= How to build PyMaemo packages = = How to build PyMaemo packages =






imported_>bruno_araujo at 21:56, 19 January 2010
2010-01-19T21:56:26Z


				
				
				
				
				
				← Older revision
				Revision as of 21:56, 19 January 2010
				
Line 1:
Line 1:
<b style="color: red">DRAFT</b> <b style="color: red">DRAFT</b>



= How to build PyMaemo packages= = How to build PyMaemo packages =



== Introduction == == Introduction ==
Line 44:
Line 44:
Clone the pymaemo-tools project inside $BASE: Clone the pymaemo-tools project inside $BASE:



  $ git clone [git repo]   $ git clone git://gitorious.org/pymaemo/pymaemo-tools.git 



This will create the directory pymaemo-tools under $BASE. This will create the directory pymaemo-tools under $BASE.



Edit the fremantle_i386.cfg and fremantle_armel.cfg under $BASE/pymaemo-tools/sbdmock, Edit the fremantle-i386.cfg and fremantle-arm.cfg under $BASE/pymaemo-tools/sbdmock,
putting the rootstrap path correspondent to each in the following key: putting the rootstrap path correspondent to each in the following key:
* i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz" * i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz"
Line 57:
Line 57:
For building all the packages for the X86 target, enter $BASE/pymaemo-tools and run: For building all the packages for the X86 target, enter $BASE/pymaemo-tools and run:



  $ ./build_packages.sh sbdmock:fremantle_i386 packages_fremantle.ini   $ ./build_packages.sh sbdmock:fremantle-i386 packages-fremantle.ini



The same can be done to ARMEL target, just replacing "i386" with "armel". The file packages_fremantle.ini contains all data necessary for obtaining the sources.   The same can be done to ARMEL target, just replacing "i386" with "arm". The file packages_fremantle.ini contains all data necessary for obtaining the sources.  



You can build individual packages too, specifying them as parameters. If you want to build only, let's say, pyopenssl and pycurl for the ARMEL target, run: You can build individual packages too, specifying them as parameters. If you want to build only, let's say, pyopenssl and pycurl for the ARMEL target, run:



  $ ./build_packages.sh sbdmock:fremantle_armel packages_fremantle.ini pyopenssl,pycurl   $ ./build_packages.sh sbdmock:fremantle-arm packages-fremantle.ini pyopenssl,pycurl



Be advised that any PyMaemo dependency for these packages must be built first, as build_packages.sh will attempt to build only the packages provided at the command line. Be advised that any PyMaemo dependency for these packages must be built first, as build_packages.sh will attempt to build only the packages provided at the command line.
Line 77:
Line 77:
=== Directories created === === Directories created ===



* $BASE/pymaemo-tools/download_cache: all downloaded files are placed here, one directory by package, so you don't have to download everything again in every build. If the sources are updated, though, you will have to erase the corresponding entries on download_cache for allow them to be downloaded again. * $BASE/pymaemo-tools/download_cache: all downloaded files are placed here, one directory by package, so you don't have to download everything again at every build. If the sources are updated, though, you will have to erase the corresponding entries on ./download_cache and ./workdir for allow them to be downloaded again and rebuilt.
* $BASE/pymaemo-tools/workdir: the generated files (prepared sources, logs, built packages) are placed under this directory, grouped by the name of the sbdmock config file used to build them. Inside each group, the logs and repo directories will contain, respectively, the build logs and the built packages. * $BASE/pymaemo-tools/workdir: the generated files (prepared sources, logs, built packages) are placed under this directory, grouped by the name of the sbdmock config file used to build them. Inside each group, the logs and repo directories will contain, respectively, the build logs and the built packages.



Line 119:
Line 119:






As said before, there are two types of packages: native and taken from upstream.  If you want to modify a native package, you can do anything you want, as the entire package is contained in the repository. However, if the package is taken from upstream, the only changes you can make will be located in the packaging - you'll have to use patches to actually modify any upstream file in build time. If you want to modify a package that lives entirely on the GIT repository, you can do anything you want, as all the files are under your control. However, if the package is taken from upstream, the only changes you can make will be located in the packaging - you'll have to use patches to actually modify any upstream file in build time.



== Tips == == Tips ==



=== Create Debian repository with one line === === Create a Debian repository with one line ===



If you want to quickly make a Debian repository for easy installation,   If you want to quickly make a Debian repository for easy installation,

← Older revision		Revision as of 12:46, 23 June 2010
Line 1:		Line 1:
	~~= How to build PyMaemo packages =~~

	~~== Introduction ==~~

	To build PyMaemo packages from the source, you'll need:		To build PyMaemo packages from the source, you'll need:

Line 45:		Line 41:
	This will create the directory pymaemo-tools under $BASE.		This will create the directory pymaemo-tools under $BASE.

	Edit the fremantle-i386.cfg and fremantle-arm.cfg under $BASE/pymaemo-tools/sbdmock,		Edit the <code>fremantle-i386.cfg</code> and <code>fremantle-arm.cfg</code> under $BASE/pymaemo-tools/sbdmock, putting the rootstrap path correspondent to each in the following key:
	putting the rootstrap path correspondent to each in the following key:
	* i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz"		* i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz"
	* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"		* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"

	If you do not use the default FREMANTLE_ARMEL and FREMANTLE_X86 target names, you also need to change that on the .cfg files, in the config_opts['sbtarget'] entry.		If you do not use the default <code>FREMANTLE_ARMEL</code> and <code>FREMANTLE_X86</code> target names, you also need to change that on the .cfg files, in the <code>config_opts['sbtarget']</code> entry.

	You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files:		You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files:
Line 56:		Line 51:
	deb http://repository.maemo.org/ fremantle/<token> nokia-binaries		deb http://repository.maemo.org/ fremantle/<token> nokia-binaries

	As Maemo SDK needs some components from Nokia binaries repository, you probably already have a token in /etc/apt/sources.list inside Scratchbox. If you don't have a token, though, go to http://tablets-dev.nokia.com/eula/index.php and get one.		As Maemo SDK needs some components from Nokia binaries repository, you probably already have a token in <code>/etc/apt/sources.list</code> inside Scratchbox. If you don't have a token, though, go to http://tablets-dev.nokia.com/eula/index.php and get one.

	== Building ==		== Building ==
Line 64:		Line 59:
	$ ./build_packages.sh sbdmock:fremantle-i386 packages-fremantle.ini		$ ./build_packages.sh sbdmock:fremantle-i386 packages-fremantle.ini

	The same can be done to ARMEL target, just replacing "i386" with "arm". The file packages_fremantle.ini contains all data necessary for obtaining the sources.		The same can be done to ARMEL target, just replacing "i386" with "arm". The file <code>packages_fremantle.ini</code> contains all data necessary for obtaining the sources.

	You can build individual packages too, specifying them as parameters. If you want to build only, let's say, pyopenssl and pycurl for the ARMEL target, run:		You can build individual packages too, specifying them as parameters. If you want to build only, let's say, pyopenssl and pycurl for the ARMEL target, run:
Line 72:		Line 67:
	Be advised that any PyMaemo dependency for these packages must be built first, as build_packages.sh will attempt to build only the packages provided at the command line.		Be advised that any PyMaemo dependency for these packages must be built first, as build_packages.sh will attempt to build only the packages provided at the command line.

	There are other options for the build; for more information, run build_packages.sh		There are other options for the build; for more information, run build_packages.sh with no parameters or refer to the README file inside pymaemo-tools.
	with no parameters or refer to the README file inside pymaemo-tools.

	When the build finishes the resultant Debian packages will be placed at		When the build finishes the resultant Debian packages will be placed at $BASE/pymaemo-tools/workdir/fremantle_<target>/repo, where <target> is i386 or armel,and the build logs placed in $BASE/pymaemo-tools/workdir/fremantle_<target>/logs. From that point on, they can be installed on the targets and the ARMEL ones can be copied to the device to be installed there.
	$BASE/pymaemo-tools/workdir/fremantle_<target>/repo, where <target> is i386 or armel,and the build logs placed in $BASE/pymaemo-tools/workdir/fremantle_<target>/logs.
	From that point on, they can be installed on the targets and the ARMEL ones
	can be copied to the device to be installed there.

	=== Directories created ===		=== Directories created ===
Line 87:		Line 78:
	== Adding your own packages to the build ==		== Adding your own packages to the build ==

	If you want to add your own package to the build process, you just have to edit one file, packages-fremantle.ini. Just add an entry at the end of the file depending on how your package is organized.		If you want to add your own package to the build process, you just have to edit one file, <code>packages-fremantle.ini</code>. Just add an entry at the end of the file depending on how your package is organized.

	* If all the files of your package are contained in a single SVN or ~~GIT~~ repository, you just have to point to this repository, as the example below for python-conic:		* If all the files of your package are contained in a single SVN or Git repository, you just have to point to this repository, as the example below for python-conic:

	[python-conic]		[python-conic]
Line 116:		Line 107:

	# Create a clone of the repository at Gitorious for the package you want to modify, and git-clone it;		# Create a clone of the repository at Gitorious for the package you want to modify, and git-clone it;
	# Modify the packages-fremantle.ini entry of the package to point to the full path of the repository directory;		# Modify the <code>packages-fremantle.ini</code> entry of the package to point to the full path of the repository directory;
	# Modify the package and run build_packages.sh to build it;		# Modify the package and run <code>build_packages.sh</code> to build it;
	## Don't forget to erase your package files from $BASE/download_cache, $BASE/workdir and $BASE/workdir/fremantle_<target>/repo before the build;		## Don't forget to erase your package files from $BASE/download_cache, $BASE/workdir and $BASE/workdir/fremantle_<target>/repo before the build;
	# Install on Scratchbox and on the device, if possible, and run all available unit tests for the package - needless to say, your modifications must not introduce regressions of any type;		# Install on Scratchbox and on the device, if possible, and run all available unit tests for the package - needless to say, your modifications must not introduce regressions of any type;
Line 123:		Line 114:
	# When you are satisfied with the results, push your local changes to your Gitorious clone and file a merge request.		# When you are satisfied with the results, push your local changes to your Gitorious clone and file a merge request.

			If you want to modify a package that lives entirely on the Git repository, you can do anything you want, as all the files are under your control. However, if the package is taken from upstream, the only changes you can make will be located in the packaging - you'll have to use patches to actually modify any upstream file in build time.
	If you want to modify a package that lives entirely on the ~~GIT~~ repository, you can do anything you want, as all the files are under your control. However, if the package is taken from upstream, the only changes you can make will be located in the packaging - you'll have to use patches to actually modify any upstream file in build time.

	== Tips ==		== Tips ==
Line 130:		Line 120:
	=== Create a Debian repository with one line ===		=== Create a Debian repository with one line ===

	If you want to quickly make a Debian repository for easy installation,		If you want to quickly make a Debian repository for easy installation, run the following command at $BASE/pymaemo-tools/workdir/fremantle_<target>/repo:
	run the following command at $BASE/pymaemo-tools/workdir/fremantle_<target>/repo:

	$ apt-ftparchive packages . \| gzip -9c > Packages.gz		$ apt-ftparchive packages . \| gzip -9c > Packages.gz

	Now you have to expose the packages' path to the Web server and add the repository		Now you have to expose the packages' path to the Web server and add the repository in the target machine accordingly.
	in the target machine accordingly.

	=== Tracking build in real time ===		=== Tracking build in real time ===

← Older revision		Revision as of 13:08, 5 February 2010
Line 7:		Line 7:
	* Maemo 5 SDK		* Maemo 5 SDK
	* Rootstraps for X86 and ARMEL targets		* Rootstraps for X86 and ARMEL targets
	* grep-dctrl		* pymaemo-tools and its dependencies (listed on the README file)
	* pymaemo-tools

	The scripts from pymaemo-tools are used to download packages' sources and build them using sbdmock, one at a time. sbdmock, in turn, uses the SDK and the rootstraps to create a clean environment for building every package. More information about sbdmock can be obtained [[Building_packages_with_sbdmock\|here]], although pymaemo-tools uses a slightly modified of sbdmock - see pymaemo-tools README if you want to know which modifications were made.		The scripts from pymaemo-tools are used to download packages' sources and build them using sbdmock, one at a time. sbdmock, in turn, uses the SDK and the rootstraps to create a clean environment for building every package. More information about sbdmock can be obtained [[Building_packages_with_sbdmock\|here]], although pymaemo-tools uses a slightly modified of sbdmock - see pymaemo-tools README if you want to know which modifications were made.

← Older revision		Revision as of 13:02, 5 February 2010
Line 51:		Line 51:
	* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"		* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"

	If you do not use the default FREMANTLE_ARMEL and FREMANTLE_X86 target names, you need to ~~also~~ change that on the .cfg files, in the config_opts['sbtarget'] entry.		If you do not use the default FREMANTLE_ARMEL and FREMANTLE_X86 target names, you also need to change that on the .cfg files, in the config_opts['sbtarget'] entry.

	You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files:		You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files:

← Older revision		Revision as of 13:01, 5 February 2010
Line 50:		Line 50:
	* i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz"		* i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz"
	* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"		* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"

			If you do not use the default FREMANTLE_ARMEL and FREMANTLE_X86 target names, you need to also change that on the .cfg files, in the config_opts['sbtarget'] entry.

	You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files:		You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files:

← Older revision	Revision as of 16:08, 29 January 2010
(No difference)

← Older revision		Revision as of 15:25, 28 January 2010
Line 145:		Line 145:
	* Build:		* Build:
	$ tail -F $BASE/workdir/fremantle_<target>/repo/build.log		$ tail -F $BASE/workdir/fremantle_<target>/repo/build.log

			[[Category:Python]]

← Older revision		Revision as of 15:51, 20 January 2010
Line 55:		Line 55:
	deb http://repository.maemo.org/ fremantle/<token> nokia-binaries		deb http://repository.maemo.org/ fremantle/<token> nokia-binaries

	As Maemo SDK needs ~~the~~ Nokia binaries repository ~~for some of its components~~, you probably already have a token in /etc/apt/sources.list inside Scratchbox. If you don't have a token, though, go to http://tablets-dev.nokia.com/eula/index.php and get one.		As Maemo SDK needs some components from Nokia binaries repository, you probably already have a token in /etc/apt/sources.list inside Scratchbox. If you don't have a token, though, go to http://tablets-dev.nokia.com/eula/index.php and get one.

	== Building ==		== Building ==

← Older revision		Revision as of 15:40, 20 January 2010
Line 50:		Line 50:
	* i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz"		* i386: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_i386.tgz"
	* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"		* armel: config_opts['rootstrap'] = "$BASE/rootstraps/maemo-sdk-rootstrap_5.0_armel.tgz"

			You'll need the Nokia binaries repository for building some packages, just add the correspondent line to the config_opts['sources.list'] entry of the .cfg files:

			deb http://repository.maemo.org/ fremantle/<token> nokia-binaries

			As Maemo SDK needs the Nokia binaries repository for some of its components, you probably already have a token in /etc/apt/sources.list inside Scratchbox. If you don't have a token, though, go to http://tablets-dev.nokia.com/eula/index.php and get one.

	== Building ==		== Building ==

← Older revision		Revision as of 21:56, 19 January 2010
Line 1:		Line 1:
	~~<b style="color: red">DRAFT</b>~~

	= How to build PyMaemo packages =		= How to build PyMaemo packages =

PyMaemo/How to build - Revision history

imported_>amigadave: use and tidy

imported_>lizardo: /* Introduction */

imported_>lizardo: /* Configuration */

imported_>lizardo: /* Configuration */

imported_>dneary: PyMaemo/HowToBuild moved to PyMaemo/How to build: Naming convention - no CamelCase

imported_>bruno_araujo at 15:25, 28 January 2010

imported_>bruno_araujo: /* Configuration */

imported_>bruno_araujo: /* Configuration */

imported_>bruno_araujo at 21:56, 19 January 2010

imported_>bruno_araujo at 21:56, 19 January 2010

imported_>amigadave: use `and tidy`