Re: problem building extension

Evidently this extension ships with a file Makefile as well as Makefile.PL. What the command perl Makefile.PL does is to write a file called Makefile. On Win32 you would usually use nmake. What nmake does is to read the content of the Makefile generated by running Makefile.PL and execute it to build the extension. The usual way to make an app on Win32 is:

perl Makefile.PL
nmake && nmake test && nmake install
[download]

See A Guide to Installing Modules. Get nmake. Try it the usual way. If you can't get it to work post a link to the extension source. Monks like PodMaster and myself like getting stuff to build on Win32.....

The fact that it is looking for lVEILibDLL means that this is an XS/C based app. You will need a C compiler to build it successfully. The fact that it can't find this lib means you have a problem. See A Practical Guide to Compiling C based Modules under ActiveState using Microsoft C++

cheers

tachyon

Comment on Re: problem building extension Select or Download Code

Replies are listed 'Best First'.
Re^2: problem building extension by BrowserUk (Patriarch) on Jun 18, 2004 at 00:23 UTC
omake is a ClearCase make tool and the `-EN` switch is meant to make it behave like `nmake`. If, as the OP states, the dates on the dependancy files are really not later than that of the target then it shouldn't be trying to rebuild the Makefile. But if the make tool doesn't know how to handle dependancies it would be pretty useless and ClearCase is a big enough name to consider that unlikely. Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "Think for yourself!" - Abigail "Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon	[reply] [d/l] [select]
Re^2: problem building extension by timfar (Acolyte) on Jun 18, 2004 at 00:20 UTC
I guess I left something out. I have used nmake and it works. I have to use omake for the configuration control system we use here (clearcase). I think what I want to know is whether there's a way to edit Makefile.PL so that in makefile, the makefile dependency isn't checked at all. When I remove the section in the makefile that checks that dependency, the build works. The missing DLL is a different problem. I know how to fix that - sorry for leaving it in. Thanks for so many replies so quick!!	[reply]
Re^3: problem building extension by tachyon (Chancellor) on Jun 18, 2004 at 00:29 UTC
Makefile.PL is just perl code. You could add any of: `unlink './Makefile'; rename './Makefile', './Makefile.old' system('nmake clean') if $^0 =~ m/Win32/;` [download] before the call to ExtUtils::MakeMaker to get rid of the old Makefile (which I think is the issue). Alternatively you can simply EDIT the Makefile after it is created to delete the section that is causing you issues. After the call to MakeMaker add some perl to make any edits you need to keep omake happy. You can add any amount of cleanup, prompting, etc, etc code to Makefile.PL. For example it is not uncommon to automatically pick a C/C++ compiler based on platform (see Inline::CPP distro Makefile.PL) or hunt down libraries (and prompt if not found) etc, etc. cheers tachyon	[reply] [d/l]