<br>Great. I'd love to receive critique of the proposed approach.<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
There must be some weakness of it :-)<br>
<div class="im"><br>
> I just wanted to add one or two points. How<br>
> can I get write permissions for the Wiki?<br>
<br>
</div>As Etienne pointed, you need OSGeo User ID<br></blockquote><div><br></div><div>I created the ID and I was able to login! .. so first step is done. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> Also as far as dependencies of GDAL driver's are concerned, we can<br>
> probably manage them using CMake superbuild support.<br>
<br>
</div>I have never heard of CMake superbuild support.<br>
Where can I learn more?<br></blockquote><div><br></div><div>This is a very good question. Actually I realized that not much information is posted on the cmake documentation. I will talk to CMake lead and find some good reference. There are projects out there (like ParaView) that uses superbuild but I will see if I can post a simple example of it. I have been using this feature now for a about year or so. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> Also I wanted to point out that, I had started cmake port of gdal last year<br>
> which is based on your work:<br>
> <a href="https://gitorious.org/cmake-gdal" target="_blank">https://gitorious.org/cmake-gdal</a><br>
<br>
</div>I see. I have seen this repo and I was wondering what is this about.<br></blockquote><div><br></div><div>Now you know -:) Actually we have been using this port for a different project. I know that 2-3 people contacted me and now using it as well. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
The cmake-gdal that used to be hosted at Google Code was a good proof<br>
of concept,<br>
but I wasn't particularly happy about structure of the configuration.<br>
So, I wanted to find out how to make it more manageable - this is<br>
important property<br>
of build configuration of large project. GDAL is large.<br>
So, I went out and looked for examples. I found Boost CMake<br>
(<a href="http://gitorious.org/boost/cmake" target="_blank">http://gitorious.org/boost/cmake</a>)<br>
I analysed their CMake configuration and code and I replicated the<br>
ideas I'd found<br>
most interesting for my purpose.<br>
That's how I came up with the configuration of SOCI.<br></blockquote><div> </div><div>Sure, we have been using this port of boost for some of our big projects. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
By the way, I'm not sure I remember correctly, but Kitware seem to be<br>
interested in supporting<br>
CMake for Boost in frame of Ryppl project<br>
("In a recent meeting between Ryppl developers and Kitware (...)"<br>
<a href="http://ryppl.org/milestones/" target="_blank">http://ryppl.org/milestones/</a> )<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div>Yes, boost developers visited Kitware I believe last year. </div><div><br></div><div>Said that, what would be our next step? Should we start from scratch? I would like to get it started as soon as possible. </div>
<div><br>Thanks </div><div> </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class="h5">
Best regards,<br>
--<br>
Mateusz Loskot, <a href="http://mateusz.loskot.net" target="_blank">http://mateusz.loskot.net</a><br>
Charter Member of OSGeo, <a href="http://osgeo.org" target="_blank">http://osgeo.org</a><br>
Member of ACCU, <a href="http://accu.org" target="_blank">http://accu.org</a><br>
</div></div></blockquote></div><br>