public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Robin Rowe <rower@movieeditor.com>
To: pthreads-win32@sources.redhat.com
Subject: Pthread win32 lite and LGPL static linking
Date: Sat, 10 Dec 2005 21:35:00 -0000	[thread overview]
Message-ID: <439B4A27.60404@movieeditor.com> (raw)

Thanks for making pthreads-win32 available.

I lead the CinePaint project. We check-in 3rd-party lib sources into our 
CVS so that when a CinePaint Windows developer does a check-out he or 
she has everything necessary to create a build. I've cut down Pthreads 
for Windows into a much smaller lite version that contains just the 
source files needed to build CinePaint Glasgow, list enclosed below. Our 
libpthread.lib file is about 300kb.

We prefer to use small libs with static linking. FLTK, another LGPL lib 
we're using, offers a static linking exception to its LGPL license to 
accommodate that. Would you be able to do that for us, too?

Robin Rowe
--
www.CinePaint.org


cleanup.c
global.c
implement.h
pthread.h
pthread_cancel.c
pthread_cond_destroy.c
pthread_cond_init.c
pthread_cond_signal.c
pthread_cond_wait.c
pthread_detach.c
pthread_equal.c
pthread_getspecific.c
pthread_join.c
pthread_key_create.c
pthread_key_delete.c
pthread_kill.c
pthread_mutex_destroy.c
pthread_mutex_init.c
pthread_mutex_lock.c
pthread_mutex_trylock.c
pthread_mutex_unlock.c
pthread_self.c
pthread_setspecific.c
pthread_testcancel.c
pthread_win32_attach_detach_np.c
ptw32_InterlockedCompareExchange.c
ptw32_callUserDestroyRoutines.c
ptw32_cond_check_need_init.c
ptw32_mutex_check_need_init.c
ptw32_new.c
ptw32_processInitialize.c
ptw32_processTerminate.c
ptw32_relmillisecs.c
ptw32_reuse.c
ptw32_semwait.c
ptw32_threadDestroy.c
ptw32_throw.c
ptw32_tkAssocCreate.c
ptw32_tkAssocDestroy.c
sched.h
sem_destroy.c
sem_init.c
sem_post.c
sem_post_multiple.c
sem_timedwait.c
sem_wait.c
semaphore.h
w32_CancelableWait.c

             reply	other threads:[~2005-12-10 21:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-10 21:35 Robin Rowe [this message]
2006-02-28  4:38 Ross Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=439B4A27.60404@movieeditor.com \
    --to=rower@movieeditor.com \
    --cc=pthreads-win32@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).