Quote:
Originally Posted by Serpentine
It works fine when everything is correctly detected, but if you need to do manual configuration it's pretty tricky to get a quick overview of things. The gui also somewhat guides you through problems.
It sounds like you used the zip, rather than the installer to 'install' cmake, if so it can get quite annoying in regards to not finding the cmake detection rules and stuff, since it will work, but tries to look for stuff in PATH, rather than the local directory... it seems anyway. Just remember that if you've manually moved libs and sdk's around, cmake will not be able to guess that, you may have to tell it where your new location is (as it does find some stuff from registry keys).
Not sure about VS Express, but since there's no MFC or anything like that, it may work.
|
Thanks for your help
I installed everything from downloaded install files, no manual trickery at all except for custom location (but I don't believe that being installed on d: instead of c: will matter).
I get a lot more, and uglier, error messages from the cmake-gui than from cli, I strongly suspect that the problem is that I miss something obvious. Hence the request for notes from someone who did manage to set it all up.
The path problem was my mistake, I set the path for my user, while the SDK cmd runs as admin.
On a side note I'm comfortable with the cli, even on Windows, I have a full range of relatively POSIX-compliant cli utilities installed on my Win7 computer at work (and my Win7 partition at home). Highly recommended if you're used to Linux/Unix/BSD