dannyedel / dspdfviewer

Dual-Screen PDF Viewer for latex-beamer
http://dspdfviewer.danny-edel.de
GNU General Public License v2.0
220 stars 29 forks source link

Ubuntu trusty, cannot compile #192

Open ouboub opened 7 years ago

ouboub commented 7 years ago

Hi

I have installed cmake-data cmake
libboost1.54-dev
libboost-program-options1.54-dev libboost-program-options-dev
libpoppler-qt5-1
autoconf-archive libboost-test1.55.0
libboost1.55-dev
libboost-test1.55-dev
libxkbcommon-x11-0

but when I follow the installation instruction running cmake ../ gives CMake Error at cmake/external_libraries.cmake:42 (find_package): By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Core", but CMake did not find one.

Could not find a package configuration file provided by "Qt5Core" (requested version 5.1.1) with any of the following names:

Qt5CoreConfig.cmake
qt5core-config.cmake

Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set "Qt5Core_DIR" to a directory containing one of the above files. If "Qt5Core" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:47 (include)

-- Configuring incomplete, errors occurred! See also "/home/oub/ALLES/src/dspdfviewer/build/CMakeFiles/CMakeOutput.log".

I have libqt5core5a 5.2.1 installed.

What is the problem?

thanks

Uwe Brauer

dannyedel commented 7 years ago

Hello Uwe,

it seems you have only installed the Qt libraries (required to run already-compiled programs), but not the headers/development files needed to compile some yourself.

A search in the ubuntu package directories suggests you should try installing qtbase5-dev.

You may need more than this one package to compile yourself. Please take a look at the dependency list inside travis.yml, which is used during the continuous integration build.

As a third option, you can use the pre-built binary from the ppa. If there is an audience for it; I'll upload the newest version to the trusty one.

I hope this helps, and sorry for the delay.

Danny

ouboub commented 7 years ago

Hi Danny,

thanks for your answer!

  1. I installed qtbase5-dev. The cmake gives the following error: CMake Error at cmake/external_libraries.cmake:47 (find_package): By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5LinguistTools", but CMake did not find one.

    Could not find a package configuration file provided by "Qt5LinguistTools" with any of the following names:

    Qt5LinguistToolsConfig.cmake I searched for qt5linuisttool, but seems that qttools5-dev-tools was the package needed, but no, compilations resulted in the same error. So I am stuck again. I think it would be good to add the required packages to the INSTALL file, if possible

Uwe

dannyedel commented 7 years ago

Hello Uwe,

I'm not sure how to best solve this, so I'll just give my comments, maybe we'll come to an idea together.

I think it would be good to add the required packages to the INSTALL file, if possible

While I admit that the INSTALL file is a bit outdated (it lists the now-default-and-working-fine Qt5 support as experimental) I don't think listing required package names is possible, since they will be different for each distribution. Essentially all that can be said distribution-agnostic is something along the lines of "You need Boost, CMake, Qt5 and poppler-qt5, each including the development headers".

The INSTALL file mentions that the website contains specific install instructions per distribution, and I checked that the Ubuntu trusty information there still works for getting the binary. You are correct in that it does not install the build-from-source-dependencies, even though the debian/control file contains the needed information.


Having said that, if you have a concrete idea how to improve the INSTALL file, please send a pullrequest with your suggested change.

I found and installed the binaries and run into a problem which I will report in a different issue, because it has to do with the functionality.

Thank you for keeping the discussions separate, it is much appreciated. I will post there aswell.

Danny