Commit | Line | Data |
bfd90409 |
1 | README for SDL_Perl-2.2.0 |
2 | |
3 | What's New in 2.2.0: |
4 | |
5 | SDL_Perl-2.2.0 adds support for a few new modules, fixes a few more |
6 | bugs, and improves the error handling of the object layer. Additional |
7 | support for SDL_sound, SDL_svg, and SDL_vnc has been added. In the |
8 | OO layer, all constructors now die when they fail to construct an object |
9 | with a valid underlying datastructure pointer. |
10 | |
11 | Prerequisites: |
12 | |
13 | SDL Perl recommends installing the following libraries available |
14 | from http://www.libsdl.org/ prior to installing: |
15 | |
16 | SDL-1.2.8 |
17 | smpeg-0.4.5 |
18 | SDL_image-1.2.4 |
19 | SDL_mixer-1.2.6 |
20 | SDL_sound-1.0.1 |
21 | SDL_net-1.2.5 |
22 | SDL_gfx-2.0.13 |
23 | SDL_ttf-2.0.7 |
24 | SDL_svg-1.1.9 |
25 | SDL_vnc-1.0.0 |
26 | |
27 | Additionally the following Perl modules should be installed: |
28 | |
29 | Module-Build-0.22 |
30 | Test-Simple-0.62 |
31 | |
32 | Installation: |
33 | |
34 | perl Build.PL |
35 | ./Build |
36 | ./Build test |
37 | ./Build install |
38 | |
39 | The build process will use the new Module::Build facility |
40 | to autodetect and build SDL Perl for your platform. If |
41 | the build fails please forward bugs to sdl-devel@perl.org. |
42 | |
43 | Documentation: |
44 | |
45 | Each module now includes its own documentation, and |
46 | is accessible through perldoc. Additional tutorials, |
47 | code, and tips can be found at the website: |
48 | |
49 | http://sdl.perl.org |
50 | |
51 | Online documentation and tutorials are available through |
52 | perldoc module. |
53 | |
54 | Contributing: |
55 | |
56 | Anyone wishing to contribute modules, sprite engines, documentation, |
57 | and anything else that others might find useful, please join |
58 | the mailing list: |
59 | |
60 | sdl-devel@perl.org |
61 | |
62 | This is a mailing list for those interested in SDLperl development, |
63 | both as an applications developer, and as a core contributor. |
64 | |
65 | I am always more than happy to take patches, bug reports, and |
66 | helpful suggestions. It is feedback, both good and poor, that |
67 | keeps projects like this going. |
68 | |
69 | Enjoy, |
70 | |
71 | David J. Goehrig <dgoehrig@cpan.org> |
72 | |