This is the mail archive of the pthreads-win32@sources.redhat.com mailing list for the pthreas-win32 project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
No! That's the GPL (and even then not strictly true IMO), not the LGPL.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 productNo! Not necessarily IMO.
Now, not to start a religious warfare here (since it is not mySome time ago there was a proposal to change the license to a more liberal Open Source license, but any change would require the agreement of everyone who has contributed significantly to the project, if not everyone who has contribributed. I guess if the current IBM-SCO case goes badly, then that proposal would be quickly resurrected.
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?
Regards. Ross
On Mon, 06 Dec 2004 17:22:38 +1100, Ross Johnson wrote:
Gili wrote:
Hi,Yes, it should be in the FAQ.
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 :)
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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |