• Help building kodi 19

    Help and Support
    6
    1 Votes
    6 Posts
    1k Views
    1

    So yesterday I had a weird error. I thought why don't I put the nvme mount with option exec into /etc/fstab. I did that and after that it would only boot into emergency and I couldn't recover anything. I tried adding the shell to cmdline.txt but nothing helped. So I decided to completly redo my retropie setup. After redoing everything, I tried again to build kodi with all the options and it just worked fine.
    No errors nothing, it just went up to 100%. I installed it with sudo make install and it works.
    :D As stupid as this seems it probably was some bad configuration which still existed from my first tries.
    I want to thank you for your help, after I remounted my drive I thought what a godsent it would have took me atleast weeks to come up with this if ever. :D
    So this thread can be closed now.

  • RetroPie setup reverting cmake to 3.13

    Help and Support
    2
    0 Votes
    2 Posts
    301 Views
    mituM

    @akamming said in RetroPie setup reverting cmake to 3.13:

    i noticed however that when i run the Update command from the RetroPie setup script, cmake is reverted to 3.13 again. Apparently it does not detect that a higher version is already installed, cause i also noticed that cmake and cmake-data are installed again as raspbian packages.

    It does not detect it, because it's not installed from a .deb package. RetroPie installs the cmake package that's available in the distro - whatever version is available in the Raspbian repositories.

    As a general rule when installing from source - in order to not get your installation overwritten by a distro package, don't install into the system directories (/usr/bin, /usr/sbin, etc.) - use /usr/local or /opt.

  • cmake and macOS

    Ideas and Development
    2
    0 Votes
    2 Posts
    598 Views
    darksiluxD

    Hey! A bit late haha

    So... I don't know much of cmake, but I ALWAYS like to start by the official website and documentation.

    I found an official tutorial on the official website:
    https://cmake.org/cmake-tutorial/

    Not the BEST answer but I hope it helps...

    Cya!

  • 0 Votes
    11 Posts
    3k Views
    P

    To find out if the RPi GPIOs are working correctly, you can use the script as described at https://github.com/petrockblog/ControlBlockService2#checking-the-raw-gpio-of-the-raspberry. It could either be a wiring issue or an issue with the ControlBlock. I suggest to run through the script and see if the GPIOs are all working correctly.

  • sudo cmake ../ not working

    Help and Support
    2
    0 Votes
    2 Posts
    2k Views
    herb_fargusH

    @JHNTR looks like you're missing all the dependencies it says you're missing.

    Also format your logs properly as described on the read this first page