@matigo Something in qt's configure or the perl script that runs afterwards is not properly quoting the path when generating the qmake files. (I'm betting the latter) I'll move the tree back where I want it after it is built then fix the stupidity later.
c1xx: fatal error C1083: Cannot open source file: '2015\Projects\pcds\3rdParty\qt\src\corelib\xml': No such file or directory
Studio
c1xx: fatal error C1083: Cannot open source file: 'Studio': No such file or directory
Really? Are you kidding me? This is 2016. Choking on spaces in a path name?
@kdfrawg Not nearly as big as trying to manhandle both environments at once. This way, it's a short-term pain / setback instead of something chronic.
And my Windows 10 box just froze up. First time that has ever happened. I do not have time for this.
Migrating QT 5.5 and a variety of 3rd party things into a Visual Studio 2015 project hierarchy.
I was dead serious when I said I was eliminating the Linux/autotools stuff. I'll worry about porting it over there when what I am working on is finished and released for Windows.
This means I am backing up a fair distance but if I put it off and continue on my old course any longer, it will become the same complicated mess I've been dealing with since 2000.
@tomas The less you try to understand humans and sexuality the better. That's always been my policy anyway. :)
// @matigo @JeremyCherfas
@tomas Steal away. I'm just babbling between bouts of fighting code.
// @matigo
AI has always stuck me as a can of worms. When you let a system navigate from grey to black and white on it's own, thus establish it's own bias, there's no telling what you're going to get.
@matigo Exactly. Algorithms are bias put to work. AI is an attempt to navigate grey instead of black and white.
// @tomas