[sword] [sword-devel] Port to PocketPC 2002/2003?

[Darin Duphorne]

I am very interested in seeing a pocketpc version available.  I would 
be happy to test betas on my ipaq 1945, but am a mac programmer and 
don't know squat about windows or pocket pc programming.

Thank you,
Darin
Houston

On Monday, July 7, 2003, at 06:58 PM, Herb Ledebohm wrote:

> Thanks Chris!
>
> I'll start tonight by getting the source and will try to work on it 
> amap
> each night.
>
> My initial plan is to get it working similar to the QPSword version (as
> far as features and functionality are concerned).  Following that, it
> can be decided what other features to add and/or what PocketPC specific
> functionality we might want to add.
>
> I'll be in touch!
>
> Thanks, and please keep me in your prayers that the code will come
> swiftly and accurately.
>
> ...HERB...
>
> -----Original Message-----
> From: sword-devel-admin@crosswire.org
> [mailto:sword-devel-admin@crosswire.org] On Behalf Of Chris Little
> Sent: Monday, July 07, 2003 6:39 PM
> To: sword-devel@crosswire.org
> Subject: RE: [sword] [sword-devel] Port to PocketPC 2002/2003?
>
>
>
>
>> -----Original Message-----
>> From: sword-devel-admin@crosswire.org
>> [mailto:sword-devel-admin@crosswire.org] On Behalf Of Name Withheld
>> Sent: Monday, July 07, 2003 3:34 PM
>> To: sword-devel@crosswire.org
>> Subject: RE: [sword] [sword-devel] Port to PocketPC 2002/2003?
>>
>>
>> Ok, so consider me officially volunteering to start this
>> port.  I currently work for nVidia so my days are quite
>> hectic (I'm a driver / systems software guy), but I would
>> give it as much effort as I can.
>>
>> Who do I contact to get access to the source code (I assume cvs)?
>>
>> I'll dig around some more on the website to get instructions
>> on how to start this port, but feel free to email me if you
>> know the quickest way to help me get started.
>
> Just use the public CVS on crosswire.org.  Instructions are on the 
> site.
>
> The MSVC project in lib/vcppmake/vc6 is updated regularly to keep in
> sync with changes made to the Borland & GCC projects and repair
> incompatabilities that they can introduce.  It compiles current CVS
> cleanly at the moment.  That's your best starting point with eVC.  When
> an eVC library project is ready for public, it should probably go under
> lib/vcppmake/evc or similar.
>
> We had a compiling but not functioning port of the libarary a while ago
> that used a 3rd party library from Dinkumware, so a good portion of the
> work is already done.  Most of the remaining difficulties will relate 
> to
> handling any remaining STL in the library (unless it's all removed
> already) and file-system functions.
>
> --Chris
>
>
> _______________________________________________
> sword-devel mailing list
> sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
>
> _______________________________________________
> sword-devel mailing list
> sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
>