<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38">
<TITLE>RE: [geos-devel] Thread Safe CAPI ready for review</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Chuck,<BR>
<BR>
This is all fairly new to me so I could be missing something here. I'm having trouble compiling these new changes you have under Visual Studio 2008<BR>
<BR>
1) First off all, it looks like you provided the changed files rather than a patch. Shouldn't you have provided a patch instead?<BR>
2) I presume this patch is for Trunk rather than 3.0 branch?<BR>
<BR>
<BR>
Now the error I get is this<BR>
<BR>
1>c:\projects\geos\trunk\capi\geos_c.h(32) : fatal error C1083: Cannot open include file: 'geosTS_c.h': No such file or directory<BR>
<BR>
<BR>
I assume that somehow the geosTS_c.h.in you provided is supposed to somehow get transformed to geosTS_c.h, but not quite clear how that magic happens.<BR>
<BR>
I presume it is not happening because you only provided a Makefile.am and I guess a similar change needs to happen for VC something or other?<BR>
<BR>
Haven't tried the changes on my OpenSUSE VM yet, but hope to at some point.<BR>
<BR>
Thanks,<BR>
Regina<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: geos-devel-bounces@lists.osgeo.org on behalf of Chuck Thibert<BR>
Sent: Fri 11/28/2008 4:19 PM<BR>
To: GEOS Development List<BR>
Subject: [geos-devel] Thread Safe CAPI ready for review<BR>
<BR>
Hello,<BR>
<BR>
I've attached the changed and new files to ticket 210. This is based on<BR>
revision 2230, which was the latest when I updated today (Nov. 28.)<BR>
<BR>
I don't have access to Windows or Mac development boxes for testing.<BR>
This was developed on Fedora Core 8. Would love if someone could check<BR>
these out for me on Mac/Windows.<BR>
<BR>
Thanks,<BR>
Chuck<BR>
<BR>
<BR>
On Thu, 2008-11-27 at 14:17 -0500, Chuck Thibert wrote:<BR>
> Hi Paul,<BR>
><BR>
> RE: Thread Safe API. I'm looking to finish up in the next day or so,<BR>
> assuming no gotchas. Just finalizing the last changes for the old API<BR>
> calling the new one. I'm pushing to have it ready for review by Friday,<BR>
> or early next week.<BR>
><BR>
> Chuck<BR>
><BR>
> On Thu, 2008-11-27 at 10:08 -0800, Paul Ramsey wrote:<BR>
> > Hi all, what features are we waiting on for the 3.1.0 release?<BR>
> > In the interest of "getting as much in as possible" I wouldn't mind<BR>
> > seeing the thread-safe API in place prior to release. What is the<BR>
> > timeline on that? Are there other functions we want to expose in the<BR>
> > CAPI before release, is the other question, since it will be a while<BR>
> > before our next opportunity.<BR>
> ><BR>
> > P.<BR>
> > _______________________________________________<BR>
> > geos-devel mailing list<BR>
> > geos-devel@lists.osgeo.org<BR>
> > <A HREF="http://lists.osgeo.org/mailman/listinfo/geos-devel">http://lists.osgeo.org/mailman/listinfo/geos-devel</A><BR>
> _______________________________________________<BR>
> geos-devel mailing list<BR>
> geos-devel@lists.osgeo.org<BR>
> <A HREF="http://lists.osgeo.org/mailman/listinfo/geos-devel">http://lists.osgeo.org/mailman/listinfo/geos-devel</A><BR>
_______________________________________________<BR>
geos-devel mailing list<BR>
geos-devel@lists.osgeo.org<BR>
<A HREF="http://lists.osgeo.org/mailman/listinfo/geos-devel">http://lists.osgeo.org/mailman/listinfo/geos-devel</A><BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
</STRONG></P></BODY></HTML>
<P><hr size=1></P>
<P><STRONG><font size="2" color="339900"> Help make the earth a greener place. If at all possible resist printing this email and join us in saving paper. </p> <p> </font></STRONG></P>