comment on

I once compiled OpenGL.pm 0.53 for Win32, and it was only a matter of patching the MS header files. The OpenGL header files should already be in the include search path for the MSVC compiler.

For SGL, I would start with registry entries, if there is some setup file for Win32 that installs the binaries, and then some directory guesses like C:/sdl/lib, and if the guesses fail, use File::Find(::Rule)? to look for the header files, at least on C:/ and the volume perl resides on.

I'm in the process of patching the Net::SSLeay Makefile to do exactly this searching, but haven't come too far with it yet.

perl -MHTTP::Daemon -MHTTP::Response -MLWP::Simple -e ' ;    # The  
$d = new HTTP::Daemon and fork and getprint $d->url and exit;#spider
($c = $d->accept())->get_request(); $c->send_response( new   #in the
HTTP::Response(200,$_,$_,qq(Just another Perl hacker\n))); ' #  web
[download]

In reply to Re: Re: Re: Re: Re: SDL_perl on 5.8 by Corion
in thread SDL_perl on 5.8 by mce

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks