Can we keep on importing libraries into the build process from custom directories in the same way as before? I used to write the following lines in build.properties file in the project source:
lib.dir=${src.dir}/../lib
userLibs=\
${lib.dir}/library_1.jar:\
${lib.dir}/library_2.jar:\
Does this still work considering that the build process now includes files in the wpilib directory?
So I have to add the libraries to \wpilib\user\java\lib? Is this the only way to get the libraries recognized by the build? The thing is that I’d like to include the libraries in the project folder for easier distribution.
I noticed that the build.properties file in wpilib defines the user libraries with
userLibs.dir=${user.home}/wpilib/user/java/lib
I tried overwriting that setting with the following two lines at the end of the build.properties file in my project:
lib.dir=${src.dir}/../lib
userLibs.dir=${lib.dir}/yamlbeans-1.11.jar:${lib.dir}/commons-collections4-4.1.jar
However, I get the following error message upon deploying:
BUILD FAILED
C:\Users\Lucas\wpilib\java\current\ant\build.xml:124: D:\Lucas\Desktop\FRC\2017\eclipse_workspace\Pie-API\lib\lib\commons-collections4-4.1.jar does not exist.
That’s cause I have my libraries in Pie-API/lib/ not Pie-API/lib/lib/. If I remove the /lib from the lib.dir definition, the build process tries to find the libraries in Pie-API/.
I know that I can just place my libraries in a Pie-API/lib/lib/ folder, but I’m sure that I’m doing something awfully wrong. Is there any way of correctly setting a different userLibs.dir directory?
Ok, I got it. I just had to set the userLibs.dir option in my build.properties like:
userLibs.dir=lib
That actually should’ve been really obvious from the beginning :rolleyes: