You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucy.apache.org by Peter Karman <pe...@peknet.com> on 2009/11/29 03:41:53 UTC

Re: [Lucy] Target platforms

Marvin Humphrey wrote on 11/27/09 1:23 PM:
> On Fri, Nov 27, 2009 at 10:21:06AM -0800, Nathan Kurz wrote:
>> More generally, it might be nice to make such goals explicit somewhere.
> 
> Yes, for example as Parrot has done with "Target Platforms" at.
> <http://www.parrotcode.org/docs/pdd/pdd01_overview.html>.
> 
>> Optimized for: 64-bit systems using GCC and supporting mmap would
>> probably be my vote.
> 
> +1.

+1

> 
>> Making MSVC a first class citizen would be fine if you think the return is
>> there.
> 
> No, as far as I'm concerned MSVC is a compatibility target. 
> 
> I think it's important for our users to provide wide portability, and that
> means supporting MSVC.  E.g. I want somebody's platform-portable wiki project
> or MVC framework to be able to integrate Lucy without hesitation.
> 
> However, Microsoft needs to work a lot harder to make my life easier as an
> open source C developer if they want first-class status.


FWIW, we make Win32 DLLs and .exe available for each Swish-e release by
cross-compiling with mingw32 on debian-based systems (I do it on ubuntu):

http://swishewiki.org/sw/index.php/Win32#Cross-compiling_for_Windows_on_Debian_or_Ubuntu

We maintain appropriate macro checks in the source code and separate makefiles
etc. The download-and-use attraction for Windows users is huge, since that's the
expectation that community holds.

I personally have no love for the MSVC stuff, and like Marvin says, M$ needs to
work harder if they want me to write free code. Swish3 (for example) has no
explicit Win32 support and I don't intend to write any, though I'd be happy to
include it if someone contributed it. That said, I'm happy to support Marvin's
desire for MSVC a compatibility target (esp since I haven't had to write any
relevant code! ;) ).

-- 
Peter Karman  .  http://peknet.com/  .  peter@peknet.com

Re: [Lucy] Target platforms

Posted by Marvin Humphrey <ma...@rectangular.com>.
On Sat, Nov 28, 2009 at 08:41:53PM -0600, Peter Karman wrote:
> FWIW, we make Win32 DLLs and .exe available for each Swish-e release by
> cross-compiling with mingw32 on debian-based systems (I do it on ubuntu):

I don't think this could work for us because of the memory mapping
requirement.  The version of FSFileHandle I'm about to submit uses
MapViewOfFile from windows.h directly.  To the best of my knowledge, MinGW
doesn't provide sys/mman.h...

  http://lists.freedesktop.org/archives/fontconfig/2006-January/001919.html

... and we need either one or the other of those headers.

However, I am curious about MinGW in a different regard.  Since Lucy currently
compiles on both GCC and MSVC, we shouldn't have any trouble compiling with
MinGW on Windows directly -- no need to cross-compile.  I believe you can
specify which C runtime DLL to link against with MinGW, right?  So it would be
possible to prepare binaries which link against MSVCRT.DLL rather than
e.g. MSVCR80.DLL.

That's very important, since every Windows box already has MSCVRT.DLL on it,
but many do *not* have later versions. 

With KinoSearch, I haven't had to worry about such things because I've made
sure that it adhered to strict C89 syntax -- and since KS has been so easy to
compile, others have always been able to build the necessary packages without
much assistance from me.

If we're going to make Lucy harder to compile, we'll have to start worrying
about such issues ourselves.

> That said, I'm happy to support Marvin's desire for MSVC a compatibility
> target (esp since I haven't had to write any relevant code! ;) ).

So long as there's someone willing to step up and write the required
Charmonizer code and limited OS-specific stuff, Lucy developers working mainly
within trunk/core don't have to bear too heavy a burden.

Marvin Humphrey