Skip to content

Commit 866760b

Browse files
author
timlinux
committedJun 10, 2007
Fixed some more formatting glitches
git-svn-id: http://svn.osgeo.org/qgis/branches/Release-0_8_0@7003 c8812cc2-4d05-0410-92ff-de0c093fc19c
·
final-0_8_1Release-0_8_1
1 parent a1966be commit 866760b

File tree

2 files changed

+267
-256
lines changed

2 files changed

+267
-256
lines changed
 

‎INSTALL

Lines changed: 136 additions & 128 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,8 @@ Tim Sutton 2007
4848
4.6. Setup ccache (Optional)
4949
4.7. Prepare your development environment
5050
4.8. Check out the QGIS Source Code
51+
4.9. Starting the compile
52+
4.10. Running QGIS
5153
5. Further help and information
5254
6. Authors and Acknowledgments
5355

@@ -207,7 +209,8 @@ Start a cmd.exe window ( Start -> Run -> cmd.exe ) Create development
207209
directory and move into it
208210

209211

210-
md c:\dev\cpp cd c:\dev\cpp
212+
md c:\dev\cpp
213+
cd c:\dev\cpp
211214

212215

213216
Check out sources from SVN For svn head:
@@ -240,7 +243,9 @@ properties so you can just type qtvars.bat when you open the cmd console.
240243
Create build directory and set it as current directory:
241244

242245

243-
cd c:\dev\cpp\qgis md build cd build
246+
cd c:\dev\cpp\qgis
247+
md build
248+
cd build
244249

245250

246251

@@ -251,10 +256,10 @@ Create build directory and set it as current directory:
251256
cmakesetup ..
252257

253258

254-
/!\ NOTE: You must include the '..' above.
259+
/!\ NOTE: You must include the '..' above.
255260

256261
Click 'Configure' button. When asked, you should choose 'MinGW Makefiles'
257-
as generator.
262+
as generator.
258263

259264
There's a problem with MinGW Makefiles on Win2K. If you're compiling on this
260265
platform, use 'MSYS Makefiles' generator instead.
@@ -652,184 +657,187 @@ to you.
652657
The packages qgis depends on to build are available in the "universe" component
653658
of Ubuntu. This is not activated by default, so you need to activate it:
654659

655-
1. Edit your /etc/apt/sources.list file. 2. Uncomment the all the lines
656-
starting with "deb"
660+
1. Edit your /etc/apt/sources.list file.
661+
2. Uncomment the all the lines starting with "deb"
662+
663+
Also you will need to be running (K)Ubuntu 'edgy' or higher in order for
664+
all dependencies to be met.
665+
666+
Now update your local sources database:
657667

658-
Also you will need to be running (K)Ubuntu 'edgy' in order for all
659-
dependencies to be met.
660668

661-
Now update your local sources database:
669+
sudo apt-get update
662670

663-
```
664-
sudo apt-get update
665-
```
666671

667672

668673
4.3. Install Qt4
669674
================
670675

