On Tue, Feb 23, 2016 at 6:29 PM, Margherita Di Leo
wrote:
> Dear All,
>
> On Mon, Feb 15, 2016 at 5:26 PM, Rashad Kanavath <
> mohammedrasha...@gmail.com> wrote:
>
>> Hello Anita,
>>
>> I think osgeo4w needs a better structuring of how packages can be added
>> or updated based on different compil
Dear All,
On Mon, Feb 15, 2016 at 5:26 PM, Rashad Kanavath wrote:
> Hello Anita,
>
> I think osgeo4w needs a better structuring of how packages can be added or
> updated based on different compilers and version.
>
> Currently, due to ABI incompatibility upgrades are stuck. For instance
> ossim.
Hi Even,
On Sun, 21. Feb 2016 at 16:16:52 +0100, Even Rouault wrote:
> Perhaps for example for GDAL packaging, I could try to see if there's someone
> volunteering in the community to look after that one. Would be cool to have a
> gdal-dev packge for example. I guess there might be some optional d
> Early after I joined there was still Frank Warmerdam who did a lot - but
> that got less over time. Matt Wilkie did some work on python. And Martin
> Landa took over GRASS. Except for some people on-and-off that's about it
> - the rest mostly ended up here.
Jürgen,
Perhaps for example for GD
Hi Markus,
On Sun, 21. Feb 2016 at 15:47:00 +0100, Markus Neteler wrote:
> since I'm not familiar with compilation on Windows, could you briefly
> indicate what's needed / which efforts to compile GRASS GIS with MSVC rather
> than mingw given the recent efforts on the 64bit packaging? Just to bet
Hi Jürgen,
since I'm not familiar with compilation on Windows, could you briefly
indicate what's needed / which efforts to compile GRASS GIS with MSVC
rather than mingw given the recent efforts on the 64bit packaging?
Just to better understand...
Thanks,
Markus
__
Hi Rashad,
On Sun, 21. Feb 2016 at 12:13:09 +0530, Rashad Kanavath wrote:
> one is enough for an example.
Sure, but not mentioning that it's the only one, might produce a wrong
impression ;)
> I agree on the ABI stability issue and usage of C api if available and I do
> think that OSSIM should
Hello Jurgen,
On Sat, Feb 20, 2016 at 7:10 PM, Jürgen E. wrote:
> Hi Rashad,
>
> On Mon, 15. Feb 2016 at 21:56:19 +0530, Rashad Kanavath wrote:
> > Currently, due to ABI incompatibility upgrades are stuck. For instance
> > ossim.
>
> BTW that's the only example there is (at least AFAIK). And tha
Hi Rashad,
On Mon, 15. Feb 2016 at 21:56:19 +0530, Rashad Kanavath wrote:
> Currently, due to ABI incompatibility upgrades are stuck. For instance
> ossim.
BTW that's the only example there is (at least AFAIK). And that's only because
OSSIM is insisting on using the GEOS C++ API that nothing else
I'm a MS Windows User at work. I'm not a C programmer, but I know enough to
compile some code. I can help with compiling and testing on Windows 64 Bit.
Landon
On Mon, Feb 15, 2016 at 8:26 AM, Rashad Kanavath wrote:
> Hello Anita,
>
> I think osgeo4w needs a better structuring of how packages ca
Hello Anita,
I think osgeo4w needs a better structuring of how packages can be added or
updated based on different compilers and version.
Currently, due to ABI incompatibility upgrades are stuck. For instance
ossim. This was discussed in
https://trac.osgeo.org/osgeo4w/ticket/473#comment:7
IMHO,
Hi,
OSGeo4W is a great project which brings together software from lots of our
projects and many users rely on it.
The volunteer team around OSGeo4W is not that big and I wonder how
sustainable this is in the long run. From what I know, there are quite a
lot of - mostly maintenance - issues on th
12 matches
Mail list logo
