in reply to Re^4: Win32 - gl/glu.h problem
in thread Daunting Problem With Perl Opengl Lighting

Like I say, ppm just breaks: 

C:\Perl>ppm install http://graphcomp.com/opengl/ppm58/OpenGL.ppd
PPM::PPD::init: not a PPD and not a file:

[download]
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Replies are listed 'Best First'.
Re^6: Win32 - gl/glu.h problem
by syphilis (Archbishop) on Jul 20, 2008 at 09:26 UTC
    Like I say, ppm just breaks

    That's interesting. I installed that ppm onto one of my perls - but I was using the PPM that's on CPAN, not ActiveState's PPM utility. Try using this as your ppd file instead: 
    <SOFTPKG NAME="OpenGL" VERSION="0,56,04,0">
    <TITLE>OpenGL</TITLE>
    <ABSTRACT>Perl binding for OpenGL</ABSTRACT>
    <AUTHOR>Bob "grafman" Free</AUTHOR>
    <IMPLEMENTATION>
        <OS NAME="MSWin32" />
        <ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.8" />
        <CODEBASE HREF="http://graphcomp.com/opengl/ppm58/OpenGL-0.56_
+04.tar.gz" />
        <PROVIDE NAME="OpenGL" VERSION="0.56_04" />
    </IMPLEMENTATION>
</SOFTPKG>

    [download]
    It contains <PROVIDE NAME>, the absence of which may (or may not) be the cause of the problem you're having.

    Update: Hmmm ... I don't think that will help. I just tried installing via (ActiveState's) ppm on ActivePerl build 822 and it worked fine for me. I used the same command (and hence PPD file as you did): 
    ppm install http://graphcomp.com/opengl/ppm58/OpenGL.ppd

    [download]
    Cheers,
    Rob
[reply]
[d/l]
[select]
      Hmmm ... I don't think that will help.

      Yes. Or rather, no. The breakage is definitely local. Once it stops working, it stops for everything. Some internal configuration, maybe registry, maybe not, gets screwed, and thence after, the only reliable way of restoring function is to uninstall, wipe the registry of anything containing "ActiveState", "ActivePerl", and anything else that looks vaguely related and then reinstall.

      An annoying, boring, laborious and ultimately, cargo-cult solution. But I've tried several times to track through the pointless nest of OO crap that forms ppm these days, and life is too just short to be bothered.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
        But I've tried several times to track through the pointless nest of OO crap that forms ppm

        Yes, I also find ActiveState's PPM to be infuriatingly difficult to deal with. Not so much, however, the version that's on CPAN - it doesn't have the bells and whistles of ActiveState's version, but it does everything I want - and I've found it to be relatively parseable on those rare occasions where I've needed to get "behind the scenes".

        I've only ever used that CPAN version with MinGW-built perls, and I don't know how difficult (or easy) it would be to replace ActiveState's PPM with it on ActivePerl.

        Cheers,
        Rob
[reply]
        Don't be bothered, just forward the error to ActiveState, along with a tracefile and ppm.xml (in site\lib )

        Maybe all you need is to regenerate ppm.xml (ppm genconfig > ppm.xml )

[reply]

In Section Seekers of Perl Wisdom