in reply to Nmake......STOP!!

Since you're using gcc, which shell are you running, is this the Command Prompt or something more civilized?

On NT, mkdir takes /a as a flag, not -p, so the makefile is for some un*x.

If you're using cygwin, don't use nmake but the gnu make which comes with it.

Hope this helps, -gjb-

Replies are listed 'Best First'.
Re: Re: Nmake......STOP!!
by eoin (Monk) on Jan 04, 2003 at 23:19 UTC
    I'm running ActivePerl under Windows Me. And the Nmake i'm using is for Windows but I still don't know whats wrong.
    I was only intrested in the module so I could look into using graphics in some programs, could you perhaps recomend a different module I could use.
    Thanks, Eoin...
[reply]

      Aha, that means the makefile is not appropriate for nmake. There are a number of differences between (un*x) make and nmake with respect to syntax, etc.

      Normally, you get the appropriate makefile using perl Makefile.PL. That generates a makefile, in case of ActiveState Perl a makefile for nmake since those guys still don't support any other compiler than VC++ and its utilities such as nmake.

      If there's a file Makefile.PL, run perl Makefile.PL</p> and then <code>nmake test, nmake install (if the former succeeds. That might work or not, but I'm not optimistic. It assumes that everything will be build and ocmpiled with VC++ and Gtk stuff is very un*x.

      I hope this clarifies things a bit, good luck, -gjb-

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom