Just discovered that filemgr.cpp seems to require only a port of mkdir() and
installmgr.cpp seems to require only a port of remove() (does not need
iostream like I mention below). Of course, this is only a test of the
build. It is yet to be seen if the rest of the file functions acutally
work. Still this is encouraging.
----- Original Message -----
From: "Herb Ledebohm" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 27, 2003 12:20 AM
Subject: [sword-devel] PocketPC: swordlibppc.lib is built :)
> I had to grab the newly provided STL from MS EVC4.0 and import to
EVC3.0 --
> no iostream, though :( Also not sure of license problems with this
approach
> :(
> Also, took advantage of fcntl.h, io.h, unistd.h, dirent.h, sys\types.h and
> sys\stat.h from the wince\sword\include directory -- need to investigate
> whether these need to be updated -- but nice to be able to take advantage
of
> previous work that was done.
>
> Also, the following files are not in the PocketPC build:
> win32\dirent.cpp -- needs to be ported
> mgr\filemgr.cpp -- needs to be ported
> mgr\installmgr.cpp -- iostream needed
> frontend\swdisp.cpp -- iostream needed
> frontend\swlog.cpp -- iostream needed
> utilfuns\zlib\untgz.c -- this file is not needed for PocketPC, right?
>
> Also, the following functions are #ifdef'd out for PocketPC (temporarily):
> perror(buf); -- Not sure what is wrong here...
> unlink(buf); -- Not sure what is wrong here...
> getenv(""); -- needs to be ported
> memset(cards, 0, 256); -- Why is this function being called without os
> abstraction? (in sapphire.cpp)
>
> Comments? Suggestions?
>
> Thanks!
>
> _______________________________________________
> sword-devel mailing list
> [EMAIL PROTECTED]
> http://www.crosswire.org/mailman/listinfo/sword-devel
_______________________________________________
sword-devel mailing list
[EMAIL PROTECTED]
http://www.crosswire.org/mailman/listinfo/sword-devel
