-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Mingw build problem #169
Comments
Here's a step by step from a clean install to successfully setup MinGW and build libusb-1.0 and stlink for MS Windows. Hopefully this helps someone.
|
Thanks. I added your comments as INSTALL.mingw 2014/1/24 dandev37 notifications@github.com
|
Thank you very much for tutorial! I also can add, that at stage 2 I add path also to c:\MinGW\msys\1.0\bin(becouse I used MSYS bash to run build). So I had done "Win+R, cmd, enter, bash, enter" and there I executed ./autogen.sh . |
FYI, if you want to connect your stlink/v2 to a USB 3.0 hub (as in most modern PCs and laptops), you must use the more recent libusb repository. Under step 5, use https://github.com/libusb/libusb instead. I have issued a pull request to update the instructions. |
request merged, thanks ! 2014-02-28 21:26 GMT+01:00 dandev37 notifications@github.com:
|
I recall mingw once having problems with long/odd path names (STLINK~1). I may remember wrong. Did you try looking at (the end of) config.log like it suggests? You should be able to spot the way the compiler test failed. |
Hi, |
Hi guys! Thank for your job! I successfully used your project on linux ubuntu and arch linux, but now I want to use it on windows. I installed latest mingw, cloned the repo and executed:
But configure crashes with:
What I do wrong? Do I need to install libusb to mingw? Where can I find it? Is there some manual for compiling texane/stlink on windows? You have alredy done a great job, and it should be some approximate instruction for compiling on windows or pre-compiled binarys.
I also tried:
But the problem remains.
Thanks in advance
The text was updated successfully, but these errors were encountered: