lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Accept GUILE 2 without extra configure options (issue 569390043 by a


From: dak
Subject: Re: Accept GUILE 2 without extra configure options (issue 569390043 by address@hidden)
Date: Fri, 21 Feb 2020 08:25:02 -0800

On 2020/02/21 16:02:14, hahnjo wrote:
> guile-config since 2.0 has the following comment:
> "This script has been deprecated. Just use pkg-config."

It is not something it outputs but rather a script-internal comment.

> Mabye it makes sense to completely turn to pkg-config? My system has $
ll
> /usr/lib/pkgconfig/guile-*
> -rw-r--r-- 1 root root 453 11. Jan 2019 
/usr/lib/pkgconfig/guile-1.8.pc
> -rw-r--r-- 1 root root 849 10. Jan 2019 
/usr/lib/pkgconfig/guile-2.0.pc
> -rw-r--r-- 1 root root 886 10. Jul 2019 
/usr/lib/pkgconfig/guile-2.2.pc
> 
> So this would also work for Guile 1.8 (which should either be
preferred as David
> suggested or completely dropped; not sure if we're already there).

How does it work?  With GUILE_CONFIG, I pass the executable as an
environment variable.  Admittedly, my non-system-wide Guile-1.8 (Ubuntu
no longer has guile-1.8-dev) contains a file
/usr/local/tmp/guile-1.8/lib/pkgconfig/guile-1.8.pc but I don't have an
idea how to use it.

https://codereview.appspot.com/569390043/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]