[GRASS5] Re: [GRASSLIST:360] Re: grass libraries

[Glynn Clements]

Brad Douglas wrote:

> > We should really be installing the include/Make/*.make files. Writing
> > portable Makefiles for add-on modules is likely to be a difficult task
> > without them (particularly Platform.make and Grass.make, which are
> > generated by the configure script).
> 
> IMHO, only files with parameters that cannot go into 'grass.pc' should
> be exported.

The grass.pc file is of little use; apart from linking in too many
libraries, it won't work with static libraries or if you need
additional -L switches to locate the dependencies.

More generally, the idea of treating GRASS as a monolithic package is
fundamentally flawed. Realistically, you would need a separate .pc
file for each library or group of related libraries.

Also, it should be possible to write Makefiles which work either as
part of GRASS or as standalone modules.

-- 
Glynn Clements <glynn at gclements.plus.com>