Package Details: arm-frc-linux-gnueabi-wpilib 2017.3.1-3

Git Clone URL: https://aur.archlinux.org/arm-frc-linux-gnueabi-wpilib.git (read-only)
Package Base: arm-frc-linux-gnueabi-wpilib
Description: The WPI FIRST Robotics Competition C/C++ library for the arm-frc-linux-gnueabi toolchain
Upstream URL: https://usfirst.collab.net/sf/projects/wpilib/
Licenses: custom=FRC-BSD
Groups: frc-toolchain
Submitter: calcmogul
Maintainer: calcmogul
Last Packager: calcmogul
Votes: 1
Popularity: 0.497981
First Submitted: 2016-08-17 00:45
Last Updated: 2017-08-29 21:01

Latest Comments

calcmogul commented on 2017-08-30 07:49

You mean Gazebo has trouble compiling? I found recompiling the ignition libraries before recompiling Gazebo fixed that. Once Gazebo is installed, this package builds simulation fine. I did forget to add the -PmakeSim flag to the pkgbuild though.

gazebo can't be an optdepend because simulation requires gazebo to build, and there's no non-gross way to optionally specify the -PmakeSim compilation flag depending on whether gazebo is installed. I suppose one option is making a separate package that _does_ build simulation, but it will be obsolete and likely orphaned for 2018 due to changes we made to the build process (see https://www.chiefdelphi.com/forums/showthread.php?p=1697009#post1697009).

I suppose for the average team, it would be best to remove the dependency on Gazebo entirely because it takes a while to compile and set up, and it doesn't work that well anyway.

Redrield commented on 2017-08-30 07:08

It seems to me that gazebo should most likely be an optdepend, rather than a full depend. It's not required for the library to function, and I find myself removing it as a dependency manually, because it's out of date, and having trouble compiling.

LanceB98 commented on 2017-08-29 16:05

Right now, package() is trying to install a license from "$srcdir/allwpilib/BSD_License_for_WPILib_code.txt", but it appears that the license has been renamed to "$srcdir/allwpilib/license.txt". This causes the build to fail.

calcmogul commented on 2016-12-18 14:15

The connection may also be getting reset. I don't seem to have the cert and I'm able to download the Doxygen plugin. You could try the HTTPS -> HTTP workaround in one of the answers to http://stackoverflow.com/questions/22887829/peer-not-authenticated-while-importing-gradle-project-in-eclipse I suppose. You'll want to edit wpilibc/build.gradle.

Once that's fixed, you may encounter errors about LLVM include files not existing during build. That's probably due to Gradle not being able to download the ntcore Maven artifact. That can be fixed by both building the appropriate commit of ntcore and publishing locally with the -PmakeDesktop flag. I'm not sure which commit it requires, so I'd have to look into it. Getting old versions of WPILib to build nowadays is a bit of a pain...

By the way, this package is technically optional. I just updated frc-2016 to reflect this. You could add the following lines to CMakeLists.txt to use the WPILib provided by the Eclipse plugins:

include_directories($ENV{HOME}/wpilib/cpp/current/include)
link_directories($ENV{HOME}/wpilib/cpp/current/lib)

ctag commented on 2016-12-18 13:35

This package appears to fail to build while downloading something over https. Looks like my java environment doesn't have the server's cert?

https://0bin.net/paste/IUDYTCFzdTZDB+os#fC1S1umbXyef09wm3ExhTttq1uaYDW84nI37R9bVWe+