elgato-gchd icon indicating copy to clipboard operation
elgato-gchd copied to clipboard

problem compiler ubuntu 16.04

Open retrocant opened this issue 8 years ago • 8 comments

Scanning dependencies of target gchd [ 4%] Building CXX object src/CMakeFiles/gchd.dir/main.cpp.o In file included from /home/alfredo/Descargas/elgato-gchd-master/src/gchd.hpp:19:0, from /home/alfredo/Descargas/elgato-gchd-master/src/main.cpp:20: /home/alfredo/Descargas/elgato-gchd-master/src/gchd/settings.hpp:69:24: error: ‘std::runtime_error::runtime_error’ nombra al constructor In file included from /home/alfredo/Descargas/elgato-gchd-master/src/main.cpp:20:0: /home/alfredo/Descargas/elgato-gchd-master/src/gchd.hpp:31:24: error: ‘std::runtime_error::runtime_error’ nombra al constructor /home/alfredo/Descargas/elgato-gchd-master/src/main.cpp: En la función ‘int main(int, char**)’: /home/alfredo/Descargas/elgato-gchd-master/src/main.cpp:383:77: error: no se encontró una función coincidente para la llamada a ‘setting_error::setting_error(const char [45])’ /home/alfredo/Descargas/elgato-gchd-master/src/main.cpp:383:77: nota: el candidato es: In file included from /home/alfredo/Descargas/elgato-gchd-master/src/gchd.hpp:19:0, from /home/alfredo/Descargas/elgato-gchd-master/src/main.cpp:20: /home/alfredo/Descargas/elgato-gchd-master/src/gchd/settings.hpp:67:7: nota: setting_error::setting_error(const setting_error&) /home/alfredo/Descargas/elgato-gchd-master/src/gchd/settings.hpp:67:7: nota: no hay una conversión conocida para el argumento 1 de ‘const char [45]’ a ‘const setting_error&’ src/CMakeFiles/gchd.dir/build.make:62: fallo en las instrucciones para el objetivo 'src/CMakeFiles/gchd.dir/main.cpp.o' make[2]: *** [src/CMakeFiles/gchd.dir/main.cpp.o] Error 1 CMakeFiles/Makefile2:85: fallo en las instrucciones para el objetivo 'src/CMakeFiles/gchd.dir/all' make[1]: *** [src/CMakeFiles/gchd.dir/all] Error 2 Makefile:127: fallo en las instrucciones para el objetivo 'all' make: *** [all] Error 2

retrocant avatar Nov 15 '16 18:11 retrocant

I have problems in the compilation in cmake I fulfill all the requirements

retrocant avatar Nov 15 '16 18:11 retrocant

What is your GCC version? You can find out with: gcc -v

According to what I just read here, the support for the C++11 feature used here was only added for gcc version 4.8 (support for inheriting constructors). If you wait till after the weekend (I will be away) I can probably strip usage of this feature away, or you can try updating your compiler. I'd prefer to not use such a bleeding edge feature if it is going to cause problems, so I'd like to try to clean it up and fix it for you.

seveirein avatar Nov 17 '16 21:11 seveirein

Greetings, thanks for answering me, I think the gcc version I have is version 4.7.

I will update the compiler to version 4.8 Thank you

El 17 nov 2016, a las 22:43, Scott Dossey [email protected] escribió:

What is your GCC version? You can find out with: gcc -v

According to what I just read here https://gcc.gnu.org/projects/cxx-status.html#cxx11, the support for the C++11 feature used here was only added for gcc version 4.8 (support for inheriting constructors). If you wait till after the weekend (I will be away) I can probably strip usage of this feature away, or you can try updating your compiler. I'd prefer to not use such a bleeding edge feature if it is going to cause problems, so I'd like to try to clean it up and fix it for you.

retrocant avatar Nov 17 '16 22:11 retrocant

@retrocant alternatively, you can also use clang, whenever gcc fails for you. But I agree on the point, that we need to have some "cutoff", where we consider features as "bleeding edge" and not use them.

Maybe we could use out-of-the-box Ubuntu 16.04.x LTS as a standard, where we expect our driver to compile. We could remove "bleeding edge" C++11 features, until it compiles on that platform.

tolga9009 avatar Nov 19 '16 12:11 tolga9009

Greetings, I just compiled perfectly updating the gcc to the last version and it worked perfectly in the compilation, now I have a problem and it is that I do not get to work and it can be by the controllers and of course in the privileges. I can not open the gchd.ts file in /tmp/gchd.ts probably due to permissions. And if I get to open the fcihero in videolan it comes out in black and I do not see the video capture on screen. The version that I have of the cat is the HD and supposedly is compatible, the driver files are located in their respective carpets that you comment. any ideas?

El 19 nov 2016, a las 13:46, Tolga Cakir [email protected] escribió:

alternatively, you can also use clang, whenever gcc fails for you. But I agree on the point, that we need to have some "cutoff", where we consider features as "bleeding edge" and not use them.

Maybe we could use out-of-the-box Ubuntu 16.04.x LTS as a standard, where we expect our driver to compile. We could remove "bleeding edge" C++11 features, until it compiles on that platform.

retrocant avatar Nov 19 '16 13:11 retrocant

For testing purposes, I would recommend using sudo gchd, in order to create the /tmp/gchd.ts file. Set permissions to 777 using sudo chmod 777 /tmp/gchd.ts and try to open the file in VLC. Watch your terminal for any output.

Due to some instability in the latest code, I would recommend replugging your Elgato, before you start a new attempt with sudo gchd. The device reset is not working 100% reliably for GCHD1 device as of now. Alternatively, if you have a GCHD1 (PID 0x0044, 0x004e and 0x0051, you can look it up by using lsusb), you can use release 0.2.0 which is working reliably, minus all the auto-detection and GCHD2 support.

tolga9009 avatar Nov 19 '16 14:11 tolga9009

Greetings I send you captures as I have everything structured, still not working.[image: Imágenes integradas 1] [image: Imágenes integradas 2] [image: Imágenes integradas 3] [image: Imágenes integradas 4]

2016-11-19 15:10 GMT+01:00 Tolga Cakir [email protected]:

For testing purposes, I would recommend using sudo gchd, in order to create the /tmp/gchd.ts file. Set permissions to 777 using sudo chmod 777 /tmp/gchd.ts and try to open the file in VLC. Watch your terminal for any output.

Due to some instability in the latest code, I would recommend replugging your Elgato, before you start a new attempt with sudo gchd. The device reset is not working 100% reliably for GCHD1 device as of now. Alternatively, if you have a GCHD1 (PID 0x0044, 0x004e and 0x0051, you can look it up by using lsusb), you can use release 0.2.0 which is working reliably, minus all the auto-detection and GCHD2 support.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tolga9009/elgato-gchd/issues/29#issuecomment-261716002, or mute the thread https://github.com/notifications/unsubscribe-auth/AWZXKR7SYztBs0sfb5oQAP3kfgDm-_4oks5q_wNigaJpZM4Ky3hB .

retrocant avatar Nov 19 '16 14:11 retrocant

Just want to ask what device you are capturing from. Thinking you may have hdcp copy protect issues possibly. Will look at captures properly when back home.

seveirein avatar Nov 21 '16 19:11 seveirein