Re: Cannot build latest master branch

On 2023-07-27 05:22, Jean Abou Samra - jean(a)abou-samra.fr wrote: By the way, where are all those compiler flags coming from? Did you write them by hand? Did you copy them from somewhere? These flags are mostly for a better debugging experience and strengthened security. A lot of them are co

Re: Cannot build latest master branch

On 2023-07-26 14:13, Jean Abou Samra - jean(a)abou-samra.fr wrote: Yes, I deleted the build directory before redoing autogen.sh, redid `mkdir build && cd build` in between autogen.sh and configure Then you failure is pretty strange. Can you show the output of "build/out/bin/lilypond -V" pl

Re: Cannot build latest master branch

On 2023-07-26 11:51, Jean Abou Samra - jean(a)abou-samra.fr wrote: I'm not sure we understand "clean build" in the same way. I get that you rerun autogen and configure, but are you starting from a completely empty build directory? Yes, I deleted the build directory before redoing autogen.sh,

Re: Cannot build latest master branch

On 2023-07-26 11:17, Jean Abou Samra - jean(a)abou-samra.fr wrote: I also got the compilation error, but after adding , my locally built LilyPond works fine. Is this from a clean build? Yes. After redoing: * ./autogen.sh --noconfigure * ../configure --prefix=/home/lj/projects/internships/

Re: Getting beam subdivision working

On 2023-06-16 17:26, Carl Sorensen - carl.d.sorensen(a)gmail.com wrote: Before you work too hard on beam-subdivide-tuplets.ly , you may wish to investigate Urs's comment on local beat structure for tuplets.  As far as I know now, you don't have a beat struct

Re: Getting beam subdivision working

On 2023-06-16 16:26, Jean Abou Samra - jean(a)abou-samra.fr wrote: Le vendredi 16 juin 2023 à 16:13 -0700, Jason Yip a écrit : My implementation is available in a private fork, I'm not sure how I should share it if any other developers want to examine it (manual invite to each one who wants it?)

Re: Fix Lilypond Beaming GSOC Project

Hey Carl, I should have the time to get started with the on-boarding process now. To reiterate, I have a working develop environment for Lilypond now; I can edit whatever source files then build them without much hassle. One thing that concerns me is that generating tests takes a long time (`m

Re: Fix Lilypond Beaming GSOC Project

I got it working on my Arch Linux after trial and error with ./configure. Here are the Arch Linux package names that translate to what Lilypond needs (I didnt include package names that I already had, so obviously there's Python, ghostscript, etc.): * dblatex (optional, configure script keeps

Re: Preferred Mentor-Mentee Communication, Plan for Auto-Beaming Project

Thanks for the feedback Carl! See my comments below On 2023-03-30 13:00, Carl Sorensen - c_sorensen(a)byu.edu wrote: Thanks, Jason. See my answers below. Carl *From: *Jason Yip *Date: *Wednesday, March 29, 2023 at 8:45 PM *To: *Carl Sorensen *Cc: *Devel *Subject: *Preferred Mentor-Mente

Preferred Mentor-Mentee Communication, Plan for Auto-Beaming Project

Hi Carl, I'm CC'ing the developers mailing list, just to let you know. I would like to first ask you about your preferred mode of communication, if my project proposal is selected. That is, what modes of communication would you prefer for: * Real-time communication for mentor-mentee matters

Re: Fwd: Interested in GNU Lilypond Google Summer of Code Beaming Fixing Project Idea

Hi everyone, In the past 2 days, I have spent my time investigating the many GitLab issues related to regular note/tuplet subdivision problems and reading the Contributor's documentation and related C++ files. I am somewhat close to completing a GSoC application draft, and would like to share