Allegro - Downloads

게임 프로그래밍 라이브러리

언어: Česky Deutsch English español français Italiano polski

Allegro

뉴스
소개
라이센스
Language bindings

다운로드

최신 버전
SVN
구버전

문서

API
FAQ
튜토리얼
Books
Wiki

지원

도움말
Report Bug
메일링 리스트
Forums
IRC

게임, 유틸리티, 라이브러리 등등

Allegro.cc

기타

공헌하신 분들
지난 뉴스
Logos
DIGMID
링크
미러
웹마스터
Humor

호스팅:
dotsrc.org

Sorry, but this language is not maintained any more. If you would like to become a web translator and update the Allegro web for your language, please inform yourself in the webmasters section.

Subversion read access

Subversion is a replacement for good'ol CVS. You can get clients for most platforms at http://subversion.tigris.org/, and there is good documentation like the Version control with Subversion manual, by some of Subversion's authors.

You can get read access from the main URL https://alleg.svn.sourceforge.net/svnroot/alleg/. While you can access this link directly and will see the files, that's really boring - instead you want to use a Subversion client to check out the whole source and make local modifications in order to send patches. Example:

svn co https://alleg.svn.sourceforge.net/svnroot/alleg/allegro/branches/4.2 (for the stable 4.2 branch) svn co https://alleg.svn.sourceforge.net/svnroot/alleg/allegro/branches/4.9 (for the unstable 4.9 branch)

You can also use a web interface to browse the repository, which you will find at http://alleg.svn.sourceforge.net/viewcvs.cgi/alleg/. The Subversion tree was migrated from SourceForge's CVS repository, so everything you used to know should be there (except the allegrowww module).

If you need write access to the Subversion tree, please ask for it on the Allegro development mailing list.

Snapshots of the Subversion tree

These are snapshots of the Allegro SVN repository. The snapshots here have been wrapped up like any normal WIP releases and are ready to compile. Keep in mind that since these are snapshots and not actual releases, they contain new code which has undergone little testing. Therefore don't be surprised if you can't even compile it or if it gives you a core dump, a bluescreen etc. So if stability is important for you, then you should rather be using one of the WIPs.
Snapshots will be released regularly every week. The goal of these snapshot releases is:

To provide users unfamiliar with SVN, access to the latest Allegro improvements.
Increase the amount of testing that is done between each WIP release. End-user feedback is important for the Allegro developers in order to maintain and improve the quality of Allegro.

The snapshots of the Allegro SVN are generated dynamically only at Sourceforge, and this means that you will have to go there to download them. Please follow this link: http://alleg.sourceforge.net/svn.ko.html.

Changelogs of the Subversion tree

Change logs for the SVN repository are generated every hour and uploaded to the Allegro web page at SourceForge. The xml versions are generated with the --verbose switch, unlike the text versions. Note that these files include the whole repository history since it was started, and they may be very big.

ChangeLog-4.2.txt.gz
ChangeLog-4.2-extract.txt (500 lines extract)
ChangeLog-4.2.xml.gz
ChangeLog-4.3.txt.gz
ChangeLog-4.3-extract.txt (500 lines extract)
ChangeLog-4.3.xml.gz

The SVN repository also has a commit hook for CIA, a system for tracking open-source projects in real-time. The CIA web interface may be easier to read than the above logs, provides an RSS feed and notifications in the #commits channel on the Freenode IRC network. You can monitor Allegro activity at http://cia.navi.cx/stats/project/alleg.