On Mon, Jul 4, 2011 at 5:03 AM, Dmitry Karasik <[email protected]> wrote: > >> (4) Replace platform OpenGL library detection >> in the Makefile.PL by an Alien::OpenGL or >> such approach. Maybe Alien::GLEW would be >> better here. > > It's your call, but I see no point in doing it in a separate module. Some > small > set of command-line parameters for explicit selection, plus some build > heuristics > should be fine, I guess.
The goal here would be to make that selection and detection available for other Perl module developers without having to learn/relearn/implement/re-implement all the platform specific issues. >> (5) Move from EU::MM to Module::Build to reduce >> platform specific shell and make issues. > > ugh, I'd rather not to. That's highly subjective and personal, but I've been > weighing Module::Build vs EU::MM and so far it doesn't pay off. If > Module::Build would help detecting installed libraries, include files, > compiling small programs to check out lib versions etc (like autoconf for > example), then I'd be first to use it. Otherwise, gains are too small for me. I wanted to clarify this a bit: We're moving towards using the Devel::CheckLib for the external library detection process. It encapsulates the standard process for test compiles to check for headers and libraries and can be a standard there. (I notice that the Prima Makefile.PL has a lot of functionality that resembles Devel::CheckLib). For PDL and POGL applications, the motivation for M::B is to remove the platform specific issues of make commands (installation, availability and versions) and command shells (sh, bash, csh, CMD (barely a shell),...) from the buld process and specifically for the win32 platforms. MSWin32 systems are handicapped by their lack of any default support for packages which implies a lack of availability of make, shells, and other build tools since a perl module user would need to download and install the needed toolset (individually, MSYS, cygwin,...) and know how to install and be able to install *before* they can even get to using perl. Using Module::Build means that you basically only need a compiler environment (MinGW is available by PPM for ActiveState Perl and included in Strawberry Perl) and Perl (ditto)! Using Alien::XX modules with Devel::CheckLib for the detection, a perl module using external libraries does not have to do anything more than 'use Alien::MyLib' to get all they need to use or work with MyLib----and it even works on non-unix platforms (i.e., MSWin32). Think of this as a flavor of improving the win32 perl environment along the lines of what Strawberry perl has done but at the module level and allowing win32 to be supported equally with unix-ish ones. This approach should also allow more perl gurus (typically with a very strong or only unix background) to develop modules that work for win32 as well. Cheers, Chris >> If you are interested in participating, please >> contact me via email or through the sf.net >> project page links at >> > > Yes please. Also, if you want to, I can jump in and help you with OpenGL > build issues > on win32 and cygwin. > > -- > Sincerely, > Dmitry Karasik _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
