From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3351 invoked by alias); 6 Dec 2004 06:35:39 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 3317 invoked from network); 6 Dec 2004 06:35:35 -0000 Received: from unknown (HELO bbs.darktech.org) (216.58.90.187) by sourceware.org with SMTP; 6 Dec 2004 06:35:35 -0000 Received: from localhost ([127.0.0.1]) by bbs.darktech.org (JAMES SMTP Server 2.2.0) with SMTP ID 115; Mon, 6 Dec 2004 01:35:36 -0500 (EST) From: "Gili" To: "pthreads-win32@sources.redhat.com" , "rpj@callisto.canberra.edu.au" Date: Mon, 06 Dec 2004 06:35:00 -0000 Priority: Normal In-Reply-To: <41B3FAAE.8060308@callisto.canberra.edu.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: Static linking under win32 X-SW-Source: 2004/txt/msg00160.txt.bz2 Message-ID: <20041206063500.Q9bTdtUE20SYM-_BnBxHQhKSA8VLGHXK_UPq509Aq3g@z> And here is an ugly question that has to be asked... I recently read this: http://www.javalobby.org/forums/thread.jspa?threadID=15903&messageID=918 18939&tstart=0 The implication seems to be that if my product links against a LGPL library (pthreads-win32 is such a library) then it must adhere to certain restrictions as set down by the LGPL. Two items I am specifically concerned with: 1) The LGPL library source-code must be restributed in full with the product 2) I must grant users the right to reverse-engineer my product Now, not to start a religious warfare here (since it is not my intent), but I'd like to clarify if this your intent as well? If I use it in my product, must I do these two things? Thanks, Gili On Mon, 06 Dec 2004 17:22:38 +1100, Ross Johnson wrote: >Gili wrote: > >>Hi, >> >> I'm sure this is a commonly asked question: how do I build >>pthreads-win32 under VC++ (7.1 in my case)? I am surprised you don't >>ship a project file with the source-code or discuss this in the FAQ :) >> >> >Yes, it should be in the FAQ. > >Pthreads-win32 relies on dynamic linking to provide a seemless interface >to it's POSIX functionality - using dllMain to do some per process and >per thread initialisation and cleanup. Static linking requires your >application to call some non-portable routines (see README.NONPORTABLE: >pthread_win32_process_attach_np etc). That's one reason why static >linking is not really 'officially' encouraged. > >However, there's a VS Workspace file provided that will build the DLL. >It was contributed by a user and I use it for debugging sometimes. >Perhaps you can modify that one and send me the result. > >Nor do the makefiles that I use to build and test include targets for >static linking. > >Regards. >Ross > >