-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UX hurdels on Windows #24
Comments
It was requested by users, didnt want to add stuff to their path. For most users, it is ok to add things to the path, but if someone wants it the other way and we can handle, we do it :)
Yes, I suggest that too! It has been a long requested (even ourselves) features, so lets add it to our issues:
Yes, that is true. In fact, bii setup:cpp was an auxiliary helper intended for novice C++ people, students, organizing workshops, etc. As long as you have CMake>3.0 available and one VS, everything is ok, no need to run it at all. Probably we will deprecate it at some point, but by now it is handy (e.g. I sometimes use it in travis-ci)
I agreed (past tense) with you, and former versions of biicode were very interactive for such things. But then it happened that a vast majority of users largely preferred command line options than interactive commands. We keeped both for a while, but at the end was a nightmare to develop and maintain (testing interactive commands in multi-platform is a pain) and we finally dropped interactivity. For seeing available generators you can just run:
As we use the generators as defined by CMake (also there are generators for 64 bits or ARM architectures in some Visual), they are not really separate targets. As for the targets (like Emscripten or Android), our current approach is user extensibility, but it is hard to offer them as options. Check for example: https://www.biicode.com/diego/rpiwin, that install a xxx_toolchain.cmake in your project, and that can be loaded with "bii configure -t xxx". But we still have not integrated xxx inside biicode, and I doubt that it should be done, as it makes more complex for toolchains to quickly evolve and adapt particular user needs. I have largely wanted to have an Emscripten toolchain for biicode, hopefully someone contributes one the same way as the RPI-win above one.
|
The purpose of this ticket is to describe some user experience hurdles on windows for a first time user.
Preconditions: I had CMake 3.2 and Visual Studio 2013 installed.
bii-win_3_0.exe
Windows+R
, typecmd
, pressEnter
Problems:
bii setup:cpp
does not detect Visual Studiobii build
does not automatically fall back to NMake/Visual Studio if MinGW isn't installedI suggest to use Visual C++ as default on Windows, as its part of the Windows SDK, which is "free" and superior to MinGW in many aspects (compatibility, 64bit, Microsoft language extensions, ...)
As for configuration: I think it'll be nice to have an interactive list to choose from, e.g.:
Thanks for making such a great tool. Keep up the good work! 👍
The text was updated successfully, but these errors were encountered: