[bt-devel] Which SWORD on Windows?

[Greg Hellings]

Martin,

On Thu, May 7, 2009 at 3:03 AM, Martin Gruner <mg.pub at gmx.net> wrote:
> Hi Greg,
>
> if possible we should change the sword detection logic to work without pgk-config, so that it works on linux and windows (and mac, possibly).

The logic that is in the "Windows only" section right now I designed
so that it *ought* to work on *Nix as well and still find most of the
normal install locations (including if one uses fink on a Mac or
installs to the normal fink directory of /sw).  The only part that I
didn't duplicate was the "find the right version" logic, since I
almost always work off of SVN HEAD or at least the latest tarballs.
However, I believe that CMake provides mostly painless ways of testing
for the presence of pre-processor definitions in header files which
could be added to that area.

If you want to give it a spin on Linux to see if it works, we can work
from there.  It would help everyone, I think, if we combined that
logic.  Just be careful to watch for, again, appending the extra
"sword/" to the include path that messes things up when installing out
of the original un-tarred SWORD sources on Windows.

--Greg

>
> mg
>
> am Donnerstag, 7. Mai 2009 um 09:59 schrieben Sie:
>
>> Are we happy enough with our performance relative to SWORD 1.6.0RC3
>> for me to package with that on Windows?  Since we're not using
>> pkg-config to detect the version of SWORD on Windows, I more or less
>> have to manually set in the CMake which version so that BibleTime
>> compiles with the proper flags.  Alternatively I could figure out how
>> to extract that information from the SWORD headers directly.  What's
>> y'alls preference?
>
>> --Greg
>
>> _______________________________________________
>> bt-devel mailing list
>> bt-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/bt-devel
>
>
>
> _______________________________________________
> bt-devel mailing list
> bt-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/bt-devel
>