<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Thank you! For the codebase that you updated, is there somewhere that I can download it to see the changes?</div><div class=""><br class=""></div><div class="">Xcode is giving me warnings, not errors, so it is technically compiling ok in that regard. (However, that does not necessarily mean that it’s ok to compile things that way.)</div><div class=""><br class=""></div><div class="">Manfred and Jaak both wrote earlier in this thread regarding how it runs on Mac and Linux. There’s issues in both cases.</div><div class=""><br class=""></div><div class="">The last official release of PocketSword was not compiled for 64-bit as far as I can tell from the download on the website for it. The project’s setting is set for 32-bit only, and not for 64-bit, though I could be mistaken.</div><div class=""><br class=""></div><div class=""></div><div class="">Your welcome reg. the bug report.</div><div class=""><br class=""></div><div class="">-TS</div><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 23, 2016, at 1:44 AM, Troy A. Griffitts <<a href="mailto:scribe@crosswire.org" class="">scribe@crosswire.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class=""><p class="">Dear TS,<br class="">
</p>
Thank you for the spreadsheet. I've had a review of the implicit
cast warning and determined where the casts were safe and added
explicit casts. This should remove most of these warnings for you.
Have you actually had a problem compiling SWORD for 64bit or were
just concerned about warnings? Manfred and Nic should be able to
answer better, but I'm quite sure we've been running 64bit on OSX
for quite some time; not sure about iOS.<br class="">
<br class="">
Thanks also for the report on the missing [] in the delete in swld.<br class="">
<br class="">
You should have better results with svn HEAD. Please keep us
posted.<br class="">
<br class="">
Troy<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">On 10/19/2016 12:58 PM, TS wrote:<br class="">
</div>
<blockquote cite="mid:BA6C5B6F-6395-4A18-9E9F-C0FDEDF7A884@icloud.com" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
<div class="">Hi Peter, thank you for your help in this. I made
the following for you and anyone else interested. I hope it’ll
help you better identify and understand the warnings and/or type
of warnings that we are seeing. I’m not really that familiar
with how clang and llvm nor autotools works so I don’t know what
changes to suggest so this is the next best thing that I thought
of. (Perhaps it is something I should investigate…?)</div>
<div class=""><br class="">
</div>
<div class=""> In order to create the numeric breakdown that I
posted earlier, I copied and pasted the warnings Xcode gave me
into a spreadsheet and sorted the data. Here is a copy of the
final spreadsheet that was done:</div>
<div class=""><br class="">
</div>
<div class=""><a moz-do-not-send="true" href="https://dl.dropboxusercontent.com/u/1472406/XCode%20Warnings.ods" class="">https://dl.dropboxusercontent.com/u/1472406/XCode%20Warnings.ods</a></div>
<div class=""><br class="">
</div>
<div class=""> On the left columns, I’ve used formulas to
label which are warnings occurring in a Sword file or CLucene
file. Whatever is not one of those is something else, but those
are a minor amount in comparison and I think are PocketSword
files unrelated to the Sword framework files. </div>
<div class="">There’s also 3 warnings which are not 64-bit related
which I’ve marked in yellow and that I already know about.</div>
<div class=""><br class="">
</div>
<div class="">On the right side of the sheet, I separated out the
file locations and their matching warnings into separate
columns.</div>
<div class=""><br class="">
</div>
<div class="">So, overall, this should give you an organized list
of the warnings that Xcode gives providing the file name and the
warning. Next to the file names are numbers. The first number is
the row number in which the error occurs and then the second
number is the number of spaces from the left that the warning is
at. (Tabs/indents seem to count as one space)</div>
<div class=""><br class="">
</div>
<div class="">I kept it as an OpenOffice doc in order to preserve
the formulas I used to sort the errors. It should help you to
organize and sort the data if you so desire. If you can’t open
it though, just let me know and I can save it in a different
format and etc.</div>
<div class=""><br class="">
</div>
<div class="">Thank you,</div>
<div class="">TS</div>
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Oct 19, 2016, at 2:44 AM, Peter Von Kaehne
<<a moz-do-not-send="true" href="mailto:refdoc@gmx.net" class="">refdoc@gmx.net</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">
<blockquote type="cite" class="">Gesendet: Mittwoch, 19.
Oktober 2016 um 09:24 Uhr<br class="">
Von: "Manfred Bergmann" <<a moz-do-not-send="true" href="mailto:manfred.bergmann@me.com" class="">manfred.bergmann@me.com</a>>b.
Is it possible that <br class="">
<br class="">
Per default Xcode uses the C compiler of LLVM.<br class="">
</blockquote>
<br class="">
Ok. <br class="">
<br class="">
I have tried compiling with clang/llvm on Linux just now,
but likely made a few/lot mistakes....<br class="">
<br class="">
CC=clang ./configure <br class="">
make<br class="">
<br class="">
produced a few (less than 10) warnings re string/char
conversions at one point, in one function only but worked
as such. Not tried the result.<br class="">
<br class="">
CC=clang++ ./configure<br class="">
make <br class="">
<br class="">
produced the same warnings but then failed at the linking
stage. <br class="">
<br class="">
But the config.log had still ample references to gcc so I
am not sure if this was really the right approach. Can you
suggest how to change the compiler properly within the
autotools setup? <br class="">
<br class="">
Peter<br class="">
<br class="">
_______________________________________________<br class="">
sword-devel mailing list: <a moz-do-not-send="true" href="mailto:sword-devel@crosswire.org" class="">sword-devel@crosswire.org</a><br class="">
<a moz-do-not-send="true" href="http://www.crosswire.org/mailman/listinfo/sword-devel" class="">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br class="">
Instructions to unsubscribe/change your settings at above
page<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" class="">sword-devel@crosswire.org</a><br class=""><a href="http://www.crosswire.org/mailman/listinfo/sword-devel" class="">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br class="">Instructions to unsubscribe/change your settings at above page<br class=""></div></blockquote></div><br class=""></body></html>