[sword-devel] Eloquent Question

[Greg Hellings]

On Wed, Apr 9, 2008 at 1:09 AM, Manfred Bergmann <bergmannmd at web.de> wrote:
> No, it has not moved out of Google code.
>  But this whole project will get MacSword 2.0 and thus the sources will
>  move into the MacSword repository.
>  Yes, the plan is to split of the Sword-wrapper but it has not been
>  done yet as we are working on the 1.4 branch of MacSword at the moment
>  and there it is not easily possible to split if off because it is too
>  tight bound into other things.
>  When we are moving to MacSword 2.0 (Eloquent again) then this will be
>  done.
>  The Wrapper which is used in Eloquent should good to hgo for that
>  already as most of the bound code has been removed.

Excellent.  At least for the time being I don't need much more than
the basic functioning of the Sword library and eventually some basic
installation.  I haven't yet figured out how the installation portion
will work in all its details, but the basic concept is starting to
become clearer as I read through the iPhone documentation.

>
>  The project is build in that a sword library, locales.d and headers
>  needs to be placed in a special path.
>  The build scripts in "sword_mac_build" folder create this environment.

I have built the whole libsword.a with an XCode project (which I'd be
happy to share), which allows me to easily build it for iPhone and the
iPhone Simulator or for Mac OS X.  I have built a few of the utilities
(both the buildtest.cpp and installmgr.cpp) from the sword library on
OS X against my XCode version of the library and both of the
executables work as expected.  Since the Eloquent wrapper compiled as
cleanly on OS X as possible once I linked in my libsword build from
the XCode project and pointed towards the headers, I imagine that the
wrapper portion alone would build cleanly against the iPhone SDK.
Tomorrow I'll try adding a target for a framework build of it to your
Eloquent project and see how things turn out.

Hopefully I'm not far away from at least a rudimentary executable that
links and builds against the iPhone simulator.  I should have most of
the program basics worked out by the time I purchase an actual iPhone,
which should be this summer, about the same time that the App Store
would be opened and applications would become generally available.

>
>
>  Manfred
>
>
>  Am 09.04.2008 um 04:52 schrieb Greg Hellings:
>
>
>
>  > Manfred (and anyone else working on Eloquent),
>  >
>  > I built Eloquent with little trouble, based off of the version of the
>  > Sword library that I had built from XCode.  An inquiry - have you yet
>  > moved out of the Google Code area and into another repository (I
>  > thought there was something similar to that mentioned in Eloquent's
>  > future, but I'm not sure)?  Are you planning to split off the
>  > Sword-wrapper portion of your code to make it a reusable
>  > library/framework?  Also, what directory is Eloquent designed to be
>  > placed in for building, relative to the Sword library?
>  >
>  > --Greg
>  >
>  > _______________________________________________
>  > sword-devel mailing list: sword-devel at crosswire.org
>  > http://www.crosswire.org/mailman/listinfo/sword-devel
>  > Instructions to unsubscribe/change your settings at above page
>
>
>  _______________________________________________
>  sword-devel mailing list: sword-devel at crosswire.org
>  http://www.crosswire.org/mailman/listinfo/sword-devel
>  Instructions to unsubscribe/change your settings at above page
>