[sword-devel] Making Import Easier

[Chris Little]

Manfred Bergmann wrote:
> 
> Am 07.04.2009 um 03:28 schrieb Chris Little:
> 
>>
>>>> they have trouble finding the Windows build of the binaries,
>>> This sounds more like an advertising/publicity/documentation issue 
>>> than a technical one?  Or it could be a packaging issue -- how are 
>>> such users getting their SWORD library onto their Windows PCs, and 
>>> doesn't it come with the utilities??  If not, why not?
>>
>> Windows builds are static and found at 
>> http://crosswire.org/ftpmirror/pub/sword/utils/win32/. This is linked 
>> from the Wiki documentation, of course. If anyone wants to make this 
>> more prominent & obvious they're welcome, but I think it's sensible to 
>> find this link within the module making documentation. (You're not 
>> really ready to use the utilities until you've at least skimmed some 
>> of the documentation.)
>>
> 
> Is it possible that we can add compiled mac tools there in a separate 
> folder?

Sure, we can do that. Is that the best option though?

We post Windows binaries because most Windows users don't have a 
compiler. We don't post Linux binaries because most Linux users _do_ 
have a compiler (or could get one quickly and easily). I don't actually 
know whether Macs come with I compiler or not.

On the other hand, if we build binaries, we know that we can ship them 
with ICU included/enabled, which is quite important.

Will we have to worry about universal binaries when we build on the 
command line?

--Chris