[geos-devel] 3.0.3 To Do

[Paul Ramsey]

My change merely reflects the numbers that the non-Windows GEOS users
are seeing, via the macro-based versions. I think HOWTORelease
describes the logic behind increments.

P

On Fri, Oct 24, 2008 at 9:35 AM, Sean Gillies <sgillies at frii.com> wrote:
> According to
>
> http://trac.osgeo.org/geos/log/branches/3.0/capi/geos_c.cpp
>
> The C API hasn't changed since the 3.0 branch was made, so a change of
> the API version number isn't warranted.
>
> Sean
>
> Paul Ramsey wrote:
>> I couldn't apply this patch cleanly, could someone else try?
>>
>> P.
>>
>> On Thu, Oct 23, 2008 at 10:52 AM, Sanak <geosanak at gmail.com> wrote:
>>> Ok, I had added geostest project to msvc80 solution file.
>>> Please see the attach
>>> file(geos-branches-3.0-build-msvc80_add_geostest.patch).
>>> geostest.vcproj will generate capi/test.out.
>>>
>>> I think that the cause of difference between generated test.out and
>>> test.expected is precision of floating point, but I don't know details.
>>>
>>> And another Visual C++ specific problem may be capi
>>> version.(capi/geos_c.h.in)
>>> ---
>>> Index: geos_c.h.in
>>> ===================================================================
>>> --- geos_c.h.in    (revision 2208)
>>> +++ geos_c.h.in    (working copy)
>>> @@ -51,9 +51,9 @@
>>>  #if defined(_MSC_VER)
>>>  #include <geos/version.h>
>>>  #define GEOS_CAPI_VERSION_MAJOR 1
>>> -#define GEOS_CAPI_VERSION_MINOR 3
>>> +#define GEOS_CAPI_VERSION_MINOR 4
>>>  #define GEOS_CAPI_VERSION_PATCH 3
>>> -#define GEOS_CAPI_VERSION "3.0.0rc4-CAPI-1.3.3"
>>> +#define GEOS_CAPI_VERSION "3.0.3-CAPI-1.4.3"
>>>  #else
>>>  #define GEOS_VERSION_MAJOR @VERSION_MAJOR@
>>>  #define GEOS_VERSION_MINOR @VERSION_MINOR@
>>> ---
>>>
>>> Regards,
>>>
>>> 2008/10/24 Frank Warmerdam <warmerdam at pobox.com>
>>>> Obe, Regina wrote:
>>>>> I know Frank already tested on Visual C++ Express (which is basically
>>>>> Visual 2008 Express) and got some test fail errors.  Do we have a solution
>>>>> file for that (or would people just use the msvc80 solution file for that if
>>>>> they wanted to use a solution) .
>>>> ...
>>>>> Running regression tests using geos_unitd.exe...
>>>>> ===============================
>>>>>  GEOS Test Suite Application
>>>>> ===============================
>>>>> capi::GEOSCoordSeq: ..... 5
>>>>> capi::GEOSSimplify: . 1
>>>> Folks,
>>>>
>>>> I would note that I wasn't running geos_unitd.exe, I ran geostest.exe
>>>> against capi/test.wkt and compared to capi/test.expected.  If I get
>>>> back to my windows build I'll look into the geos_unitd.exe which I wasn't
>>>> aware of.
>>>>
>>>> Best regards,
>>>> --
>>>>
>>>> ---------------------------------------+--------------------------------------
>>>> I set the clouds in motion - turn up   | Frank Warmerdam,
>>>> warmerdam at pobox.com
>>>> light and sound - activate the windows | http://pobox.com/~warmerdam
>>>> and watch the world go round - Rush    | Geospatial Programmer for Rent
>>>>
>>>> _______________________________________________
>>>> geos-devel mailing list
>>>> geos-devel at lists.osgeo.org
>>>> http://lists.osgeo.org/mailman/listinfo/geos-devel
>>>
>>> _______________________________________________
>>> geos-devel mailing list
>>> geos-devel at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/geos-devel
>>>
>> _______________________________________________
>> geos-devel mailing list
>> geos-devel at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/geos-devel
>>
>
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geos-devel
>