[bt-devel] Windows Build status
Greg Hellings
greg.hellings at gmail.com
Tue Feb 24 09:01:43 MST 2009
On Tue, Feb 24, 2009 at 4:30 AM, Eeli Kaikkonen
<eekaikko at mail.student.oulu.fi> wrote:
> Quoting Greg Hellings <greg.hellings at gmail.com>:
>
>>>
>>> We should somehow make this as easy as possible for newcomers. Maybe a
>>> zip
>>> package which includes all the tool and library packages?
>>
>> It's probably better to setup a wiki page like the Gnomesword team did
>> and document exactly what to do and how to do it - I know it would be
>> a nightmare for me to think of exactly what I did more than a few days
>> into the future. Perhaps tomorrow I'll see about getting it down in
>> writing.
>
> Of course we have to have a wiki page, but it's much easier to download one
> zip from our sf repo than to follow several links, especially if we use the
> unpackaged (i.e., with no .exe installer) mingw version. Additionally we can
> avoid licence problems, especially if we use static build for windows. In
> that case we would be obligated to distribute the source code of a GPL
> library. Or even if we use prebuilt .dll's and want to distribute them.
Alrighty - I don't really know what the licensing of the MinGW system
is, but I know it has come distributed with a few other things I've
downloaded in the past days, so I would imagine we could use that
method too. At the moment, it just doesn't build with MinGW because
of the errors I related with the lucene headers.
>> config.h makes more sense - it's more in keeping with other software
>> I've seen - and the issue is just an ordering of the include
>> directories. Obviously it's a quirk of CMake, since the problem
>> doesn't appear in Mac or Linux. I'd say leave it be and we can just
>> shuffle it around when we make the project file in VS.
>
> Ok, if it doesn't cause any other problems.
There are no other problems on Windows that I've seen, and I haven't
heard any reports of issues on other systems at all.
--Greg
More information about the bt-devel
mailing list