671-
```
672-
sudo apt-get install libqt4-core libqt4-debug libqt4-debug-dev \
673-
libqt4-dev libqt4-gui libqt4-qt3support libqt4-sql lsb-qt4 qt4-designer \
674-
qt4-dev-tools qt4-doc qt4-qtconfig uim-qt gcc libapt-pkg-perl resolvconf
675-
```
676-
677-
/!\ *A Special Note:* If you are following this set of instructions on
678-
a system where you already have Qt3 development tools installed, there will
679-
be a conflict between Qt3 tools and Qt4 tools. For example, qmake will
680-
point to the Qt3 version not the Qt4. Ubuntu Qt4 and Qt3 packages are
681-
designed to live alongside each other. This means that for example if you
682-
have them both installed you will have three qmake exe's:
683-
684-
```
685-
/usr/bin/qmake -> /etc/alternatives/qmake
686-
/usr/bin/qmake-qt3
687-
/usr/bin/qmake-qt4
688-
```
689-
690-
The same applies to all other Qt binaries. You will notice above that the
691-
canonical 'qmake' is managed by apt alternatives, so before we start to
692-
build QGIS, we need to make Qt4 the default. To return Qt3 to default later
693-
you can use this same process.
694-
695-
You can use apt alternatives to correct this so that the Qt4 version of
696-
applications is used in all cases:
697-
698-
```
699-
sudo update-alternatives --config qmake
700-
sudo update-alternatives --config uic
701-
sudo update-alternatives --config designer
702-
sudo update-alternatives --config assistant
703-
sudo update-alternatives --config qtconfig
704-
sudo update-alternatives --config moc
705-
sudo update-alternatives --config lupdate
706-
sudo update-alternatives --config lrelease
707-
sudo update-alternatives --config linguist
708-
```
709-
710-
Use the simple command line dialog that appears after running each of the
711-
above commands to select the Qt4 version of the relevant applications.
676+
677+
sudo apt-get install libqt4-core libqt4-debug libqt4-debug-dev \
678+
libqt4-dev libqt4-gui libqt4-qt3support libqt4-sql lsb-qt4 qt4-designer \
679+
qt4-dev-tools qt4-doc qt4-qtconfig uim-qt gcc libapt-pkg-perl resolvconf
680+
681+
682+
/!\ *A Special Note:* If you are following this set of instructions on
683+
a system where you already have Qt3 development tools installed, there will
684+
be a conflict between Qt3 tools and Qt4 tools. For example, qmake will
685+
point to the Qt3 version not the Qt4. Ubuntu Qt4 and Qt3 packages are
686+
designed to live alongside each other. This means that for example if you
687+
have them both installed you will have three qmake exe's:
688+
689+
690+
/usr/bin/qmake -> /etc/alternatives/qmake
691+
/usr/bin/qmake-qt3
692+
/usr/bin/qmake-qt4
693+
694+
695+
The same applies to all other Qt binaries. You will notice above that the
696+
canonical 'qmake' is managed by apt alternatives, so before we start to
697+
build QGIS, we need to make Qt4 the default. To return Qt3 to default later
698+
you can use this same process.
699+
700+
You can use apt alternatives to correct this so that the Qt4 version of
701+
applications is used in all cases:
702+
703+
704+
sudo update-alternatives --config qmake
705+
sudo update-alternatives --config uic
706+
sudo update-alternatives --config designer
707+
sudo update-alternatives --config assistant
708+
sudo update-alternatives --config qtconfig
709+
sudo update-alternatives --config moc
710+
sudo update-alternatives --config lupdate
711+
sudo update-alternatives --config lrelease
712+
sudo update-alternatives --config linguist
713+
714+
715+
Use the simple command line dialog that appears after running each of the
716+
above commands to select the Qt4 version of the relevant applications.
712717

713718

714719
4.4. Install additional software dependencies required by QGIS
715720
==============================================================
716721

717-
```
718-
sudo apt-get install gdal-bin libgdal1-dev libgeos-dev proj libtool \
719-
libgdal-doc libhdf4g-dev libhdf4g-run autoconf2.13 automake1.9 python-dev \
720-
swig libgsl0-dev g++ libjasper-1.701-dev libtiff4-dev subversion gsl-bin \
721-
libsqlite3-dev sqlite3 ccache make libpq-dev flex bison firefox
722-
```
722+
723+
sudo apt-get install gdal-bin libgdal1-dev libgeos-dev proj libtool \
724+
libgdal-doc libhdf4g-dev libhdf4g-run autoconf2.13 automake1.9 python-dev \
725+
swig libgsl0-dev g++ libjasper-1.701-dev libtiff4-dev subversion gsl-bin \
726+
libsqlite3-dev sqlite3 ccache make libpq-dev flex bison firefox
727+
723728

724729

725730
4.5. GRASS Specific Steps
726731
=========================
727732

728-
/!\ *Note:* If you don't need to build with GRASS support, you can
729-
skip this section.
733+
/!\ *Note:* If you don't need to build with GRASS support, you can
734+
skip this section.
735+
736+
Now you can install grass from dapper:
737+
730738

731-
Now you can install grass from dapper:
739+
sudo apt-get install grass libgrass-dev libgdal1-grass
732740

