Skip to content
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

libudev packaging problems #3702

Closed
27thLiz opened this issue Feb 13, 2016 · 1 comment · Fixed by #3708
Closed

libudev packaging problems #3702

27thLiz opened this issue Feb 13, 2016 · 1 comment · Fixed by #3708

Comments

@27thLiz
Copy link
Contributor

27thLiz commented Feb 13, 2016

While reading through the irc backlogs I noticed this discussion (ping @punto- ):

<punto> can we statically link libudev.so? that one seems to not be as standard as the others
<punto> (for example it's not on the steam runtime, at least not the version that we use to build on the build server)
<Akien> punto: I have it in the steam runtime: /home/akien/.steam/steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libudev.so.0
<Akien> punto: Don't you mean libevdev?
<Akien> punto: libevdev was dropped so shouldn't be an issue
<punto> yeah but the build server links with libudev.so.1
<punto> and package libudev0 doesn't exist anymore
<punto> could we do the same with udev? replace it with normal code?
<Akien> No idea

The following options came into my mind:

  • Figure out a way to add statically linked libraries to the build system. Might come in handy in the future.
  • Add a code-path (enabled when libudev hasn't been found) that manually checks for joystick devices changes every (few) frame/s like the old code has. (poll_joysticks(), if you remember it ^^ )
  • Try to load the symbols at runtime (like with xinput on windows)
@punto-
Copy link
Contributor

punto- commented Feb 13, 2016

If the only thing that udev provides is notifications when devices are
connected, I like option 2. With that in place we can eventually implement
option 1 if necessary, and it's not a big deal if the engine takes a second
to realize a joystick has been plugged in.. We would have to compile
without udev by default, since the original problem was that our build
machine is linking with version 1 and steam only has version 0.. We don't
want it to fail at static linking time..

On 13 February 2016 at 16:29, Hondres [email protected] wrote:

While reading through the irc backlogs I noticed this discussion (ping
@punto- https://github.com/punto- ):

can we statically link libudev.so? that one seems to not be as standard as the others
(for example it's not on the steam runtime, at least not the version that we use to build on the build server)
punto: I have it in the steam runtime: /home/akien/.steam/steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libudev.so.0
punto: Don't you mean libevdev?
punto: libevdev was dropped so shouldn't be an issue
yeah but the build server links with libudev.so.1
and package libudev0 doesn't exist anymore
could we do the same with udev? replace it with normal code?
No idea

The following options came into my mind:

  • Figure out a way to add statically linked libraries to the build
    system. Might come in handy in the future.
  • Add a code-path (enabled when libudev hasn't been found) that
    manually checks for joystick devices changes every (few) frame/s like the
    old code was. (poll_joysticks(), if you remember it ^^ )
  • Try to load the symbols at runtime (like with xinput on windows)


Reply to this email directly or view it on GitHub
#3702.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants