#235 closed defect (fixed)
Build process broken
| Reported by: | rudi | Owned by: | |
|---|---|---|---|
| Priority: | blocker | Milestone: | Qt 4.7 |
| Component: | General | Version: | |
| Severity: | low | Keywords: | |
| Cc: |
Change History (4)
comment:2 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed in r1000.
It's not quoted names, it's the backslash. CMD.EXE's "cd" and "mkdir" commands can't deal with it.
BTW, you may report build break issues like that directly to my JID (dmik at dmik dot org) so that I can instantly fix them. Unfortunately, I can't test each qmake scenario to make sure there are no regressions (and not always think enough to predict those problems upfront).
comment:3 Changed 13 years ago by
"mkdir-p.cmd" works with trailing backslashes but falls over with the quotes. CMD.EXE's "cd" command does exactly the opposite.
It's absolutely clear to me that you can't test everything. Not to talk about the time a full build will take.
comment:4 Changed 13 years ago by
Yes, you are right, mkdir-p.cmd is capable of doing slashes (just because the code strips it before passing it to SysMkDir?() which can't also tolerate it). I also added support for quotes in r1002 as it was just simple (thanks to the Tokenize routine I have around for long) and important as long as we don't move to POSIX.
Fuck, I really hate all this stupidancient OS/2craptools like CMD.EXE do really require too much effort to support them. We should move to sh and friends ASAP.