> On Oct 19, 2023, at 12:47, Ian West wrote:
>
> From the attached photo you will see that I created in 'home' a folder
> called 'LilyPondArea', and in that a folder called 'lilypond-2.24.2'. In the
> former I placed the downloaded tar, and in the latter the unpacked files of
>
> From the attached photo you will see that I created in 'home' a
> folder called 'LilyPondArea', and in that a folder called
> 'lilypond-2.24.2'. In the former I placed the downloaded tar, and in
> the latter the unpacked files of lilypond-2.24.2 (i.e. 'bin', etc)
Looks good.
> I use Textedit
Le samedi 07 octobre 2023 à 17:46 +0100, Ian West a écrit :
> Was there a version (or a build) of 2.20.0 that ran on 64 bit machines? Some
> say there was not; I think there was and that I used it.
Well, at some point there was an *unofficial* build of 2.20 around as a
workaround for the lack of
> On Oct 7, 2023, at 18:46, Ian West wrote:
>
> I can see that it is a complex business constructing a new software package.
>
> I was under the impression that, on 12 Aug 2022, I downloaded lilypong02.20.0
> build 20200311175017-darwin-64.tar, unpacked it and ran the package on my
> 64-bit
I can see that it is a complex business constructing a new software package.
I was under the impression that, on 12 Aug 2022, I downloaded lilypong02.20.0
build 20200311175017-darwin-64.tar, unpacked it and ran the package on my
64-bit M2 MacBookAir running Ventura 13.4.1
It ran successfully
> On Oct 7, 2023, at 07:43, Werner LEMBERG wrote:
>
>> libpaper is listed on
>> https://ports.macports.org/port/ghostscript/details/
>>
>> Well, that's too bad since there is no actual license
>> incompatibility due to the use as subprocess, as already noted by
>> several others. Not sure if
>> I think it's ghostscript – there are no pre-built packages
>> available either. While LilyPond doesn't link to it in normal
>> builds, gs is needed for converting LilyPond's EPS output files to
>> PDF. In other words, a MacPorts user still needs a compiler...
>
> Damn, you are right.
David Kastrup writes:
> msk...@ansuz.sooke.bc.ca writes:
>
>> On Fri, 6 Oct 2023, Werner LEMBERG wrote:
>>
>>> Thanks. I think it's ghostscript – there are no pre-built packages
>>> available either. While LilyPond doesn't link to it in normal builds,
>>> gs is needed for converting LilyPond's
> Le 6 oct. 2023 à 23:18, Werner LEMBERG a écrit :
> Thanks. I think it's ghostscript – there are no pre-built packages
> available either. While LilyPond doesn't link to it in normal builds,
> gs is needed for converting LilyPond's EPS output files to PDF. In
> other words, a MacPorts
msk...@ansuz.sooke.bc.ca writes:
> On Fri, 6 Oct 2023, Werner LEMBERG wrote:
>
>> Thanks. I think it's ghostscript – there are no pre-built packages
>> available either. While LilyPond doesn't link to it in normal builds,
>> gs is needed for converting LilyPond's EPS output files to PDF. In
>>
On Fri, 6 Oct 2023, Werner LEMBERG wrote:
> Thanks. I think it's ghostscript – there are no pre-built packages
> available either. While LilyPond doesn't link to it in normal builds,
> gs is needed for converting LilyPond's EPS output files to PDF. In
> other words, a MacPorts user still needs
>> Ah, now I remember, thanks! I wasn't fluent enough then with the
>> 'ports' program to find out which of the dependencies actually uses
>> libpaper, since LilyPond itself [doesn't use it](
>> https://github.com/macports/macports-ports/blob/master/textproc/lilypond/Portfile
>> )
>
> It's most
Le ven. 6 oct. 2023 à 22:35, Werner LEMBERG a écrit :
>
> > It's in the non-distributable list:
> >
> > not-distributable.txt:lilypond "lilypond" is not distributable
> > because its license "GPL-3+" conflicts with license "GPL-2" of
> > dependency "libpaper" not-distributable.txt:lilypond-devel
> Ah, now I remember, thanks! I wasn't fluent enough then with the
> 'ports' program to find out which of the dependencies actually uses
> libpaper, since LilyPond itself [doesn't use
> it](https://github.com/macports/macports-ports/blob/master/textproc/lilypond/Portfile)
I've even asked to
> It's in the non-distributable list:
>
> not-distributable.txt:lilypond "lilypond" is not distributable
> because its license "GPL-3+" conflicts with license "GPL-2" of
> dependency "libpaper" not-distributable.txt:lilypond-devel
> "lilypond-devel" is not distributable because its license
Hello,
Le ven. 6 oct. 2023 à 15:19, Werner LEMBERG a écrit :
>
> > All of LilyPond's dependencies definitely are GPLv3-compatible (or
> > we could not distribute official binaries on lilypond.org).
>
> I don't have access to my old Mac in the next days, but there is a
> possibility to actually
>> Again: license issues, as far as I know (but not from Apple in this
>> case).
>
> Are you sure? It seems to me that it just wants clang from XCode.
> I can't imagine what else could be useful for building LilyPond and
> provided by XCode.
Well, there are no pre-built 'lilypond' (or
> Le 6 oct. 2023 à 07:16, Werner LEMBERG a écrit :
> Again: license issues, as far as I know (but not from Apple in this
> case).
Are you sure? It seems to me that it just wants clang from XCode. I can't
imagine what else could be useful for building LilyPond and provided by XCode.
> There
> You are very kind. I shall give it a go. But I think you will have
> to agree that this is some 5 orders (***) of magnitude more complex
> than versions: 2.12.3, 2.18.2-1, and 2.20.0. I never would have got
> into Lilypond were I starting from here.
Please always bear in mind that *none* of
> Le 6 oct. 2023 à 01:23, Knute Snortum a écrit :
>
> I don't think you ever had the ability to just press a button and install
> LilyPond.
It used to be true on macOS and Windows. There was a (very minimal) GUI
application with basically a simple text editor and a menu button to compile
David,
> Perhaps that might be made clearer in the macOS section of
> https://lilypond.org/doc/v2.25/Documentation/web/download .
Could you provide better wording for this and the other issues you are
mentioning? I can then incorporate your changes into the
documentation.
Werner
On Thu 05 Oct 2023 at 23:12:44 (+0200), Jean Abou Samra wrote:
> > Le 5 oct. 2023 à 22:39, Ian West a écrit :
> > Dear David (copied to Jean, and Paul,)
> > You are very kind. I shall give it a go. But I think you will have to
> > agree that this is some 5 orders (***) of magnitude more
I'm going to jump in here and hopely not muddy the waters.
You say that you need to know the terminal and many other things to install
Lilypond 2.24, but I don't think this is true. I'm not on a Mac; I'm on
Ubuntu GNU/Linux but they are similar, I believe. First you go to the
download page:
> Le 5 oct. 2023 à 22:39, Ian West a écrit :
> Dear David (copied to Jean, and Paul,)
> You are very kind. I shall give it a go. But I think you will have to
> agree that this is some 5 orders (***) of magnitude more complex than
> versions: 2.12.3, 2.18.2-1, and 2.20.0. I never
Dear David (copied to Jean, and Paul,)
You are very kind. I shall give it a go. But I think you will have to
agree that this is some 5 orders (***) of magnitude more complex than versions:
2.12.3, 2.18.2-1, and 2.20.0. I never would have got into Lilypond were I
starting from here.
> Le 5 oct. 2023 à 21:26, David Wright a écrit :
>
> I'm sorry—perhaps I attached too much significance to the OP's
> "I do not want to use Frescobaldi." If a GUI is required,
> I would have thought a Mac editor could supply that, and
> drag-and-drop could run LP on the file that's dropped
On Thu 05 Oct 2023 at 19:43:27 (+0200), Jean Abou Samra wrote:
> > Le 5 oct. 2023 à 17:36, David Wright a écrit :
> >
> > Is this the way you should be going?
>
> No, it's not going to give him the GUI that he regrets.
I'm sorry—perhaps I attached too much significance to the OP's
"I do not
> Le 5 oct. 2023 à 17:36, David Wright a écrit :
>
> Is this the way you should be going?
No, it's not going to give him the GUI that he regrets.
Le 5 oct. 2023 à 15:49, Ian West a écrit :Dear Lilypond team, continuing from 1 Sept 17:43hrs. (similar problems to Mark Stephen Mrotek though he is Windows.) I successfully used version 2.20.0 on my MacBook Air M2 2022, macOS 13.4.1 from August 2022 till July 2023. Now I cannot, and I have
On Thu 05 Oct 2023 at 14:49:41 (+0100), Ian West wrote:
> Dear Lilypond team, continuing from 1 Sept 17:43hrs. (similar problems to
> Mark Stephen Mrotek though he is Windows.)
>
> I successfully used version 2.20.0 on my MacBook Air M2 2022, macOS
> 13.4.1 from August 2022 till July
30 matches
Mail list logo
