comment on

In seven or eight months of trying, I've personally never found a sensible answer to any of these questions.

Most of those questions you can answer progamatically (and some you don't even have to answer), but asking the user sounds sensible to me (with shortcuts like perl Build.PL --opengl=-lmesa --smpeg --gfx ...).

What isn't sensible (imho) is something like

package SDL::Build::MSWin32; ...

sub find_header
{
    for my $key (qw( LIBS PATH ))
    {
        die "Environment variable $key is empty\n" unless $ENV{$key};
    }
[download]

That is needless death right there (besides, its always LIB and only optionally LIBS). Since sdl-config won't exist on win32 (when dealing with MSVS), makes no sense to die if it doesn't exist, especially if SDL.h/SDL.lib area already in the include/lib path.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

In reply to Re^2: SDL_Perl for Win32? by PodMaster
in thread SDL_Perl for Win32? by jryan

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks