[sword-devel] Next Release

[Troy A. Griffitts]

Dear Greg,

Yes, we've had to handle the windows config issue in the past and this 
is why config.h is actually committed to the source tree.  You can 
include config.h in your windows code; otherwise, if you don't want a 
code change specifically for windows, it looks like you can define 
USE_AUTOTOOLS in your project and the swordlib will include config.h for 
you.

Hope this helps.

	-Troy.


Greg Hellings wrote:
> I fully support the soon-release mantra.
> 
> On Wed, Nov 26, 2008 at 1:40 PM, Troy A. Griffitts <scribe at crosswire.org> wrote:
>> Good suggestion Karl.  Others sound like they would also like this.  May
>> I ask first for some feedback regarding current state of TRUNK?  I
>> believe we have a fairly optimized impl of the old functionality running
>> in the new paradigm of dyn versification.  We might be able to clean it
>> up by next week.  I currently understand there are two issues:
>>
>> 1) non-backward-compat change of removing VerseKey::books hardcoded
>> array.  We've talked about adding a SWORDVERSION define, but I just had
>> a 'doh' moment and realized we have: pkg-config --modversion sword
> 
> Great idead... except for the current push to get out versions built
> on Windows.  Unless you're in the Cygwin environment, you have no
> access to pkg-config.  That's bit me more than once.  Having a
> SWORDVERSION define would be fantastic, IMO.
> 
> --Greg
> 
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page