733-
```
734-
sudo apt-get install grass libgrass-dev libgdal1-grass
735-
```
736741

737742

738743
4.6. Setup ccache (Optional)
739744
============================
740745

741-
You should also setup ccache to speed up compile times:
746+
You should also setup ccache to speed up compile times:
747+
748+
749+
cd /usr/local/bin
750+
sudo ln -s /usr/bin/ccache gcc
751+
sudo ln -s /usr/bin/ccache g++
742752

743-
```
744-
cd /usr/local/bin
745-
sudo ln -s /usr/bin/ccache gcc
746-
sudo ln -s /usr/bin/ccache g++
747-
```
748753

749754

750755
4.7. Prepare your development environment
751756
=========================================
752757

753-
As a convention I do all my development work in $HOME/dev/<language>, so in
754-
this case we will create a work environment for C++ development work like
755-
this:
758+
As a convention I do all my development work in $HOME/dev/<language>, so in
759+
this case we will create a work environment for C++ development work like
760+
this:
761+
762+
763+
mkdir -p ${HOME}/dev/cpp
764+
cd ${HOME}/dev/cpp
756765

757-
```
758-
mkdir -p ${HOME}/dev/cpp
759-
cd ${HOME}/dev/cpp
760-
```
761766

762-
This directory path will be assumed for all instructions that follow.
767+
This directory path will be assumed for all instructions that follow.
763768

764769

765770
4.8. Check out the QGIS Source Code
766771
===================================
767772

768-
There are two ways the source can be checked out. Use the anonymous method
769-
if you do not have edit privaleges for the QGIS source repository, or use
770-
the developer checkout if you have permissions to commit source code
771-
changes.
773+
There are two ways the source can be checked out. Use the anonymous method
774+
if you do not have edit privaleges for the QGIS source repository, or use
775+
the developer checkout if you have permissions to commit source code
776+
changes.
777+
778+
1. Anonymous Checkout
779+
780+
781+
cd ${HOME}/dev/cpp
782+
svn co https://svn.qgis.org/repos/qgis/trunk/qgis qgis
783+
772784

773-
1. Anonymous Checkout
785+
2. Developer Checkout
774786

775-
```
776-
cd ${HOME}/dev/cpp
777-
svn co https://svn.qgis.org/repos/qgis/trunk/qgis qgis
778-
```
779787

780-
2. Developer Checkout
788+
cd ${HOME}/dev/cpp
789+
svn co --username <yourusername> https://svn.qgis.org/repos/qgis/trunk/qgis qgis
781790

782-
```
783-
cd ${HOME}/dev/cpp
784-
svn co --username <yourusername> https://svn.qgis.org/repos/qgis/trunk/qgis qgis
785-
```
786791

787-
The first time you check out the source you will be prompted to accept the
788-
qgis.org certificate. Press 'p' to accept it permanently:
792+
The first time you check out the source you will be prompted to accept the
793+
qgis.org certificate. Press 'p' to accept it permanently:
789794

790-
```
791-
Error validating server certificate for 'https://svn.qgis.org:443':
792795

793-
- The certificate is not issued by a trusted authority. Use the
794-
fingerprint to validate the certificate manually! Certificate
795-
information:
796-
- Hostname: svn.qgis.org
797-
- Valid: from Apr 1 00:30:47 2006 GMT until Mar 21 00:30:47 2008 GMT
798-
- Issuer: Developer Team, Quantum GIS, Anchorage, Alaska, US
799-
- Fingerprint:
800-
2f:cd:f1:5a:c7:64:da:2b:d1:34:a5:20:c6:15:67:28:33:ea:7a:9b (R)eject,
801-
accept (t)emporarily or accept (p)ermanently?
802-
```
796+
Error validating server certificate for 'https://svn.qgis.org:443':
797+
- The certificate is not issued by a trusted authority. Use the
798+
fingerprint to validate the certificate manually! Certificate
799+
information:
800+
- Hostname: svn.qgis.org
801+
- Valid: from Apr 1 00:30:47 2006 GMT until Mar 21 00:30:47 2008 GMT
802+
- Issuer: Developer Team, Quantum GIS, Anchorage, Alaska, US
803+
- Fingerprint:
804+
2f:cd:f1:5a:c7:64:da:2b:d1:34:a5:20:c6:15:67:28:33:ea:7a:9b (R)eject,
805+
accept (t)emporarily or accept (p)ermanently?
803806

