Source repositories overview: Difference between revisions
From RISC OS
Jump to navigationJump to search
m (Don't link the SVN URLs in commands) |
m (Update with latest 4.1.1 Release 2 info) |
||
| Line 89: | Line 89: | ||
:The ''gccsdk'' repository has its trunk at <code>trunk</code>, branches at <code>branches</code> and tags at <code>tags</code> as subdirectories of the ''gccsdk'' repository. |
:The ''gccsdk'' repository has its trunk at <code>trunk</code>, branches at <code>branches</code> and tags at <code>tags</code> as subdirectories of the ''gccsdk'' repository. |
||
:The autobuilder code is located at <code>trunk/autobuilder</code> and does not have any branches nor tags so far. |
:The autobuilder code is located at <code>trunk/autobuilder</code> and does not have any branches nor tags so far. |
||
:Note that the code at <code>trunk/gcc4</code> is <b>not stable</b> and is currently used for |
:Note that the code at <code>trunk/gcc4</code> is <b>not stable</b> and is currently used for future [[GCCSDK Development|GCCSDK GCC 4.x developments]]. If you want the currently latest and stable gcc code branch <code>branches/release_4_1_1 gccsdk</code>, instead use: |
||
:<code><nowiki>$ svn co svn://svn.riscos.info/gccsdk/branches/ |
:<code><nowiki>$ svn co svn://svn.riscos.info/gccsdk/branches/release_4_1_1/ gccsdk</nowiki></code> |
||
:The following are the most important tags used: |
:The following are the most important tags used: |
||
:*release_4_1_1_v2 : tree snapshot for the GCCSDK GCC 4.1.1 Release 2 release. |
|||
:*release_3_4_6_v3 : tree snapshot for the GCCSDK GCC 3.4.6 Release 3 release. |
:*release_3_4_6_v3 : tree snapshot for the GCCSDK GCC 3.4.6 Release 3 release. |
||
:*release_3_4_6_v2 : tree snapshot for the GCCSDK GCC 3.4.6 Release 2 release. |
:*release_3_4_6_v2 : tree snapshot for the GCCSDK GCC 3.4.6 Release 2 release. |
||
| Line 103: | Line 104: | ||
:*release_2_95_4_v3 : tree snapshot for the GCCSDK GCC 2.95.4 Release 3 release. |
:*release_2_95_4_v3 : tree snapshot for the GCCSDK GCC 2.95.4 Release 3 release. |
||
:The following are the most important branches used: |
:The following are the most important branches used: |
||
:* |
:*release_4_1_1 : '''stable branch''' containing minor fixes and enhancements for the GCCSDK GCC 4.1.1 releases. |
||
:*release_3_4_6 : '''closed branch''', this was the stable branch for the GCCSDK GCC 3.4.6 releases. |
|||
:*release_3_4_4_v2_stable : '''closed branch''', this was the stable branch for the GCCSDK GCC 3.4.4 releases. |
:*release_3_4_4_v2_stable : '''closed branch''', this was the stable branch for the GCCSDK GCC 3.4.4 releases. |
||
:*release_3_3 : '''closed branch''', this was the development branch for all GCCSDK 3.3 based work. |
:*release_3_3 : '''closed branch''', this was the development branch for all GCCSDK 3.3 based work. |
||
:*release_2_95 : '''closed branch''', this |
:*release_2_95 : '''closed branch''', this was the development branch for all GCCSDK 2.95 based work. |
||
=== QEMU === |
=== QEMU === |
||
Revision as of 13:58, 27 December 2009
People not or not fully experienced with Subversion are strongly recommended to read the Subversion Book and the Subversion FAQ.
Subversion clients
- RISC OS Subversion client.
- Windows Subversion client
- For Linux and other Unices, a Subversion client should be included in the distribution.
SVN repositories at riscos.info
All SVN repositories at svn.riscos.info have anonymous read-only access. Write-access needs an account and password.
Unless otherwise noted:
- all svn.riscos.info SVN repositories have the RISC OS filetypes of their files encoded using the ",xyz" hex suffix method. This means that, if using the RISC OS subversion client, the
svn$filetypeextsystem variable must be set. See the svn !Help file for more details. - the repositories follow the layout conventions suggested in the svn book. (That is, branches are kept in
branchesand tags intags.)
You can view the contents of all available SVN repositories using the WebSVN interface.
Commit notification mailing list
Many of the projects are configured to send an email when changes (commits) are made to the repositories. To receive these emails, subscribe to the riscos-commits mailing list.
SVN Repository List
The following SVN repositories are available:
| Project | Description | Paths |
|---|---|---|
| AMPlayer | RISC OS MP3 player and front end | svn://svn.riscos.info/amplayer/trunk/ |
| CCres | A Text to Resource (filetype &fae) and Template (filetype &fec) compiler and decompiler | svn://svn.riscos.info/ccres/trunk/ |
| ChoX11 | The XLib replacement for RISC OS | svn://svn.riscos.info/ChoX11/trunk/ |
| Cretin | IRC Client | svn://svn.riscos.info/cretin/trunk/ |
| CVS GUI | Easy CVS operations via graphical frontend | svn://svn.riscos.info/cvsgui/trunk/ |
| DeskLib | C Wimp library for RISC OS | svn://svn.riscos.info/DeskLib/trunk/ (Main development) |
| GCCSDK | RISC OS GCC and Autobuilder | svn://svn.riscos.info/gccsdk/trunk/ |
| PCITV | TV card application | svn://svn.riscos.info/pcitv/trunk/ |
| QEMU | RISC OS/ARM emulator | svn://svn.riscos.info/qemu/branches/riscos |
| RPCEmu | RiscPC emulator | svn://svn.riscos.info/rpcemu/trunk/
svn://svn.riscos.info/rpcemu/branches/ppcmacport/ (PPC Mac OS X) |
| Thump | Image Viewer | svn://svn.riscos.info/thump/trunk/ |
| WinEd | Template Editor | svn://svn.riscos.info/wined/trunk/ |
Notes
GCCSDK & Autobuilder
- GCCSDK and Autobuilder sources are stored in one repository gccsdk. To check out the 'trunk', use:
$ svn co svn://svn.riscos.info/gccsdk/trunk/ gccsdk- The gccsdk repository has its trunk at
trunk, branches atbranchesand tags attagsas subdirectories of the gccsdk repository. - The autobuilder code is located at
trunk/autobuilderand does not have any branches nor tags so far. - Note that the code at
trunk/gcc4is not stable and is currently used for future GCCSDK GCC 4.x developments. If you want the currently latest and stable gcc code branchbranches/release_4_1_1 gccsdk, instead use: $ svn co svn://svn.riscos.info/gccsdk/branches/release_4_1_1/ gccsdk- The following are the most important tags used:
- release_4_1_1_v2 : tree snapshot for the GCCSDK GCC 4.1.1 Release 2 release.
- release_3_4_6_v3 : tree snapshot for the GCCSDK GCC 3.4.6 Release 3 release.
- release_3_4_6_v2 : tree snapshot for the GCCSDK GCC 3.4.6 Release 2 release.
- release_3_4_6_v1 : tree snapshot for the GCCSDK GCC 3.4.6 Release 1 release.
- release_3_4_5_v1 : tree snapshot for the GCCSDK GCC 3.4.5 Release 1 release.
- release_3_4_4_v3 : tree snapshot for the GCCSDK GCC 3.4.4 Release 3 release.
- release_3_4_4_v2 : tree snapshot for the GCCSDK GCC 3.4.4 Release 2 release.
- release_3_4_4 : tree snapshot for the GCCSDK GCC 3.4.4 Release 1 release.
- release_3_4_1 : tree snapshot for the GCCSDK GCC 3.4.1 Release 1 release.
- release_3_3_3_pre2 : tree snapshot for the GCCSDK GCC 3.3.3 pre-release 2 release.
- release_2_95_4_v3 : tree snapshot for the GCCSDK GCC 2.95.4 Release 3 release.
- The following are the most important branches used:
- release_4_1_1 : stable branch containing minor fixes and enhancements for the GCCSDK GCC 4.1.1 releases.
- release_3_4_6 : closed branch, this was the stable branch for the GCCSDK GCC 3.4.6 releases.
- release_3_4_4_v2_stable : closed branch, this was the stable branch for the GCCSDK GCC 3.4.4 releases.
- release_3_3 : closed branch, this was the development branch for all GCCSDK 3.3 based work.
- release_2_95 : closed branch, this was the development branch for all GCCSDK 2.95 based work.
QEMU
- RISC OS and GCCSDK specific changes to the QEMU project are stored in the repository.
- Revision 2 contains a snapshot of QEMU CVS repository made on 2006-03-21 01:00:00 CET. The trunk will be from time to time updated with snapshots taken from the QEMU CVS repository. The RISC OS and GCCSDK specific changes will be made in the branch riscos.
Other source repositories
The following are source repositories for RISC OS projects which aren't hosted by riscos.info.
NetSurf
- The source code for NetSurf can be obtained with the following command.
$ svn co svn://svn.netsurf-browser.org/trunk/netsurf- The source can also be viewed via a web interface.
- Full instructions for building NetSurf on RISC OS are available on NetSurf's web site.
