On Tue, May 15, 2012 at 08:01:55AM -0600, we recorded a bogon-computron collision of the <ru...@bogodyn.org> flavor, containing: > On Tue, May 15, 2012 at 06:55:25PM +1000, we recorded a bogon-computron > collision of the <c...@stagecraft.cx> flavor, containing: > > Evening All, > > The latest Proj4 release, 4.8 doesn't install projects.h anymore thus > > breaking the Xastir build if configured for gdal. > > I do not follow proj's development mailing list --- this issue surely must > break lots of other projects, since including projects.h used to be the > correct way to get at a lot of proj.4's utility functions, and there > are still some functions like "dmstor" that are only declared in > projects.h. Now it appears that "proj_api.h" is the intended high-level > include, so it may be that Xastir's use of proj.4 can be changed to use > proj_api.h instead. In fact, a quick look at it suggests that that will work > Just Fine for Xastir. Could you check that replacing "projects.h" with > "proj_api.h" works fine? I won't have time to test until later this week, so > if you can try that out it would speed the process.
A lot of the stuff in projects.h was apparently considered "private" and the project has rudely stopped installing projects.h even though no warning was given that it was deprecated (a friendlier way to do this would be to have at least one release where including projects.h would have spit out a warning). One of the things Xastir uses was one of those things in projects.h that is considered "private", a structure definition. This is a reasonable thing to make private, as the internal details of the structure should not be exposed to the world, and access to the internals should be provided by an API (so that the structure can be changed as needed without requiring all code that uses the library to be fixed). Fortunately, Xastir only used a pointer to that type of structure to pass to various pj_ calls, and the API provides a typedef for a pointer of that sort. I'm going to commit the simple, two line change now, since it does compile and should not be an issue. I have tested it once by viewing a USGS topo in Xastir, and it worked fine, so I have confidence that the change is robust. -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "And, isn't sanity really just a one-trick pony anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit!" --- The Tick _______________________________________________ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
