From: Xiaofan C. <xia...@gm...> - 2010-08-23 10:45:37
|
On Mon, Aug 23, 2010 at 5:23 PM, Pete Batard <pb...@gm...> wrote: > OK. I don't have a problem reviewing the snapshot's file organization > when we do something official (which the current snapshots is not), > however a couple of things: > > 1. I don't see the examples ever having higher status than the library > files. Of course that is right. The include file and the libraries are the most important files. > 2. _NOBODY_ seems to have the fingerprint device that the dpfp samples > target. Providing executables for a device that almost nobody has access > to is a waste of space IMO. I agree the binary of dpfp can be dropped since it is not to be built under MinGW and MSVC. And we may not want to provide binares for Cygwin anyway. > 3. I agree that ultimately we should only provide one set of DLLs. > However, we're still pretty much in experimental stage, with DLL > interchangeability having only very recently been added. Also, since not > everybody seems to be convinced about that, I want to confirm that the > multilib MinGW32 DLLs work as well as the DDK one. As such, and as I > consider any user of non-official binaries to be OK with being guinea > pigs, I am planning to continue providing 2 sets of DLLs. Because of > that, I'll keep the MinGW/MS -> DLL/static_lib approach in my snapshot, > instead of DLL/static_lib -> MinGW/MS Okay. > But I think this discussion makes sense, since I doubt we'll have an > installer ready by the time we have an official release but we'll need > something a bit more official than the current non official snapshots. That is probably the object of this discussion. > Might also want to get started on a readme describing the files > included, that would also provide links to the API, etc, so that we have > something that looks redistributable when we go official. I agree. > It might also make sense to include the source for the examples in what > we distribute, as the expectation is that people downloading the library > snapshot are going build a libusb based application, so having some > sample code included by default could be useful. Yes. So the source lsusb.c, xusb.c, dpfp.c and dpfp_threaded.c should be provided. -- Xiaofan |