Compiling allwpilib #5751
Replies: 4 comments 28 replies
-
|
I'm not sure about the gradle error, but for packaging you might want to consider using the cmake build instead of the gradle build. We build/bundle a lot of third party dependencies into the gradle build (e.g. opencv), while the cmake build uses system dependencies. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah. Due to this, I'm trying to get it working by compiling from source and if possible packaging it for other teams. It is not practical for me to switch away from nixos right now so this is currently my best option. |
Beta Was this translation helpful? Give feedback.
-
|
@sciencewhiz My laptop is my main machine for all my work and thus needs to remain consistent. The reason no supported distro would work is because: 2: I just spent the last 2 weeks configuring it (Yes I know this is the sunk cost fallacy but configuration takes a long time) |
Beta Was this translation helpful? Give feedback.
-
|
Out of curiosity, did you try running the WPILib installer in an FHS sandbox, e.g. via |
Beta Was this translation helpful? Give feedback.
-
|
No I have not. Might try that to see how it goes. |
Beta Was this translation helpful? Give feedback.
-
|
No I have not. Might try that to see how it goes. |
Beta Was this translation helpful? Give feedback.
-
|
Did you clone the repository? Or did you just download the source? |
Beta Was this translation helpful? Give feedback.
-
|
cloning the repo did weirder stuff so I am not going to worry about it and just focus on stable versions |
Beta Was this translation helpful? Give feedback.
-
|
I'm pretty sure that error is from the wpilib versioning plug-in that can't find any git info. Cloning the repository doesn't keep you from running a stable version. |
Beta Was this translation helpful? Give feedback.
-
|
That worked. compilation fails with |
Beta Was this translation helpful? Give feedback.
-
|
google finds lots of people having problems because NixOS adds compiler flags and doesn't allow them to be overridden, going back years, and I'm not finding solutions. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, I will have to see if any of the guys in the nixos Discord have a fix. In the meantime, would you happen to know what flags it is adding that are not in the standard build. |
Beta Was this translation helpful? Give feedback.
-
|
I managed to get allwpilib to compile successfully on the latest master branch. Hopefully the last hurdle. I have managed to solve the issues relating to the compiler and dependencies. However, I appear to be having an issue where one of the tests is failing. The test is apparently |
Beta Was this translation helpful? Give feedback.
-
|
im building version 4.3. |
Beta Was this translation helpful? Give feedback.
-
2023.4.3 is not "the latest master branch". You'll need to patch wpiutil_test sources to not run that test. |
Beta Was this translation helpful? Give feedback.
-
|
Why does it matter whether 2023.4.3 is not the latest branch? Wouldn't the testing change based on the branch? |
Beta Was this translation helpful? Give feedback.
-
|
The test in 2023.4.3 that fails with modern GCC versions was disabled on main. You'll need to do the same if you want to use 2023.4.3 (or you can build with CMake and not run wpiutil tests at all). It's fine to disable because the comparison tests aren't even valid invariants to enforce. JSON doesn't mandate a key ordering. |
Beta Was this translation helpful? Give feedback.
-
|
Ok I will try with an older gcc version and if that does not work I will just disable tests. If all goes well I will hopefully be able to package 2023.4.3 with cmake tonight. |
Beta Was this translation helpful? Give feedback.
-
|
any idea what could be happening with this in the cmake build. Tried turning on and off different parts of the build with no success. This is not the only issue I'm having on the cmake build but its the only one so far that I have no clue what to do about. |
Beta Was this translation helpful? Give feedback.
-
|
I got that a few minutes ago and fixed it by deleting my build folder and rerunning cmake configure. |
Beta Was this translation helpful? Give feedback.
-
|
That worked. What do you use for the opencv jar. I found javacv mentioned in a chief delphi post but it is not explicitly mentioned in the cmake docs. |
Beta Was this translation helpful? Give feedback.
-
|
OpenCV comes with its own Java bindings. Most systems have an option to install an opencv-java or similar package (e.g. Ubuntu has a libopencv-java package). |
Beta Was this translation helpful? Give feedback.
-
I am trying to compile allwpilib-2023.4.3 from source. The end goal of this is to package it as a Nix package for Nixos users. However, when compiling using the build instructions and the source from the release I ended up with this error:
* What went wrong: A problem occurred evaluating root project 'allwpilib-2023.4.3'. > Failed to calculate the value of extension 'wpilibVersioning' property 'version'. > org.eclipse.jgit.api.errors.RefNotFoundException: Ref HEAD cannot be resolvedI looked around and was unable to find another occurrence of this that's surfaced on the web.
I am not super familiar with gradle and don't want to touch any of the code
I also had separate issues compiling the current master branch. However, I am not worrying about this for the time being.
EDIT: I solved the about problem using @sciencewhiz solution. However, it is failing to compile with the error:
error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Werror=cpp] 413 | # warning _FORTIFY_SOURCE requires compiling with optimization (-O) | ^~~~~~~ cc1plus: all warnings being treated as errorsdo I just need to change the optimization level somehow?Is this the right place to ask when I have compilation issues?
What other tips would you give for compiling future versions of wpilib.
Thanks in advance
EDIT: The same error mentioned appears to be happening on both 2023.4.2 and 2023.4.3.
Beta Was this translation helpful? Give feedback.
All reactions