I still have problem linking SWORD and ICU with BCB6. I almost give up. I would like
to download the changes you made with all the files needed to get SWORD compiled and
likned with BCB6.
Paul
-----Original Message-----
From: Chris Little [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 9:28 AM
To: Daniel Glassey
Cc: [EMAIL PROTECTED]
Subject: Re: [sword-devel] Borland project updates
On Mon, 27 Jan 2003, Daniel Glassey wrote:
> Thanks Chris :)
> I've committed the bigger changes that change the biblecs app to
> mostly use tnt controls so it'll need checked again.
Cool, I'll take a look & see if anything requires patching up for BCB5.
> I added a BCB6 project to /lib/bcppmake since it is a different file
> format and needs an extra define.
> I called it libsword6icu to indicate that it is for BCB6 and uses
> icu. Does that sound like a reasonable naming standard and if so
> could you rename the BCB5 one to libsword5icu? I not, I think we
> should come up with some kind of naming standard so please suggest
> other ideas.
In my opinion, we should make directories under bcppmake called
bcb5/bcb6/.... I made a vcppmake/vc6 directory for VC++ 6.0 project files
with the intention of making a vc7 some day according to the same
principle. I just modified the existing libsword project since that's
where Troy had put it and what he had named it.
Blessings,
Chris
_______________________________________________
sword-devel mailing list
[EMAIL PROTECTED]
http://www.crosswire.org/mailman/listinfo/sword-devel
****************Internet Email Confidentiality Footer******************
Privileged/Confidential Information may be contained in this message. If
you are not the addressee indicated in this message (or responsible for
delivery of the message to such person), you may not copy or deliver
this message to anyone. In such case, you should destroy this message
and notify the sender by reply email. Please advise immediately if you
or your employer do not consent to Internet email for messages of this
kind. Opinions, conclusions and other information in this message that
do not relate to the official business of The Shaw Group Inc. or its
subsidiaries shall be understood as neither given nor endorsed by it.
_______________________________________________________________________
The Shaw Group Inc.
http://www.shawgrp.com
0]zx%luޕ"+m+0j)fjb?
+uׯz
