-
Notifications
You must be signed in to change notification settings - Fork 145
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
VS2019 build using CMake #951
Comments
VS2019 Error messages. Apparently it is not related to USE_EXTERNAL option, but rather compiler detection. So it is rather strange. Even if I add "-D USE_EXTERNAL=1" as the additional command line option to CMake, it still has the same issues.
|
Looks like my VS2019 installation is broken. I will try again later. |
Now it is a bit better. Need to figure out the installation of flex and bison.
|
After running
|
But the build process failed. Something is still wrong. Click for full build log
|
Strange, removing the two files and then adding them back see to fix the issue.
|
Restart the whole thing again and everything is okay.
|
But once the option to build sharedlib, the build will fail. |
I am trying to build avrdude by following the instruction which seems to be very different from other projects I know of (hidapi, libftdi, libuvc, etc).
https://github.com/avrdudes/avrdude/wiki/Building-AVRDUDE-for-Windows-using-Visual-Studio
No issues in the first three steps. But I can not find the CMake option USE_EXTERNAL.
4) Set the CMake option USE_EXTERNAL to True by checking the Value checkbox.
Sorry that I may miss something obvious as I have not really used CMake inside VS.
Motivation: I prefer to use dynamic link with libusb, libftdi and hidapi. As a tester I routinely test libusb, libftdi and hidapi git head under different OS and different compilers, so it is much more convenient for me to use dynamic link.
The text was updated successfully, but these errors were encountered: