Static build attempts to use dynamic libudev

Open
#576 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cmake, cpp, linux

Research direction

Start from the CMake configure path used with -DBUILD_STATIC=ON and find where udev is detected and passed to the linker (CMakeLists and related find modules). Confirm the link line requests -ludev without requiring libudev.a. Done when a static configure fails early if the static udev library is missing, instead of failing at /usr/bin/ld.

Written by the indexing model from the issue text.

Description

enhancement

If you configure with cmake -DBUILD_STATIC=ON .., the system will happily build until:

/usr/bin/ld: cannot find -ludev: No such file or directory

Of course, when you look at the link directory, you find libudev.so and don't think anything about the fact that libudev.a is the thing that is missing.

Yes, this is nominally user error. However, a static build really should examine for the existence of the static library up front since the ld error is so obtuse.

Thanks.

Dominant language
C++
Stars
1.7k
Forks
396
Avg merge
2d 4h
Merged PRs (30d)
15

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from trabucayre/openFPGALoader

All issues in trabucayre/openFPGALoader

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.