[GRASS-dev] [GRASS GIS] #2528: r.shade not in menu

[GRASS GIS]

#2528: r.shade not in menu
--------------------------+-------------------------------------------------
  Reporter:  cmbarton     |       Owner:  grass-dev@…              
      Type:  defect       |      Status:  reopened                 
  Priority:  normal       |   Milestone:  7.0.0                    
 Component:  wxGUI        |     Version:  unspecified              
Resolution:               |    Keywords:  toolboxes, menu, r.shade 
  Platform:  Unspecified  |         Cpu:  Unspecified              
--------------------------+-------------------------------------------------

Comment(by cmbarton):

 Replying to [comment:10 wenzeslaus]:
 > Replying to [comment:8 cmbarton]:
 > > Is there some way to force an update to the menu from the command line
 after compilation?
 >
 >  * compile with `make`
 >  * run GRASS from `dist...` directory, i.e. using `bin.../grass..`
 >  * `cd` into `gui/wxpython`
 >  * `make clean`
 >  * `make`
 >
 > This should work. If you want to recompile the toolboxes and not the
 whole GRASS, use:
 >
 >  * (in GRASS session)
 >  * `rm dist.../gui/wxpython/xml/*.xml`
 >  * `cd` into `gui/wxpython`
 >  * `make clean`
 >  * `make`
 >
 > If you want to script it, you probably have to start GRASS from command
 line in the demo location and set the environmental variable
 `GRASS_BATCH_JOB` to a script where you have the steps which must be
 executed inside GRASS.

 I'll try these. They might at least reduce the number of steps in a
 workaround. Do you think that the 2nd one will work if I'm running any
 GRASS 7 session? Or must it be the one just compiled?

 >
 > How it works with binary distribution or `make install`, especially on
 Mac OS X,  I have no idea

 ** This in general is part of the problem, not for you specifically but
 for most GRASS devs **

 but you can easily encounter some problems with access rights or not
 execute the whole procedure, e.g. running just `make` and not `make
 install`, I guess.

 This is not a problem in my case at least. Thanks for the suggestions.

 Michael

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2528#comment:13>
GRASS GIS <http://grass.osgeo.org>