Send grass-windows mailing list submissions to
        grass-windows@lists.osgeo.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.osgeo.org/mailman/listinfo/grass-windows
or, via email, send a message with subject or body 'help' to
        grass-windows-requ...@lists.osgeo.org

You can reach the person managing the list at
        grass-windows-ow...@lists.osgeo.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of grass-windows digest..."


Today's Topics:

   1. Re: r.basin for windows [was Re:  WinGrass6.5.svn-installer
      with selected addons] (Margherita Di Leo)
   2. Re: r.basin for windows [was Re:  WinGrass6.5.svn-installer
      with selected addons] (Glynn Clements)


----------------------------------------------------------------------

Message: 1
Date: Fri, 14 Oct 2011 10:32:25 +0200
From: Margherita Di Leo <direg...@gmail.com>
Subject: Re: [GRASS-windows] r.basin for windows [was Re:
        WinGrass6.5.svn-installer with selected addons]
To: Glynn Clements <gl...@gclements.plus.com>
Cc: grass-windows@lists.osgeo.org, Helmut Kudrnovsky <hel...@web.de>
Message-ID:
        <CABa=8qp-3hebzitibwt-hldxeosmnfbwm8ewij4yh1_c3hf...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hi,

2011/10/13 Glynn Clements <gl...@gclements.plus.com>

>
> Helmut Kudrnovsky wrote:
>
> > any ideas? I don't know if python-scripts are recognised correctly in
> build
> > process.
>
> They aren't.
>
> And the rules can't simply be back-ported from 7.0 because 7.0's
> Script.make only works for Python scripts, not for shell scripts.
>
>
Sorry I am a bit confused. If I understand, there is no way to compile any
python script on grass 6 series? Is that related to windows or is platform
independent?
I tried to compile r.basin on debian and I do have problems as well. I would
have bet that it was working when i committed it, but I'm not sure at this
point.
But.. could it be a problem in the makefile? I'm not sure I wrote it
correctly. Please could anyone more experienced than me give a look at it?

Thanks,

madi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://lists.osgeo.org/pipermail/grass-windows/attachments/20111014/a58069ba/attachment-0001.html

------------------------------

Message: 2
Date: Fri, 14 Oct 2011 13:27:45 +0100
From: Glynn Clements <gl...@gclements.plus.com>
Subject: Re: [GRASS-windows] r.basin for windows [was Re:
        WinGrass6.5.svn-installer with selected addons]
To: Margherita Di Leo <direg...@gmail.com>
Cc: Helmut Kudrnovsky <hel...@web.de>, grass-windows@lists.osgeo.org
Message-ID: <20120.10945.633377.719...@cerise.gclements.plus.com>
Content-Type: text/plain; charset=us-ascii


Margherita Di Leo wrote:

> > > any ideas? I don't know if python-scripts are recognised correctly in
> > > build
> > > process.
> >
> > They aren't.
> >
> > And the rules can't simply be back-ported from 7.0 because 7.0's
> > Script.make only works for Python scripts, not for shell scripts.
> 
> Sorry I am a bit confused. If I understand, there is no way to compile any
> python script on grass 6 series? Is that related to windows or is platform
> independent?

It isn't platform-specific. The 6.x build system has no support for
Python scripts.

The 6.x build system assumes that scripts are shell scripts. The
"script" target defined by Script.make will attempt to install $(PGM)
as $(ARCH_DISTDIR)/scripts/$(PGM). Also, the rule used to make the
HTML file doesn't set PYTHONPATH, so if a Python script imports e.g. 
grass.script, the import will fail. Also, on Windows it will create a
.bat file which invokes the script via $GRASS_SH (which won't work for
Python scripts).

In 7.0, the "script" target will attempt to install $(PGM).py as
either $(ARCH_DISTDIR)/scripts/$(PGM) (on Unix) or
$(ARCH_DISTDIR)/scripts/$(PGM).py (on Windows, as Windows uses the
extension rather than the #! line to determine how to "execute" a
script). And it will set PYTHONPATH when running a command to generate
its HTML file.

> I tried to compile r.basin on debian and I do have problems as well. I would
> have bet that it was working when i committed it, but I'm not sure at this
> point.
> But.. could it be a problem in the makefile? I'm not sure I wrote it
> correctly. Please could anyone more experienced than me give a look at it?

That won't work, because no file named "r.basin" exists in the
directory.

-- 
Glynn Clements <gl...@gclements.plus.com>


------------------------------

_______________________________________________
grass-windows mailing list
grass-windows@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-windows


End of grass-windows Digest, Vol 60, Issue 12
*********************************************

Reply via email to