Hi 2.0.4 does indeed fix the build on Mac but I got the same warnings. I thought it was a /opt/local prefix issue or that it was due to the fact of not using X11. The machine indeed had no denemo / lilypond history.
yves > Le 7 mars 2016 à 05:04, Richard Shann <[email protected]> a écrit : > > On Mon, 2016-03-07 at 10:20 +0100, Johan Vromans wrote: >> On Sun, 06 Mar 2016 20:01:26 +0000 >> Richard Shann <[email protected]> wrote: >> >>> I've given a sanity-check on >>> http://denemo.org/~jjbenham/denemo-release/denemo-2.0.4.tar.gz >>> >>> and this appears to me to be good for release. >> >> Custom built rpm + install => all seems to be okay. >> >> During startup, denemo gives a couple of warnings/errors: >> >> Denemo - WARNING : Failed to add font dir /usr/share/denemo/fonts. >> Denemo - CRITICAL: Could not find feta.ttf >> Denemo - CRITICAL: Could not find Denemo.ttf >> Denemo - CRITICAL: Could not find emmentaler.ttf >> >> The rpm build process puts the fonts in /usr/share/fonts/denemo >> (RedHat/Fedora conventions, %{_fontdir} macro). >> >> Despite the "CRITICAL", it seems to work. >> >> I'm not sure how to fix this. > > Well, it may be that if you were installing on a machine with no > previous history of LilyPond or Denemo it could fail; that is the fonts > may be present already. More likely they are installed, and are picked > up, but the warnings from Denemo are based on naive assumptions. > > Thanks for the check! > > Richard > > > > _______________________________________________ > Denemo-devel mailing list > [email protected] <mailto:[email protected]> > https://lists.gnu.org/mailman/listinfo/denemo-devel > <https://lists.gnu.org/mailman/listinfo/denemo-devel>
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
