-
Notifications
You must be signed in to change notification settings - Fork 141
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
Unable to build libavrdude dynamic and static library with CMake buildsystem #952
Comments
This was used as a reason against CMake in the libusb build system discussion. But I believe something can be done as in the libftdi example. |
@subnut Are you able to build the share library? Somehow I have no issues to build the static library under MSYS2 (mingw32 and mingw64) but not able to do the same for the shared library. click for the full build log
|
@mcuee Yes, I am. But I am on Linux, and I do not have a Windows system nearby to test. |
Thanks. I will try your patch as well to see if that helps. Or maybe I will try to fix my MSY2 MinGW32/64 build. |
@mcuee I don't think my patch is going to fix that. https://stackoverflow.com/a/57932764
|
@dl8dtl Building the avrdude libraries is getting quite a bit attention. I spend very little time looking at this because I was under the impression that the avrdude library is not really used. Also, the avrdude code base does not really seem to be prepared for building libraries (i.e. external references such as What's your view on this? Are libraries part of the avrdude delivery, if so, both static and dynamic libraries? |
Basically, the separation of the library backend from the CLI frontend has been a long-standing wish, but it's still kinda work in progress, see for example issue #774 |
How can I shared a version of avrdude binary which is dynamically linked to libusb-1.0.dll and libhidapi.dll under Windows? I do not really need to build the shared library. #955 has been raised for this issue. |
I guess my question is whether we accept PRs for this, or just call the libraries 'deprecated' until there is a real need for it. Right now, I see very little value in PRs trying to build avrdude dummy DLLs, just for the sake of building it. It would be a whole different matter if there was a real project behind this. |
Pull requrst #960 was closed -- but it actually helps to fix the issue under macOS even though it can not help on Windows. |
Right now macOS homebrew is using a trick to build shared library. I can use the trick to build shared library and static library with seperate build, which seems to be the way to go for CMake.
|
As of now, there is no way to build shared libavrdude.dll under Windows, either with MinGW or MSVC. Example using MSYS2 mingw.
|
Under Linux, there is no issues build the static link and dynamic link libraries. The default
But it is also easy to build shared library
|
Just want to mention this issue is still there.
|
It seems to me that most CMake based project will require seperate build for static and dynamic library. So the original request can be closed as not planned. |
But the Windows dynamic library build is a bug to me. So I will create a new issue for that. |
Regarding |
Previously,
./configure
would build both static and shared libraries in one go.Now, using the new CMake build, I am unable to do so.
Please tell me how to do so.
The text was updated successfully, but these errors were encountered: