Feature #3951
closedConsider adopting an installation directory scheme
0%
Description
The default installation directories of installers for Windows doesn't adhere to a consistent folder naming scheme. Moreover, default folder names contain spaces which makes it more cumbersome to specify paths in build scripts.
A folder hierarchy scheme similar to Qt's would bring several benefits:
- Consistency for the sake of consistency (the trivial argument)
- No spaces in folder names
- Easier management of various Wt versions based on releases, compilers and CPU architecture.
- A single top folder 'Wt' would look nicer.
Here is an example folder hierarchy from Qt:
Qt/
5.3/
clang_64/
bin/
lib/
...
5.4/
clang_64/
bin/
lib/
...
Updated by Wim Dumon about 9 years ago
- Status changed from New to Resolved
The current scheme is:
- .lib files go in lib
- .exe, .dll, .bat, .pdb or whatever else is required for proper execution go in bin
- include files go in include
Examples are hidden in lib/Wt/examples
The resources folder is hidden in lib/share/Wt/resources
I don't think we have spaces in any of the directories? If I unzip the SDK zip file, I see Wt-3.3.2-msvs2010-Windows-x86-SDK. The name of this directory already contains the compiler version and 64/32 bit mode. Debug libraries have a 'd' appended to the library name, except for the boost libraries, which use the typical boost naming scheme.
So compared to the boost scheme we collapse three directory levels in one directory name. A matter of taste? You can still unzip the Wt SDK archive in c:\Wt and you would have effectively the same scheme...
Best regards,
Wim.
Updated by Kayra Akman about 9 years ago
Hi Wim,
I was thinking about the suggested installation path by the installers. The suggested path contains spaces, e.g. "C:\Program Files (x86)\Wt 3.3.3 msvs2013 x86".
Regards,
Kayra
Updated by Koen Deforche over 8 years ago
- Status changed from Resolved to Closed