804-
== Starting the compile ==
805807

806-
I compile my development version of QGIS into my ~/apps directory to avoid
807-
conflicts with Ubuntu packages that may be under /usr. This way for example
808-
you can use the binary packages of QGIS on your system along side with your
809-
development version. I suggest you do something similar:
810808

811-
```
812-
mkdir -p ${HOME}/apps
813-
```
809+
4.9. Starting the compile
810+
=========================
811+
812+
I compile my development version of QGIS into my ~/apps directory to avoid
813+
conflicts with Ubuntu packages that may be under /usr. This way for example
814+
you can use the binary packages of QGIS on your system along side with your
815+
development version. I suggest you do something similar:
816+
817+
818+
mkdir -p ${HOME}/apps
819+
820+
821+
The script will carry on to build QGIS - it may take a little while to go
822+
and have a cup of your favourite beverage while you wait...
823+
824+
825+
4.10. Running QGIS
826+
==================
814827

815-
The script will carry on to build QGIS - it may take a little while to go
816-
and have a cup of your favourite beverage while you wait...
828+
Once the compile is complete it should pop up a page in firefox with unit
829+
test results. At the time of writing the unit tests are just stubs - we
830+
still need to create the test implementations - so dont worry to much about
831+
their output at the moment.
817832

818-
== Running QGIS ==
833+
Now you can try to run QGIS:
819834

820-
Once the compile is complete it should pop up a page in firefox with unit
821-
test results. At the time of writing the unit tests are just stubs - we
822-
still need to create the test implementations - so dont worry to much about
823-
their output at the moment.
824835

825-
Now you can try to run QGIS:
836+
$HOME/apps/bin/qgis
826837

827-
```
828-
$HOME/apps/bin/qgis
829-
```
830838

831-
If all has worked properly the QGIS application should start up and appear
832-
on your screen.
839+
If all has worked properly the QGIS application should start up and appear
840+
on your screen.
833841

834842

835843
5. Further help and information

‎INSTALL.t2t

Lines changed: 131 additions & 128 deletions
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,8 @@ Start a cmd.exe window ( Start -> Run -> cmd.exe ) Create development
154154
directory and move into it
155155

156156
```
157-
md c:\dev\cpp cd c:\dev\cpp
157+
md c:\dev\cpp
158+
cd c:\dev\cpp
158159
```
159160

160161
Check out sources from SVN For svn head:
@@ -185,7 +186,9 @@ Create build directory and set it as current directory:
185186

186187

187188
```
188-
cd c:\dev\cpp\qgis md build cd build
189+
cd c:\dev\cpp\qgis
190+
md build
191+
cd build
189192
```
190193

