[mythtv-users] CMake remembers too much

[David Hampton]

On Tue, 2025-02-11 at 12:43 -0500, James Abernathy wrote:
> So after a build on mythtv using cmake on a RPI4, I decided to go
> back to testing a build with mythtv-light using cmake.  So I deleted
> my ~/build directory that contained the mythtv clone and also my
> output director that was created by the -
> DCMAKE_INSTALL_PREFIX=/home/jim/build/jfa-build-out
> 
> However, when I did a new clone of mythtv and packaging then tried to
> build mythtv-light I got errors that somewhere on my system it
> remembered to look for stiff in my CMAKE_INSTALL_PREFIX directory as
> show below in the example console output:
> 
> CMake Error in programs/mythfrontend/CMakeLists.txt:
>   Imported target "PkgConfig::LIBAVFORMAT" includes non-existent path
> 
>     "/home/jim/build/jfa-build-out/include/mythtv"
> 
>   in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:
> 
>   * The path was deleted, renamed, or moved to another location.
> 
>   * An install or uninstall procedure did not complete successfully.
> 
>   * The installation package was faulty and references files it does
> not
>   provide.
> 
> Not sure how to clear that short of reformatting the drive and
> rebuilding.

Are you installing into the same CMAKE_INSTALL_PREFIX directory as
before?  Try deleting that first.  The cmake builds will look at the
install directory to see if exiv2 and ffmpeg have already been built,
and will reuse those earlier builds if possible.  You could also try
building mythtv by adding -DLIBS_USE_INSTALLED=OFF to the "cmake --
preset" command.  That should ignore any previously built libraries and
rebuild everything.

Its also possible since you've copied your install to /usr before, so
the builds might be picking up bad information from there.  Try this
command:

  find /usr -name libmyth*.pc

If that returns any file names, delete those files.  Also check to see
if the files ffnvcodec.pc and mythexiv2.pc exist in the same directory
as the others, and delete those too.  This shouldn't be necessary if
you set the LIBS_USE_INSTALLED flag.

David