On Thu, Nov 27, 2008 at 2:26 PM, Alexander Neundorf <span dir="ltr"><<a href="mailto:a.neundorf-work@gmx.net">a.neundorf-work@gmx.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Well, it depends on how complex the APR build process is, how good you know it<br>
and how good you are with cmake :-)<br>
<br>
You need to convert all necessary configure checks to cmake, which can take<br>
some time. APR is the apache runtime, right ?<br>
This is quite cross-platform, so maybe it has a lot of tests. Making sure that<br>
the converted ones produce everywhere the same results as the original ones<br>
can be time consuming.<br>
Is this about introducing cmake as official buildsystem for APR or just for<br>
you ?<br>
If it's just for you, it also means you have to track the changes in the<br>
buildsystem of newer versions of APR.</blockquote></div><br>The problem does indeed sound too complex for my needs, as you've emphasized. I'm creating my own open source project which depends on the Subversion library, and the subversion library has dependencies on APR, Neon, and several other libraries. It's a big complex tree of dependencies that I'm not sure how to handle. I'm new to open source projects so some advice here might be helpful. At this point I'm getting a bit off topic so I do apologize for that. My first thought on solving this problem, as you've seen, is to try to use CMake to build everything. However now it seems like a pretty bad idea.<br>