These are chat archives for highfidelity/hifi

12th
Sep 2017
Christoph Haag
@ChristophHaag
Sep 12 2017 00:30
that mac problem sounds like something wrong with libopenvr_api library in the openvr repository with the updated openvr 1.0.10
the warnings sound like all of them should have been there before the pull request already...
Ryan Huffman
@huffman
Sep 12 2017 18:11
@ElderOrb re: tools + cmake, I asked internally and it's a known issue that will be addressed. Sorry if it caused you trouble!
Thijs Wenker
@thoys
Sep 12 2017 18:48
heya @ChristophHaag took a quick peek at your Jenkins warnings/errors , the windows error seems to be related to the #endif that is on the same line as a return. The windows compiler doesn't seem to allow that. The warnings came in existence because gcc got involved as soon as you exposed openvr to all the platforms. Gcc is a bit more strict on type conversion warnings, you probably have to do some type conversions
hope that helps
Christoph Haag
@ChristophHaag
Sep 12 2017 18:49
oh right, the entire openvr plugin wasn't compiled on gcc before
Thijs Wenker
@thoys
Sep 12 2017 18:50
correct
thanks for doing this btw @ChristophHaag , looking forward to turn this machine into a dual boot :)
Christoph Haag
@ChristophHaag
Sep 12 2017 18:51
wow I didn't even know you could have something after #endif on the same line. that was definitely an accident
Thijs Wenker
@thoys
Sep 12 2017 18:51
hehe thats what I guessed
Christoph Haag
@ChristophHaag
Sep 12 2017 18:53
thanks, I will fix all that. only I have no idea what to do about the mac problem with undefined symbols. I am guessing it's because I updated to the newest openvr and something is wrong with it
old openvr versions have some bugs left like ValveSoftware/SteamVR-for-Linux#35
i think that was only in the C api though
Christoph Haag
@ChristophHaag
Sep 12 2017 22:49
do we honestly need to set QT_CMAKE_PREFIX_PATH=/usr/lib/cmake now?
since highfidelity/hifi@9c03fa0
MiladNazeri
@MiladNazeri
Sep 12 2017 23:22
From what I can tell, it isn't necessary, but you can still use that environment variable to overrule the new method of setting it's path
Christoph Haag
@ChristophHaag
Sep 12 2017 23:27
CMake Error at cmake/macros/SetupQt.cmake:69 (message):
  Unable to locate Qt cmake config in /home/chris/Qt/5.9.1/gcc_64/lib/cmake
Call Stack (most recent call first):
  CMakeLists.txt:64 (setup_qt)
if i don't set it
https://highfidelity.com now responds with 406 Not Acceptable unless you explicitly send the header Accept: text/html. Weird.
MiladNazeri
@MiladNazeri
Sep 12 2017 23:50
Just want to double check, but is your cmake dir for sure in /home/chris/Qt/5.9.1/gcc_64/lib/cmake ?
Christoph Haag
@ChristophHaag
Sep 12 2017 23:53
no, i don't have qt there
no need since archlinux has qt 5.9.1 in the repositories, with its cmake directories in cmake's system standard /usr/lib/cmake directory, the SetupQt macro just doesn't check the default path