-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
On Thursday 06 November 2014 06.29:49 Michele
Calgaro wrote:
Nightly builds are being rebuilt for RC1, but
(...) I am writing from
such a
system, since I build all packages on my own
:-) )
Cheers
Michele
I'm not very experienced, but what is necessary to build packages? I
assume
one must get the source code, but what then? Is it possible with the tools
provided by a standard distribution, what should I understand to manage
such
a task?
In general you want to do major development on a dedicated system (one
that you can wipe/reload if needed) due to the possibility of breaking
core components of TDE. I'd recommend at least a dual-core machine with
several GB of RAM as well.
- From the software side, a standard Debian/Ubuntu install is a good base.
You can install the base development packages with 'apt-get install
build-essential git', and install the build dependencies for a specific
package with 'apt-get build-dep <package name>'.
After a development system is set up, I like to hack on TDE packages with
the following method:
mkdir ~/TEMP
cd ~/TEMP
apt-get source <package name-trinity>
rm *
git clone https://<git username>(a)scm.trinitydesktop.org/scm/git/<package
name>
mv <package-name>/.git <package-name-revid-folder>
rm -rf package-name
cd <package-name-revid-folder>
dpkg-buildpackage -r fakeroot -b
That last command kicks off the build process; when done you get a series
of .debs in the folder above the source tree. However, you don't have to
rerun that to build most changes you make to the source after the initial
build, usually you can just:
<edit sources>
cd obj-*
make install
<test>
<edit sources>
make install
<repeat>
Hope this helps some!
Tim
Hi, Tim already posted some very good instructions.
I just add that after v14.0.0 is released, we are planning to add some building scripts to
the TDE repository for
Debian/Ubuntu to help anyone who wants to build their own packages to get started. Just
keep in mind that TDE is huge
and if you use the current sources it gets broken from time to time by changes in other
packages provided by the
distribution (especially on a rolling distribution like Jessie), so sometimes you will
have to do some fix-up or wait
for a fix-up to appear on the GIT sources.
Cheers
Michele