Daniel Glassey wrote:
Lynn Allan wrote:
Troy wrote:
PS. I don't think we can add the VC6 project files to clutter our
source directories. If you can get them to follow the same theme as
our
other project files, then we can consider adding them; however,
we're
really close to a final release f
Lynn Allan wrote:
> Troy wrote:
>
>>PS. I don't think we can add the VC6 project files to clutter our
>>source directories. If you can get them to follow the same theme as
>
> our
>
>>other project files, then we can consider adding them; however,
>
> we're
>
>>really close to a final releas
Thanks for the guidance ... I had the impression that attachments were
frowned on ... but I guess they are fairly commonplace anymore ... in
any case, I also provided a link to the .patch file to be downloaded.
I probably could/should have .zipped that
>> lcdbible.sf.net/misc/sword_examples-cmdli
Lynn,
I found in submitting patches to JSword that it was better to zip the
patch and give it as an attachment as it prevented the wrapping of the
patch. When the patch wraps then the person who applies the patch has
to join the lines back together properly. For small patches it is not a
big de
Troy wrote:
> PS. I don't think we can add the VC6 project files to clutter our
> source directories. If you can get them to follow the same theme as
our
> other project files, then we can consider adding them; however,
we're
> really close to a final release for 1.5.8-- but I would still like
th
> Could you please submit a patch for inclusion. It would make my
> life much easier than submitting the entire changed file and me
having
> to diff and manually make the changes. You should be able to run,
from
> the top level of your tree, a command similar to:
>
Below are results of svn patch
Lynn,
Thanks for the added example lines to the usage for the examples and
such. Could you please submit a patch for inclusion. It would make my
life much easier than submitting the entire changed file and me having
to diff and manually make the changes. You should be able to run, from
the
> I think examples and tests are less important, but
> we can see about adding projects for them also.
Your call ... I found the test\*.cpp files to be very helpful to
debug-step-around in the sword-api to figure out how it works. Other
than biblecs and search.cpp, there isn't sample code to learn
Lynn Allan wrote:
If it would help, I put together a series of vc6 .dsp project files
for sword\examples\cmdline and sword\tests. Also, I incorporated some
changes in some of the usage messages to hopefully make it a little
clearer what the cmdline expects. In addition, there is a vc7.1
project for
From: "Chris Little" <[EMAIL PROTECTED]>
> The library and diatheke now build & diatheke runs correctly, using
VC++
> 6 and 7.1.
Thanks. Much better.
If it would help, I put together a series of vc6 .dsp project files
for sword\examples\cmdline and sword\tests. Also, I incorporated some
changes i
The library and diatheke now build & diatheke runs correctly, using VC++
6 and 7.1.
--Chris
Chris Little wrote:
Lynn Allan wrote:
Please have a go with it and report what you find!
Not sure what you are asking ...
lib\vcppmake\vc6 won't build ... seems to be invalid project files?
lib\vcppmake\
> ///
> SWModule *SWMgr::CreateMod(...) {
> ...
> if (pos == 1) // pos didn't get defined
> ///
>
> Am I doing something wrong or missing a step?
>
Actually, it looks like vc7.1 in debug mode detects that pos was never
initialized and (somehow or other) causes a run-time e
> I'll take a look at the VC++ projects and make sure they're building
today.
That would be great.
I wrestled with vc7.1 project files and can get diatheke, lookup, and
mod2vpl to build.
(involves url.cpp, stringmgr.cpp, swobject.cpp, etc.)
With svn 1804, however, they all crash within:
///
Lynn Allan wrote:
Please have a go with it and report what you find!
Not sure what you are asking ...
lib\vcppmake\vc6 won't build ... seems to be invalid project files?
lib\vcppmake\vc7.1 won't build ... unresolved compiler errors related
to S_IREAD and S_IWRITE
I'll take a look at the VC++ proj
> Please have a go with it and report what you find!
Not sure what you are asking ...
lib\vcppmake\vc6 won't build ... seems to be invalid project files?
lib\vcppmake\vc7.1 won't build ... unresolved compiler errors related
to S_IREAD and S_IWRITE
>
http://crosswire.org/sword/ALPHAcckswwlkrfre2
We finally have a release candidate 2 available for download! Thanks
again for everyone's patience and hard work, including all the great
feedback and patch submissions. I think I have everything in and all
known issues addressed (that we've agreed to address for this release).
Please have a
16 matches
Mail list logo
