[GRASS-dev] Make Changes to Modules in Grass GIS

Hi all,

I have installed ubuntu, downloaded the source code from https://grass.osgeo.org/grass74/source/grass-7.4.1.tar.gz and installed grass-dev package. Since I do not have experience with c can you again briefly explain how to do changes and compile the code. Is the workflow following is correct to do what I intended.

  1. copy r.ros folder from grass-7.4.1/raster and rename it as r.new.ros
  2. make relevant changes to main.c file in r.new.ros
  3. compile the code with ‘make’ command.
  • can you explain what the grass-dev package does.
    Thank you. Have a nice day.

BR,
Vidura Dantanarayana

On Fri, Aug 3, 2018 at 9:50 AM, Vidura Dantanarayana <vidurada@gmail.com>
wrote:

Hi all,
I have installed ubuntu, downloaded the source code from
https://grass.osgeo.org/grass74/source/grass-7.4.1.tar.gz and installed
grass-dev package. Since I do not have experience with c can you again
briefly explain how to do changes and compile the code. Is the workflow
following is correct to do what I intended.

1) copy r.ros folder from grass-7.4.1/raster and rename it as r.new.ros
2) make relevant changes to main.c file in r.new.ros

Yes and yes.

3) compile the code with 'make' command.

You will need to provide parameters to help make find the GRASS GIS
installation and where to put the compiled module. The g.extension module
will do this for you if you do something like this:

g.extension extension=r.new.ros url=/path/to/r.new.ros

* can you explain what the grass-dev package does.

Usually, for most packages on Linux, the files needed for development, e.g.
linking with the library, are not distributed together with the library and
program in the package without -dev (since unless you do development you
don't need them). If you install the grass-dev package you get, for example
the C header files for the libraries (that's actually most of what you
get). You can list all these files using:

dpkg --listfiles grass-dev

Additionally, you should also get all the compile-time dependencies of
GRASS GIS not only the runtime ones which is very useful.

HTH,
Vaclav

Thank you. Have a nice day.

BR,
Vidura Dantanarayana

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Hi Vaclav,
Of course, that helped me a lot. Thank you so much.

BR,
Vidura Dantanarayana

···

On Fri, Aug 3, 2018 at 9:50 AM, Vidura Dantanarayana <vidurada@gmail.com> wrote:

Hi all,

I have installed ubuntu, downloaded the source code from https://grass.osgeo.org/grass74/source/grass-7.4.1.tar.gz and installed grass-dev package. Since I do not have experience with c can you again briefly explain how to do changes and compile the code. Is the workflow following is correct to do what I intended.

  1. copy r.ros folder from grass-7.4.1/raster and rename it as r.new.ros
  2. make relevant changes to main.c file in r.new.ros

Yes and yes.

  1. compile the code with ‘make’ command.

You will need to provide parameters to help make find the GRASS GIS installation and where to put the compiled module. The g.extension module will do this for you if you do something like this:

g.extension extension=r.new.ros url=/path/to/r.new.ros

  • can you explain what the grass-dev package does.

Usually, for most packages on Linux, the files needed for development, e.g. linking with the library, are not distributed together with the library and program in the package without -dev (since unless you do development you don’t need them). If you install the grass-dev package you get, for example the C header files for the libraries (that’s actually most of what you get). You can list all these files using:

dpkg --listfiles grass-dev

Additionally, you should also get all the compile-time dependencies of GRASS GIS not only the runtime ones which is very useful.

HTH,

Vaclav

Thank you. Have a nice day.

BR,
Vidura Dantanarayana


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev