[mythtv-users] building mythtv for Fedora 41 with cmake

[James Abernathy]

On Sun, Feb 9, 2025 at 3:58 PM James Linder <jam at tigger.ws> wrote:

>
>
> > On Feb 9, 2025, at 22:13, Peter Bennett <pb.mythtv at gmail.com> wrote:
> >
> >
> > On 2/9/25 09:02, James Abernathy wrote:
> >> Sorry about the partial email that went out too soon.
> >>
> >> I think the correct way to use the new cmake build stuff has finally
> sunk into my brain.
> >>
> >> On a fresh nuc box with Fedora Plasma 41 installed I followed the cmake
> readme and this time I built master with these commands:
> >>
> >> cmake --preset qt5 -DCMAKE_INSTALL_PREFIX=~/mythtv-output-jfa
> >> cmake --build build-qt5
> >>
> >> This way I didn't need 'sudo' to accomplish this and everything is in
> my $HOME directory.
> >>
> >> At first I did what the Mythtv Build from Source wiki calls out for
> libraries but I also try setting the LD_LIBRARY_PATH.
> >>
> >> I created a file /etc/ld.so.conf.d called mythtv.conf with the contents:
> >> /home/jim/mythtv-output-jfa/lib/
> >> /home/jim/mythtv-output-jfa/lib64/
> >>
> >> and ran sudo ldconfig
> >>
> >> I added to the end of my ~/.bashrc file the following:
> >> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/jim/mythtv-output-jfa/
> >> export PATH=$PATH:/home/jim/mythtv-output-jfa/bin/
> >>
> >> mythfrontend --platform xcb runs against my production backend just
> fine.
> >>
> >> Is this sort of what I'm supposed to do?
> >>
> >> Do I need the /etc/ld.so.conf.d stuff or is LD_LIBRARY_PATH all I need?
> >>
> >> Jim A
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >>
> > If you copy it into /usr/local then all the paths are automatically
> sorted out. Otherwise to run from a different directory you need a number
> of variables. This is from test.sh in deb-light in the packaging repository:
> > basedir=$destdir/usr
> > export PATH=$basedir/bin:$basedir/local/bin:$PATH
> > export MYTHTVDIR=$basedir
> > export
> LD_LIBRARY_PATH=$basedir/lib:$basedir/share/mythtv/lib:$LD_LIBRARY_PATH
> > export PYTHONPATH=`ls -d $basedir/local/lib/python*/dist-packages`
> > export PERL5LIB=`ls -d
> $basedir/local/share/perl/*`${PERL5LIB:+:${PERL5LIB}}
> > test.sh can be used to run packages from the install location used with
> deb-light. See the deb-light readme.
> > Peter
>
> Jim the way we build and try various systems I can’t imagine why you’d
> give a curley wossname about sudo but changing permissions of /usr/local/
> for the duration of the build seems much easier.
> For moi I’d just use sudo and “in the unlikely event of depressuration …”
> just rebuild (and cmake again just to watch :-)
> James
>

I'm famous for screwing up my PC so badly I have to rebuild.  This may be
partly caused by CUI (coding under the influence)

So that's why I mostly use BTRFS so snapshots save my butt.

I do like to try to understand the correct way to do stuff.  From my
playing over the last week it looks like building without sudo and
specifying a directory I own for the build output and then moving it to
/usr/local or /usr/ when it builds successfully is the best way to go for
me.

Jim A
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20250209/096c4dd6/attachment.htm>