191194
== Configuration ==
@@ -194,10 +197,10 @@ cd c:\dev\cpp\qgis md build cd build
194197
cmakesetup ..
195198
```
196199

197-
/!\ NOTE: You must include the '..' above.
200+
/!\ NOTE: You must include the '..' above.
198201

199202
Click 'Configure' button. When asked, you should choose 'MinGW Makefiles'
200-
as generator.
203+
as generator.
201204

202205
There's a problem with MinGW Makefiles on Win2K. If you're compiling on this
203206
platform, use 'MSYS Makefiles' generator instead.
@@ -564,174 +567,174 @@ to you.
564567
The packages qgis depends on to build are available in the "universe" component
565568
of Ubuntu. This is not activated by default, so you need to activate it:
566569

567-
1. Edit your /etc/apt/sources.list file. 2. Uncomment the all the lines
568-
starting with "deb"
570+
1. Edit your /etc/apt/sources.list file.
571+
2. Uncomment the all the lines starting with "deb"
569572

570-
Also you will need to be running (K)Ubuntu 'edgy' in order for all
571-
dependencies to be met.
573+
Also you will need to be running (K)Ubuntu 'edgy' or higher in order for
574+
all dependencies to be met.
572575

573-
Now update your local sources database:
576+
Now update your local sources database:
574577

575-
```
576-
sudo apt-get update
577-
```
578+
```
579+
sudo apt-get update
580+
```
578581

579582

580-
== Install Qt4 ==
583+
== Install Qt4 ==
581584

582-
```
583-
sudo apt-get install libqt4-core libqt4-debug libqt4-debug-dev \
584-
libqt4-dev libqt4-gui libqt4-qt3support libqt4-sql lsb-qt4 qt4-designer \
585-
qt4-dev-tools qt4-doc qt4-qtconfig uim-qt gcc libapt-pkg-perl resolvconf
586-
```
585+
```
586+
sudo apt-get install libqt4-core libqt4-debug libqt4-debug-dev \
587+
libqt4-dev libqt4-gui libqt4-qt3support libqt4-sql lsb-qt4 qt4-designer \
588+
qt4-dev-tools qt4-doc qt4-qtconfig uim-qt gcc libapt-pkg-perl resolvconf
589+
```
587590

588-
/!\ ***A Special Note:*** If you are following this set of instructions on
589-
a system where you already have Qt3 development tools installed, there will
590-
be a conflict between Qt3 tools and Qt4 tools. For example, qmake will
591-
point to the Qt3 version not the Qt4. Ubuntu Qt4 and Qt3 packages are
592-
designed to live alongside each other. This means that for example if you
593-
have them both installed you will have three qmake exe's:
591+
/!\ ***A Special Note:*** If you are following this set of instructions on
592+
a system where you already have Qt3 development tools installed, there will
593+
be a conflict between Qt3 tools and Qt4 tools. For example, qmake will
594+
point to the Qt3 version not the Qt4. Ubuntu Qt4 and Qt3 packages are
595+
designed to live alongside each other. This means that for example if you
596+
have them both installed you will have three qmake exe's:
594597

595-
```
596-
/usr/bin/qmake -> /etc/alternatives/qmake
597-
/usr/bin/qmake-qt3
598-
/usr/bin/qmake-qt4
599-
```
598+
```
599+
/usr/bin/qmake -> /etc/alternatives/qmake
600+
/usr/bin/qmake-qt3
601+
/usr/bin/qmake-qt4
602+
```
600603

601-
The same applies to all other Qt binaries. You will notice above that the
602-
canonical 'qmake' is managed by apt alternatives, so before we start to
603-
build QGIS, we need to make Qt4 the default. To return Qt3 to default later
604-
you can use this same process.
604+
The same applies to all other Qt binaries. You will notice above that the
605+
canonical 'qmake' is managed by apt alternatives, so before we start to
606+
build QGIS, we need to make Qt4 the default. To return Qt3 to default later
607+
you can use this same process.
605608

606-
You can use apt alternatives to correct this so that the Qt4 version of
607-
applications is used in all cases:
609+
You can use apt alternatives to correct this so that the Qt4 version of
610+
applications is used in all cases:
608611

609-
```
610-
sudo update-alternatives --config qmake
611-
sudo update-alternatives --config uic
612-
sudo update-alternatives --config designer
613-
sudo update-alternatives --config assistant
614-
sudo update-alternatives --config qtconfig
615-
sudo update-alternatives --config moc
616-
sudo update-alternatives --config lupdate
617-
sudo update-alternatives --config lrelease
618-
sudo update-alternatives --config linguist
619-
```
612+
```
613+
sudo update-alternatives --config qmake
614+
sudo update-alternatives --config uic
615+
sudo update-alternatives --config designer
616+
sudo update-alternatives --config assistant
617+
sudo update-alternatives --config qtconfig
618+
sudo update-alternatives --config moc
619+
sudo update-alternatives --config lupdate
620+
sudo update-alternatives --config lrelease
621+
sudo update-alternatives --config linguist
622+
```
620623

621-
Use the simple command line dialog that appears after running each of the
622-
above commands to select the Qt4 version of the relevant applications.
624+
Use the simple command line dialog that appears after running each of the
625+
above commands to select the Qt4 version of the relevant applications.
623626

624-
== Install additional software dependencies required by QGIS ==
627+
== Install additional software dependencies required by QGIS ==
625628

626-
```
627-
sudo apt-get install gdal-bin libgdal1-dev libgeos-dev proj libtool \
628-
libgdal-doc libhdf4g-dev libhdf4g-run autoconf2.13 automake1.9 python-dev \
629-
swig libgsl0-dev g++ libjasper-1.701-dev libtiff4-dev subversion gsl-bin \
630-
libsqlite3-dev sqlite3 ccache make libpq-dev flex bison firefox
631-
```
629+
```
630+
sudo apt-get install gdal-bin libgdal1-dev libgeos-dev proj libtool \
631+
libgdal-doc libhdf4g-dev libhdf4g-run autoconf2.13 automake1.9 python-dev \
632+
swig libgsl0-dev g++ libjasper-1.701-dev libtiff4-dev subversion gsl-bin \
633+
libsqlite3-dev sqlite3 ccache make libpq-dev flex bison firefox
634+
```
632635

633636

634-
== GRASS Specific Steps ==
637+
== GRASS Specific Steps ==
635638

636-
/!\ ***Note:*** If you don't need to build with GRASS support, you can
637-
skip this section.
639+
/!\ ***Note:*** If you don't need to build with GRASS support, you can
640+
skip this section.
638641

639-
Now you can install grass from dapper:
642+
Now you can install grass from dapper:
640643

641-
```
642-
sudo apt-get install grass libgrass-dev libgdal1-grass
643-
```
644+
```
645+
sudo apt-get install grass libgrass-dev libgdal1-grass
646+
```
644647

645-
== Setup ccache (Optional) ==
648+
== Setup ccache (Optional) ==
646649

647-
You should also setup ccache to speed up compile times:
650+
You should also setup ccache to speed up compile times:
648651

649-
```
650-
cd /usr/local/bin
651-
sudo ln -s /usr/bin/ccache gcc
652-
sudo ln -s /usr/bin/ccache g++
653-
```
652+
```
653+
cd /usr/local/bin
654+
sudo ln -s /usr/bin/ccache gcc
655+
sudo ln -s /usr/bin/ccache g++
656+
```
654657

655-
== Prepare your development environment ==
658+
== Prepare your development environment ==
656659

657-
As a convention I do all my development work in $HOME/dev/<language>, so in
658-
this case we will create a work environment for C++ development work like
659-
this:
660+
As a convention I do all my development work in $HOME/dev/<language>, so in
661+
this case we will create a work environment for C++ development work like
662+
this:
660663

661-
```
662-
mkdir -p ${HOME}/dev/cpp
663-
cd ${HOME}/dev/cpp
664-
```
664+
```
665+
mkdir -p ${HOME}/dev/cpp
666+
cd ${HOME}/dev/cpp
667+
```
665668

666-
This directory path will be assumed for all instructions that follow.
669+
This directory path will be assumed for all instructions that follow.
667670

668671

669-
== Check out the QGIS Source Code ==
672+
== Check out the QGIS Source Code ==
670673

671-
There are two ways the source can be checked out. Use the anonymous method
672-
if you do not have edit privaleges for the QGIS source repository, or use
673-
the developer checkout if you have permissions to commit source code
674-
changes.
674+
There are two ways the source can be checked out. Use the anonymous method
675+
if you do not have edit privaleges for the QGIS source repository, or use
676+
the developer checkout if you have permissions to commit source code
677+
changes.
675678

676-
1. Anonymous Checkout
679+
1. Anonymous Checkout
677680

678-
```
679-
cd ${HOME}/dev/cpp
680-
svn co https://svn.qgis.org/repos/qgis/trunk/qgis qgis
681-
```
681+
```
682+
cd ${HOME}/dev/cpp
683+
svn co https://svn.qgis.org/repos/qgis/trunk/qgis qgis
684+
```
682685

683-
2. Developer Checkout
686+
2. Developer Checkout
684687

685-
```
686-
cd ${HOME}/dev/cpp
687-
svn co --username <yourusername> https://svn.qgis.org/repos/qgis/trunk/qgis qgis
688-
```
688+
```
689+
cd ${HOME}/dev/cpp
690+
svn co --username <yourusername> https://svn.qgis.org/repos/qgis/trunk/qgis qgis
691+
```
689692

690-
The first time you check out the source you will be prompted to accept the
691-
qgis.org certificate. Press 'p' to accept it permanently:
693+
The first time you check out the source you will be prompted to accept the
694+
qgis.org certificate. Press 'p' to accept it permanently:
692695

693-
```
694-
Error validating server certificate for 'https://svn.qgis.org:443':
695-
- The certificate is not issued by a trusted authority. Use the
696-
fingerprint to validate the certificate manually! Certificate
697-
information:
698-
- Hostname: svn.qgis.org
699-
- Valid: from Apr 1 00:30:47 2006 GMT until Mar 21 00:30:47 2008 GMT
700-
- Issuer: Developer Team, Quantum GIS, Anchorage, Alaska, US
701-
- Fingerprint:
702-
2f:cd:f1:5a:c7:64:da:2b:d1:34:a5:20:c6:15:67:28:33:ea:7a:9b (R)eject,
703-
accept (t)emporarily or accept (p)ermanently?
704-
```
696+
```
697+
Error validating server certificate for 'https://svn.qgis.org:443':
698+
- The certificate is not issued by a trusted authority. Use the
699+
fingerprint to validate the certificate manually! Certificate
700+
information:
701+
- Hostname: svn.qgis.org
702+
- Valid: from Apr 1 00:30:47 2006 GMT until Mar 21 00:30:47 2008 GMT
703+
- Issuer: Developer Team, Quantum GIS, Anchorage, Alaska, US
704+
- Fingerprint:
705+
2f:cd:f1:5a:c7:64:da:2b:d1:34:a5:20:c6:15:67:28:33:ea:7a:9b (R)eject,
706+
accept (t)emporarily or accept (p)ermanently?
707+
```
705708

706-
== Starting the compile ==
709+
== Starting the compile ==
707710

708-
I compile my development version of QGIS into my ~/apps directory to avoid
709-
conflicts with Ubuntu packages that may be under /usr. This way for example
710-
you can use the binary packages of QGIS on your system along side with your
711-
development version. I suggest you do something similar:
711+
I compile my development version of QGIS into my ~/apps directory to avoid
712+
conflicts with Ubuntu packages that may be under /usr. This way for example
713+
you can use the binary packages of QGIS on your system along side with your
714+
development version. I suggest you do something similar:
712715

713-
```
714-
mkdir -p ${HOME}/apps
715-
```
716+
```
717+
mkdir -p ${HOME}/apps
718+
```
716719

717-
The script will carry on to build QGIS - it may take a little while to go
718-
and have a cup of your favourite beverage while you wait...
720+
The script will carry on to build QGIS - it may take a little while to go
721+
and have a cup of your favourite beverage while you wait...
719722

720-
== Running QGIS ==
723+
== Running QGIS ==
721724

722-
Once the compile is complete it should pop up a page in firefox with unit
723-
test results. At the time of writing the unit tests are just stubs - we
724-
still need to create the test implementations - so dont worry to much about
725-
their output at the moment.
725+
Once the compile is complete it should pop up a page in firefox with unit
726+
test results. At the time of writing the unit tests are just stubs - we
727+
still need to create the test implementations - so dont worry to much about
728+
their output at the moment.
726729

727-
Now you can try to run QGIS:
730+
Now you can try to run QGIS:
728731

729-
```
730-
$HOME/apps/bin/qgis
731-
```
732+
```
733+
$HOME/apps/bin/qgis
734+
```
732735

733-
If all has worked properly the QGIS application should start up and appear
734-
on your screen.
736+
If all has worked properly the QGIS application should start up and appear
737+
on your screen.
735738

736739

737740
= Further help and information =

0 commit comments

Comments
 (0)
Please sign in to comment.