Opened 16 years ago
Closed 6 years ago
#15 closed enhancement (fixed)
Finish configure.cmd
| Reported by: | Dmitry A. Kuminov | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | Qt 5 |
| Component: | General | Version: | 4.5.1 Beta 1 |
| Severity: | low | Keywords: | |
| Cc: |
Description
Fully implement configure.cmd functionality which includes:
- Process command line options to alter Qt configuration.
- Generate Makefiles for all .pro files in the source tree.
- Resolve all remaining @todo's.
Change History (4)
comment:1 by , 16 years ago
| Type: | defect → enhancement |
|---|
comment:2 by , 15 years ago
| Milestone: | Qt GA → Qt Enhanced |
|---|---|
| Severity: | → low |
comment:3 by , 6 years ago
| Milestone: | Qt Enhanced → Qt 5 |
|---|
We completely changed the way configure works in Qt5. And for Qt4 this is just what it is.
comment:4 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I don't actually think that command line options are so much important for the GA -- there is no such a practice (or a real need) to customize the libraries on OS/2; and we are providing the binary build that is recommended to use with real distributed applications anyway. Those who really needs to tailor the build will be able to do it by editing configure.cmd directly.
What about the .pro files for examples and sources, it's also questionable as it will only increase the build time while, again, we provide the pre-built versions of demos and examples and if somebody wants to build them on his own, it's easily doable manually (qmake + make).
Moving the task to Enhanced.