From: Xiaofan C. <xia...@gm...> - 2010-08-23 02:25:06
|
On Mon, Aug 23, 2010 at 9:38 AM, Peter Stuge <pe...@st...> wrote: > Personally I think this thread is about us learning what seems like a > good way to organize files that will be installed by an installer. > Say if the installer will install the binary snapshots to the C:\Program Files\libusb-1.0; then I think a way to do this is like the following. The installer also can drop the x64 binary if the system is 32bit Windows. For 64bit Windows, it is good to have both sets. Also I am omitting the files like Authors.txt, Copying.txt, readme.txt, changelog.txt, etc. They probably should reside in the root directory. Here I am treating lsusb.exe and xusb.exe as having "higher status" since they are good for debugging purpose. bin x86 libusb-1.0.dll lsusb.exe xusb.exe x64 libusb-1.0.dll lsusb.exe xusb.exe lib MinGW32 static libusb-1.0.a import libusb-1.0.dll.a MinGW64 static libusb-1.0.a import libusb-1.0.dll.a MSVC32 static libusb-1.0.lib import libusb-1.0.lib MinGW64 static libusb-1.0.lib import libusb-1.0.lib include libusb.h Example lsusb.c xusb.c dpfp.c If we treat lsusb.exe and xusb.exe as not having that higher status, then the following organization might be good. dll x86 libusb-1.0.dll x64 libusb-1.0.dll lib MinGW32 static libusb-1.0.a import libusb-1.0.dll.a MinGW64 static libusb-1.0.a import libusb-1.0.dll.a MSVC32 static libusb-1.0.lib import libusb-1.0.lib MinGW64 static libusb-1.0.lib import libusb-1.0.lib include libusb.h Example lsusb.c xusb.c dpfp.c binary x86 lsusb.exe xusb.exe dpfp.exe x64 lsusb.exe xusb.exe dpfp.exe -- Xiaofan |