public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Re-building stock libusb package?
@ 2015-05-29 13:54 Erik Walthinsen
  0 siblings, 0 replies; only message in thread
From: Erik Walthinsen @ 2015-05-29 13:54 UTC (permalink / raw)
  To: cygwin

I'm working on a product that needs libusb to work in a cygwin process, 
but there's a problem.  The released version (1.0.19) doesn't support 
two very fundamental features: pollfds and hotplug.  I see strong 
indications that the current git version *does* have these features, so 
I was really hoping to try using it to see if I can avoid the extremely 
nasty (and still not working) tricks I'm having to devise.

The problem is, libusb doesn't build due to w32api headers referencing 
other headers that don't exist:

   CC       os/libusb_1_0_la-windows_usb.lo
In file included from /usr/include/w32api/setupapi.h:27:0,
                  from os/windows_usb.c:28:
/usr/include/w32api/oledlg.h:28:19: fatal error: tchar.h: No such file 
or directory

Even pulling the libusb source package with the cygwin installer doesn't 
result in any different behavior.  I've tried various headers packages 
(w32api, cygwin32-wapi, mingw-w32api) to no avail.

So, my question is: how does one simply rebuild the existing 1.0.19 
package?  I'm pretty sure I can take it from there as far as getting a 
git version to compile...

Thanks!

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-05-28 20:13 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-29 13:54 Re-building stock libusb package? Erik Walthinsen

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).