[GRASS-dev] Installing own Python script

Martin Landa landa.martin at gmail.com
Mon Jun 13 12:52:40 EDT 2011


2011/6/1 Glynn Clements <glynn at gclements.plus.com>:
>> > The per-module "install" target (which doesn't exist for scripts at
>> > present) copies a single module (along with its manual page in HTML
>> > and man formats) from the dist.<arch> directory to the installation
>> > directory.
>> >
>> > AFAICT, this is only useful if you're pushing your changes into the
>> > installed version so frequently that having to do a full "make install"
>> > from the top level each time would actually be a problem.
>> Which could be interesting when developing that module/script?
> If you're developing, you should be running GRASS from the staging
> directory rather than using an installed version.
> Apart from convenience, leaving the installed version alone means that
> you can compare the behaviour of the modified version to the installed
> version.
> FWIW, the only time I run "make install" is if I've been working on
> the Makefiles and I want to check that "make install" still works.

I think that there should the per-script "install" target. At least
for g.extension. Currently, g.extension fails with error.

Installing 'r.threshold'...
make: *** No rule to make target `install'.  Stop.
WARNING: Installation failed, sorry. Please check above error messages.


Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa

More information about the grass-dev mailing list