Am 19.12.18 um 21:56 schrieb Michael Gerdau:
First step would be running Frescobaldi from its Git repository
(and at that occasion test if the description is accurate and also works
for Windows 10):
https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-from-Git-on-Windows
Commenting as
> First step would be running Frescobaldi from its Git repository
> (and at that occasion test if the description is accurate and also works
> for Windows 10):
> https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-from-Git-on-Windows
Commenting as I go:
These are the discrepancies so fa
OK, great.
First step would be running Frescobaldi from its Git repository
(and at that occasion test if the description is accurate and also works
for Windows 10):
https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-from-Git-on-Windows
Am 19.12.18 um 18:54 schrieb Saul Tobin:
I'd b
I'd be happy to help test as well.
On Wed, Dec 19, 2018, 9:32 AM Michael Gerdau
> > Indeed, it's not a real problem to compose a special command line for
> WSL Windows - if we know exactly how it should look like.
> > Testing would be a little bit awkward, though
>
> I‘d be happy to test it.
>
>
> Indeed, it's not a real problem to compose a special command line for WSL
> Windows - if we know exactly how it should look like.
> Testing would be a little bit awkward, though
I‘d be happy to test it.
Kind regards,
Michael
___
lilypond-user mailin
Am 19.12.18 um 17:12 schrieb Michael Gerdau:
The Windows program "wsl.exe" is the interop program that ties things
together. You can call it and pass it a command to be executed within
the WSL environment.
So, while I can simply say "lilypond" in a WSL shell, under a Windows
shell I need to sa
> The Windows program "wsl.exe" is the interop program that ties things
> together. You can call it and pass it a command to be executed within
> the WSL environment.
>
> So, while I can simply say "lilypond" in a WSL shell, under a Windows
> shell I need to say "wsl lilypond" to have the same
Aaron Hill writes:
> On 2018-12-18 9:26 pm, Saul Tobin wrote:
>> 1) Is there a technical obstacle or other reason preventing a Windows
>> 64-bit build?
>
> I would presume that GUB can target 64-bit MinGW,
I should be surprised, given just when GUB was under active development.
It probably is no
On 2018-12-19 3:43 am, Urs Liska wrote:
Am 19. Dezember 2018 11:53:26 MEZ schrieb Aaron Hill
:
But if Frescobaldi needs to have a path to the LilyPond installation,
then it can never be made to work with WSL. There is no* path to the
WSL file system that a Windows program can access. Instead,
> How does one launch Linux programs then? Is that some specific "WSL Shell"
> that you start and then have a bash or something? And this does mean theWSL
> can only be used to do stuff on the Linux command line, no way to use Linux
> commands triggered from Windows applications?
Yes.
As the n
Am 19. Dezember 2018 11:53:26 MEZ schrieb Aaron Hill :
>On 2018-12-19 2:17 am, Michael Gerdau wrote:
>>> Not really.
>>> What I *can* say is this:
>>>
>>> * LilyPond installations are registered in Frescobaldi by pointing
>
>>> to
>>> their executable.
>>> * Frescobaldi calculates a path
On 2018-12-19 2:17 am, Michael Gerdau wrote:
Not really.
What I *can* say is this:
* LilyPond installations are registered in Frescobaldi by pointing
to
their executable.
* Frescobaldi calculates a path relative to that executable and adds
that to the library path in the LilyPond p
> Not really.
> What I *can* say is this:
>
> * LilyPond installations are registered in Frescobaldi by pointing to
> their executable.
> * Frescobaldi calculates a path relative to that executable and adds
> that to the library path in the LilyPond process's environment
>
> I have no
Am 19.12.18 um 08:09 schrieb Aaron Hill:
On 2018-12-18 10:51 pm, Urs Liska wrote:
This UI is populated by running LilyPond with the
-dshow-available-fonts option, so it actually displays what LilyPond
can really use.
Ah, that greatly reduces confusion.
However, my point still stands that one
On 2018-12-18 10:51 pm, Urs Liska wrote:
This UI is populated by running LilyPond with the
-dshow-available-fonts option, so it actually displays what LilyPond
can really use.
Ah, that greatly reduces confusion.
However, my point still stands that one needs to be aware that the fonts
availabl
Am 19.12.18 um 07:49 schrieb Aaron Hill:
On 2018-12-18 10:39 pm, Urs Liska wrote:
I have no idea about the WSL, but in general I can't imagine there
should be any source of confusion here. Frescobaldi wouldn't need to
access anything font-like when it comes to LilyPond…
But doesn't Frescobald
On 2018-12-18 10:39 pm, Urs Liska wrote:
I have no idea about the WSL, but in general I can't imagine there
should be any source of confusion here. Frescobaldi wouldn't need to
access anything font-like when it comes to LilyPond…
But doesn't Frescobaldi have a UI for enumerating/previewing avai
Am 19.12.18 um 07:17 schrieb Aaron Hill:
2) Is it possible to run Lilypond under WSL from Frescobaldi?
Possibly; however I do not use Frescobaldi, so I cannot speak from
experience. Theoretically, you should only need to configure
Frescobaldi to launch LilyPond as "wsl /path/to/lilypond" so
On 2018-12-18 9:26 pm, Saul Tobin wrote:
1) Is there a technical obstacle or other reason preventing a Windows
64-bit build?
I would presume that GUB can target 64-bit MinGW, but I gather that this
has not been a priority to deliver. Perhaps one of the developers could
speak to this more com
Thanks so much for the confirmation. A couple questions:
1) Is there a technical obstacle or other reason preventing a Windows
64-bit build?
2) Is it possible to run Lilypond under WSL from Frescobaldi?
On Tue, Dec 18, 2018 at 8:36 PM Aaron Hill wrote:
> On 2018-12-18 7:24 pm, Saul Tobin wrote:
On 2018-12-18 7:24 pm, Saul Tobin wrote:
It looks like the Fatal realloc error happens after the score finishes
compiling while it's being written to a temporary file. At that point,
the
Lilypond process is using ~1.8 G of RAM. Is it possible I'm running
into a
32 bit size limitation in Guile
It looks like the Fatal realloc error happens after the score finishes
compiling while it's being written to a temporary file. At that point, the
Lilypond process is using ~1.8 G of RAM. Is it possible I'm running into a
32 bit size limitation in Guile or something like that?
On Sun, Dec 16, 2018
Hi Ben,
I did see that thread, but I don't think it can be directly related to my
issue, since in my case there is no single line of my code that is
triggering the compile error. Each score compiles correctly on its own and
in combination with any of the others, but when I compile all together it
On 12/16/2018 5:32 PM, Saul Tobin wrote:
Hi all,
I'm getting a fatal error when I compile all of the movements of a
large project on 2.19.82 on Windows 10. I can compile the movements
individually and in smaller combinations with no problems. There is no
Lilypond error in the debug output, ju
Hi all,
I'm getting a fatal error when I compile all of the movements of a large
project on 2.19.82 on Windows 10. I can compile the movements individually
and in smaller combinations with no problems. There is no Lilypond error in
the debug output, just "FATAL: memory error in realloc."
I had no
25 matches
Mail list logo
