These are chat archives for highfidelity/hifi

26th
Dec 2014
Joe Large [Omega Heron]
@OmegaHeron
Dec 26 2014 00:07
@morrisford, I don't think that's the intent (making it difficult to add docs) - it just doesn't currently, IMHO, make it easy to say "I have some content, here it is - please use it." - You have to, if I have it right, create a job request on worklist - then have it approved - then build the doc - then have it reviewed - then, maybe posted. If you want to edit it you have to pretty much repeat a good portion of that process. I think worklist is great for more substantial jobs and getting paid for them, but, I'm not really looking to bid on jobs/be paid for such - so I'm not feeling the love for (last time I tried) needing to supply a fair bit of personal financial info so I could be legally paid.
If that's changed or incorrect, please correct me.
morrisford
@morrisford
Dec 26 2014 00:13
@OmegaHeron Ouch. I would guess there should be some other mechanism to be able to contribute useful docs. I just went through the build process for Linux including trying to discover a workable Linux release and then working out the missing bits so I wanted to help out other people but it seems like I can't. Oh well. I guess the hifi how to for beginners that I was working on as I go through the discovery process my self won't be used either.
Joe Large [Omega Heron]
@OmegaHeron
Dec 26 2014 00:15
Yes - I have the step by step method for 14.10 posted in the alpha forums - plus an outdated method for 14.04. There's info for CentOS contributed by another as well. I also have scripts I wrote to automate it for the 14.04 method - still need to update those to 14.10 and post in my GIT repo.
and I could very well be wrong about the process to get docs in now - it's been a few weeks since I last looked and things do change fast here.
morrisford
@morrisford
Dec 26 2014 00:18
I am REALLY new to hifi but if it is intended to help people compile and run that are not in the Alpha program then docs like that should be very obvious and visible in the hifi website.
Joe Large [Omega Heron]
@OmegaHeron
Dec 26 2014 00:19
Agreed :) I'm just a watcher and try to help when I can.
morrisford
@morrisford
Dec 26 2014 00:19
What is a watcher?
Joe Large [Omega Heron]
@OmegaHeron
Dec 26 2014 00:20
someone who has nothing to do with this officially - I meant.
morrisford
@morrisford
Dec 26 2014 00:20
Aha. Me too.
Joe Large [Omega Heron]
@OmegaHeron
Dec 26 2014 00:22
I got into it back in June or July... managed to compile based on old info in docs system and have kept up with all the changes. The linux side of it, so far, has been all on your own and that makes sense for now. Windows and Mac have prebuilt binaries for all the parts once you get into the alpha program
morrisford
@morrisford
Dec 26 2014 00:26
I made my first attempt at compiling in October and actually got a Centos good compile. I ran interface but had no idea what I was looking at and couldn't get it to do anything so I gave up till the last couple of days. I tried again and had much better success. I think this could be an interesting new environment eventually and I would like to help out if I can
Joe Large [Omega Heron]
@OmegaHeron
Dec 26 2014 00:28
It's fascinating stuff and my thought is to simply learn, document and help others as possible. Eventually it will all be of use - but, this is still very early alpha level stuff - code is changing at insane rates and often it takes longer to write up a document than it's valid for. ;)
morrisford
@morrisford
Dec 26 2014 00:40
I can see how long it might take with the process that you described. Maybe that will get changed.
Joe Large [Omega Heron]
@OmegaHeron
Dec 26 2014 00:42
I'm sure it will
morrisford
@morrisford
Dec 26 2014 00:43
Well, Merry Merry and all that. Have a good night.
Joe Large [Omega Heron]
@OmegaHeron
Dec 26 2014 00:43
Merry Christmas
Juan Andrés
@juandiana
Dec 26 2014 02:25
I'm stuck with the following error:
CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: LINKED_TARGET_DEPENDENCY_INCLUDES
Not sure what's wrong. Looked at the recent commits, perhaps commit 114e3bb is related.
David Rowe
@ctrlaltdavid
Dec 26 2014 23:02
@juandiana Re missing Faceshift, LibOVR, PrioVR, Sixense, LeapMotion, RtMidi, QXmpp and SDL2 ... these are all optional libraries: you don't need to include them in your build unless you want to use the associated functionality (i.e., Faceshift, Oculus Rift, ...). ... Though one of these you might want is Qxmpp which is used for text chat.