<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 20, 2013 at 8:04 AM, Ben <span dir="ltr"><<a href="mailto:cricketc@gmail.com" target="_blank">cricketc@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
Good catch - looks like I accidentally grep'd for the wrong string when<br>
I was making sure I had gotten them all. I have added the additional<br>
option of BINDIR that captures the appropriate value. You can try again<br>
now, if you'd like.<br>
</div></blockquote>
<br>
Looks good.</blockquote><div><br></div><div style>Good to hear.</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>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Also, I'm not sure it's causing anything to fail, but the name of<br>
the icu directory seems to be missing something (1.6.2_icu_).<br>
<br>
<br>
Hmm, maybe. I'm very un-knowledgeable on what the ICU stuff all is<br>
supposed to be. That could explain the missing data warnings I see when<br>
I run the modules frequently. I'll look into that.<br>
</blockquote>
<br></div>
OK. I tried running make tests, but the osistest doesn't seem to be included. It'd be nice to get the test suite passing.<br>
<br>
As a start for fixing osistest, I added osistest to the list of test programs in tests/CMakeLists.txt, and the following command to tests/testsuite/CMakeLists.<u></u>txt:<br>
COMMAND cp ${CMAKE_CURRENT_SOURCE_DIR}/*.<u></u>xml ${CMAKE_CURRENT_BINARY_DIR}<br>
<br>
osistest still fails for me, but I'm not sure it's related to cmake at all. May not be worth holding up the release if the tests pass for others.</blockquote><div><br></div><div style>Since the testsuite is really developer-only and basically only Troy uses or maintains it, I've not been on top of keeping the CMake portion up-to-date. Troy uses and maintains the autofoo for the library and so he just has them churning along as he needs. I'll see about adding the missing command - the main difference there is that I force the CMake build to be in a different directory whereas most autotools people will build in the same directory as source.</div>
<div style><br></div><div style>Did you try running the testsuite with autotools to see if it works?</div><div style><br></div><div style>--Greg</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
<br>
-Ben<br>
<br>
______________________________<u></u>_________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/<u></u>mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br></div></div>