[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Pkg-grass-general] Re: Bug#264566: Any progress on grass 5.7?



On Tuesday 12 October 2004 04:13, Hamish wrote:
> [Debian]
>
> > OK. Now back the the grass/gdal problem:
> > Indeed the problem is that I need the grass development package for
> > gdal to be build against grass. Otherwise we need gdal to build
> > grass with general gdal support (i.e. with support for other raster
> > and vector formats).
> >
> > So the build order is
> > - create grass development libraries
> > - build gdal
> > - build grass
> >
> > Since I can not make gdal build depend on grass and grass build
> > depend on gdal in the same time  I only see one solution to get both
> > pacakges in a clean way into debian:
> >
> > grass is splitted into two completely independent packages. The
> > first one is just meant to build the development packages
> > (libgrass-dev) and doesn't create any binary packages at all. The
> > second one does build grass and libgrass.
> >
> > Disadvantage:
> > - The grass src will be included twice in debian :-(
> >
> > Other suggestions? Am I overlooking something?
>
> I think we may be overlooking something:
>
>
> It was my understanding that with the latest version of gdal 1.2.3 (not
> yet in debian) that Radim's patches had been applied and the conflict no
> longer existed. I am not sure though? guys?

No, the patches resolve the conflict between libgrass and 
GRASS 5.7 libs.

Here is what I have already sent to Cavallini:

> This is question for Glynn, I think, send it to devel list.
> 
> I think that now it is possible, but not optimal. I dont quite
> understand 
> "first one is just meant to build the development packages
>  (libgrass-dev) and doesn't create any binary packages at all."
>
> GDAL depends on libgrass_I, libgrass_vask, libgrass_gmath,
> libgrass_gis and libgrass_datetime but libgrass_vect
> depends on GDAL, so it is impossible to put all GRASS libraries
> to one package. 
> It will become even worse once I write OGR driver for GRASS.
> 
> Another bad solution could be to built also static libraries
> for GRASS and compile GDAL using static libraries.




Reply to: