Re: Keep "\""-signs for graphviz (issue 292110043 by thomasmorle...@gmail.com)

2016-03-26 Thread pkx166h

I cannot test this patch using the method suggested by Thomas from the
CG:

http://www.lilypond.org/doc/v2.19/Documentation/contributor/tracing-object-relationships

as it appears to no longer work (or we need more 'steps' or information
for those that don't know enough about how graphviz and LP are supposed
to work together).

So the least I can do is to test this the 'usual' way.

Passes make, make check and a full make doc.

https://codereview.appspot.com/292110043/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


building from source

2016-03-26 Thread Daniel Birns
So, as an experienced C/C++ developer, I’m interested in working on midi, and 
have been welcomed by some on the development team. First thing: build from the 
sources. I’ve always found this step, with every software project, to be one of 
the most difficult, so I’m not terribly surprised.

I spent hours trying to get autogen.sh to approve my prereq, and am left with 
this:

ERROR: Please install required programs:  TeX Gyre fonts OTF (make sure the 
fc-list utility can see them, e.g. 'sudo apt-get install fonts-texgyre', or use 
--with-texgyre-dir) metapost CTAN package (texlive-metapost) fontforge 
libpango1.0-dev or pango?-devel >= 1.6.0 (installed: ) texi2html dblatex 
epsf.tex lh CTAN package (texlive-lang-cyrillic or texlive-texmf-fonts) pngtopnm


I’m on Mac/OS X. My impression is that most (all?) lilypond developers are on 
linux. I will need help getting past this point. Truth is, I don’t need a full 
source build, though it might be nice for testing. All I need is the lilypond 
binary. Perhaps I wouldn’t need all this to build just that much.

I have VMWare with a windows VM, and could probably add a linux VM, though I’d 
prefer not. I’m already on limited disk space, and getting the build to get 
this far has eaten quite a bit of memory. The fonts in particular are difficult.

Otherwise, I will probably have to give up, which is okay.

-d
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: Doc: CG - replace all references of Google Code (issue 294820044 by pkx1...@gmail.com)

2016-03-26 Thread pkx166h

Thanks Trevor


https://codereview.appspot.com/294820044/diff/1/Documentation/contributor/issues.itexi
File Documentation/contributor/issues.itexi (left):

https://codereview.appspot.com/294820044/diff/1/Documentation/contributor/issues.itexi#oldcode121
Documentation/contributor/issues.itexi:121: Configure your email client:
On 2016/03/19 16:50:08, Trevor Daniels wrote:

I think we need to keep this item and the following @enumerate.

Otherwise the

following sub-items don't make sense.


Yes I see. I took some more time to look over this subsection and have
re-organized it slightly so that it 'flows' more logically, I also
noticed that we ask the bu-squadee to send his request for Allura to
lilypond-dev but actually that would mean they would need to also
subscribe to that mail list to be allowed to send emails. As this is not
a requirement for bug Squad work, I changed this to 'send your SF user
name to bug-lilypond instead - although that would mean you (or Phil)
would need to be on that list. I have assumed you both are, but if you
want to put this back (and require that they subscribe to dev as well)
let me know.

https://codereview.appspot.com/294820044/diff/1/Documentation/contributor/issues.itexi
File Documentation/contributor/issues.itexi (right):

https://codereview.appspot.com/294820044/diff/1/Documentation/contributor/issues.itexi#newcode105
Documentation/contributor/issues.itexi:105: permissions to create and
edit tracker issues.
On 2016/03/19 16:50:08, Trevor Daniels wrote:

It's not the email address we need but the SourgeForge Username.


Done - with a minor addition.

https://codereview.appspot.com/294820044/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: building from source

2016-03-26 Thread Dan Eble
On Mar 26, 2016, at 11:34 , Daniel Birns  wrote:
> I’m on Mac/OS X. My impression is that most (all?) lilypond developers are on 
> linux. I will need help getting past this point.
…
> I have VMWare with a windows VM, and could probably add a linux VM, though 
> I’d prefer not. I’m already on limited disk space, and getting the build to 
> get this far has eaten quite a bit of memory. The fonts in particular are 
> difficult.
> 
> Otherwise, I will probably have to give up, which is okay.

I’m using LilyDev in a VM hosted on OS X and it’s the bee’s knees.  Facing your 
limitations, I would probably give up, though it has been years since I tried 
building on OS X.  At that time, it required three days of building and 
installing dependencies with fink, macports, or whatever it was.
—
Dan


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: building from source

2016-03-26 Thread Daniel Birns
What is LilyDev?

-d
> On Mar 26, 2016, at 8:49 AM, Dan Eble  wrote:
> 
> On Mar 26, 2016, at 11:34 , Daniel Birns  wrote:
>> I’m on Mac/OS X. My impression is that most (all?) lilypond developers are 
>> on linux. I will need help getting past this point.
> …
>> I have VMWare with a windows VM, and could probably add a linux VM, though 
>> I’d prefer not. I’m already on limited disk space, and getting the build to 
>> get this far has eaten quite a bit of memory. The fonts in particular are 
>> difficult.
>> 
>> Otherwise, I will probably have to give up, which is okay.
> 
> I’m using LilyDev in a VM hosted on OS X and it’s the bee’s knees.  Facing 
> your limitations, I would probably give up, though it has been years since I 
> tried building on OS X.  At that time, it required three days of building and 
> installing dependencies with fink, macports, or whatever it was.
> —
> Dan
> 


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: building from source

2016-03-26 Thread Daniel Birns
Never mind: https://github.com/fedelibre/LilyDev/releases/tag/v4.0 

> On Mar 26, 2016, at 8:49 AM, Daniel Birns  wrote:
> 
> What is LilyDev?
> 
> -d
>> On Mar 26, 2016, at 8:49 AM, Dan Eble  wrote:
>> 
>> On Mar 26, 2016, at 11:34 , Daniel Birns  wrote:
>>> I’m on Mac/OS X. My impression is that most (all?) lilypond developers are 
>>> on linux. I will need help getting past this point.
>> …
>>> I have VMWare with a windows VM, and could probably add a linux VM, though 
>>> I’d prefer not. I’m already on limited disk space, and getting the build to 
>>> get this far has eaten quite a bit of memory. The fonts in particular are 
>>> difficult.
>>> 
>>> Otherwise, I will probably have to give up, which is okay.
>> 
>> I’m using LilyDev in a VM hosted on OS X and it’s the bee’s knees.  Facing 
>> your limitations, I would probably give up, though it has been years since I 
>> tried building on OS X.  At that time, it required three days of building 
>> and installing dependencies with fink, macports, or whatever it was.
>> —
>> Dan
>> 
> 

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: building from source

2016-03-26 Thread Carl Sorensen
On 3/26/16 9:49 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
behalf of Daniel Birns"  wrote:

>What is LilyDev?

http://www.lilypond.org/doc/v2.19/Documentation/contributor/lilydev


A Debian iso ready-to-go for doing LilyPond development.

I used to maintain a usable lilypond development site on OS X.  New
updates to OS X invariably broke the site and required hours or days of
fixing things.  LilyDev in a VirtualBox VM always works, and works easily.

I would really recommend using LilyDev in a VM.

Carl


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: building from source

2016-03-26 Thread Daniel Birns
Yes, that’s working fine — building now. Now I need to find all the stuff I 
installed on my mac to retrieve some disk space.

As I was getting frustrated yesterday, I was thinking “maybe they need a 
virtual machine…”

:-)

-d
> On Mar 26, 2016, at 8:54 AM, Carl Sorensen  wrote:
> 
> On 3/26/16 9:49 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
> behalf of Daniel Birns"  on behalf of daniel.bi...@icloud.com> wrote:
> 
>> What is LilyDev?
> 
> http://www.lilypond.org/doc/v2.19/Documentation/contributor/lilydev
> 
> 
> A Debian iso ready-to-go for doing LilyPond development.
> 
> I used to maintain a usable lilypond development site on OS X.  New
> updates to OS X invariably broke the site and required hours or days of
> fixing things.  LilyDev in a VirtualBox VM always works, and works easily.
> 
> I would really recommend using LilyDev in a VM.
> 
> Carl
> 


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: building from source

2016-03-26 Thread Daniel Birns
1) I have a good build, have made a trivial modification, and it seems to work. 
(I found a class (Midi-duration) that’s unused. I commented it out, and 
everything builds fine. Since there’s no references to it, I presume the 
testsuites will be unaffected, though you never know...
2) I’m reading ‘contributor.pdf’. It says I will be assigned a mentor. That’s 
fine with me either way, but I’m curious if perhaps there’s some formal route I 
should go through at this point.
3) My plan is to work via the C++ files and improve the midi output. I see 
several .cc files with midi in their name and I think 4 header files with midi 
in the name. 

So, at this point, I could use some advice about 1) where to focus in the 
contributor.pdf, and 2) some idea of the architecture, particularly with regard 
to midi processing. Of course, I could try to figure that out myself, but that 
doesn’t seem like the right approach.

The first thing I need to do is understand what’s going on today before I muck 
with anything.

-d

> On Mar 26, 2016, at 8:54 AM, Carl Sorensen  wrote:
> 
> On 3/26/16 9:49 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
> behalf of Daniel Birns"  on behalf of daniel.bi...@icloud.com> wrote:
> 
>> What is LilyDev?
> 
> http://www.lilypond.org/doc/v2.19/Documentation/contributor/lilydev
> 
> 
> A Debian iso ready-to-go for doing LilyPond development.
> 
> I used to maintain a usable lilypond development site on OS X.  New
> updates to OS X invariably broke the site and required hours or days of
> fixing things.  LilyDev in a VirtualBox VM always works, and works easily.
> 
> I would really recommend using LilyDev in a VM.
> 
> Carl
> 


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: building from source

2016-03-26 Thread Dan Eble
Please consider getting your feet wet with 
https://sourceforge.net/p/testlilyissues/issues/4789/ .  (Developers who are 
actually familiar with MIDI generation may wish to shoot down this idea.)
— 
Dan

> On Mar 26, 2016, at 15:49 , Daniel Birns  wrote:
> 
> 1) I have a good build, have made a trivial modification, and it seems to 
> work. (I found a class (Midi-duration) that’s unused. I commented it out, and 
> everything builds fine. Since there’s no references to it, I presume the 
> testsuites will be unaffected, though you never know...
> 2) I’m reading ‘contributor.pdf’. It says I will be assigned a mentor. That’s 
> fine with me either way, but I’m curious if perhaps there’s some formal route 
> I should go through at this point.
> 3) My plan is to work via the C++ files and improve the midi output. I see 
> several .cc files with midi in their name and I think 4 header files with 
> midi in the name. 
> 
> So, at this point, I could use some advice about 1) where to focus in the 
> contributor.pdf, and 2) some idea of the architecture, particularly with 
> regard to midi processing. Of course, I could try to figure that out myself, 
> but that doesn’t seem like the right approach.
> 
> The first thing I need to do is understand what’s going on today before I 
> muck with anything.
> 
> -d
> 
>> On Mar 26, 2016, at 8:54 AM, Carl Sorensen  wrote:
>> 
>> On 3/26/16 9:49 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
>> behalf of Daniel Birns" > on behalf of daniel.bi...@icloud.com> wrote:
>> 
>>> What is LilyDev?
>> 
>> http://www.lilypond.org/doc/v2.19/Documentation/contributor/lilydev
>> 
>> 
>> A Debian iso ready-to-go for doing LilyPond development.
>> 
>> I used to maintain a usable lilypond development site on OS X.  New
>> updates to OS X invariably broke the site and required hours or days of
>> fixing things.  LilyDev in a VirtualBox VM always works, and works easily.
>> 
>> I would really recommend using LilyDev in a VM.
>> 
>> Carl
>> 
> 


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: building from source

2016-03-26 Thread Urs Liska
Hi Daniel,

we don't have a formal mentorship program. This was intended but AFAICS
this never really worked out. So it seems the CG should be cleaned up in
this respect. The "mentoring" you'll receive is from this mailing list.

If you have reached the state where you can build LilyPond and create
some improvement you're ready to start, I think.

What you *can* do is ask on this list whether your perception of a
possible patch is viable (actually that's what you just did). And if
noone objects you should upload a patch for review - and that's what you
should concentrate on next in the CG.

You will need a SourceForge account and should communicate your user
name, so someone can add you to the issue tracker project. This is
needed for successfully going through the upload process with git-cl.

If your patch is good and reaches (maybe after some iterations) the
"push" status you will have to ask someone (again, here on this list) to
push the patch on your behalf. After a number of successful patches you
can ask for getting push access on the LilyPond repository itself.

HTH
Urs

Am 26.03.2016 um 20:49 schrieb Daniel Birns:
> 1) I have a good build, have made a trivial modification, and it seems to 
> work. (I found a class (Midi-duration) that’s unused. I commented it out, and 
> everything builds fine. Since there’s no references to it, I presume the 
> testsuites will be unaffected, though you never know...
> 2) I’m reading ‘contributor.pdf’. It says I will be assigned a mentor. That’s 
> fine with me either way, but I’m curious if perhaps there’s some formal route 
> I should go through at this point.
> 3) My plan is to work via the C++ files and improve the midi output. I see 
> several .cc files with midi in their name and I think 4 header files with 
> midi in the name. 
> 
> So, at this point, I could use some advice about 1) where to focus in the 
> contributor.pdf, and 2) some idea of the architecture, particularly with 
> regard to midi processing. Of course, I could try to figure that out myself, 
> but that doesn’t seem like the right approach.
> 
> The first thing I need to do is understand what’s going on today before I 
> muck with anything.
> 
> -d
> 
>> On Mar 26, 2016, at 8:54 AM, Carl Sorensen  wrote:
>>
>> On 3/26/16 9:49 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
>> behalf of Daniel Birns" > on behalf of daniel.bi...@icloud.com> wrote:
>>
>>> What is LilyDev?
>>
>> http://www.lilypond.org/doc/v2.19/Documentation/contributor/lilydev
>>
>>
>> A Debian iso ready-to-go for doing LilyPond development.
>>
>> I used to maintain a usable lilypond development site on OS X.  New
>> updates to OS X invariably broke the site and required hours or days of
>> fixing things.  LilyDev in a VirtualBox VM always works, and works easily.
>>
>> I would really recommend using LilyDev in a VM.
>>
>> Carl
>>
> 
> 
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
> 


-- 
Urs Liska
www.openlilylib.org

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: grob.cc segfaults (with GCC6?)

2016-03-26 Thread Valentin Villenave
On 3/25/16, Valentin Villenave  wrote:
> I’m having a weird segfault on several regtests

Greetings,
I’ve added it as https://sourceforge.net/p/testlilyissues/issues/4814/
(I can use GUB releases for now and Fedora 24 is not even tagged as
alpha, so there’s no emergency. Still -- I’m out of my depth here :-)

Cheers,
Valentin.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: Doc: CG - replace all references of Google Code (issue 294820044 by pkx1...@gmail.com)

2016-03-26 Thread tdanielsmusic

New stuff looks OK, but I'm concerned about the deleted section.


https://codereview.appspot.com/294820044/diff/1/Documentation/contributor/issues.itexi
File Documentation/contributor/issues.itexi (right):

https://codereview.appspot.com/294820044/diff/1/Documentation/contributor/issues.itexi#newcode1021
Documentation/contributor/issues.itexi:1021: @end itemize
This is a large section to simply delete.  I realise much of it is not
currently relevant, but rather than just deleting it perhaps it would be
better to replace it with details of the current procedure, so that when
the day comes (hopefully not soon!) to appoint a new bug-meister he will
have a source of reference for our procedures.

https://codereview.appspot.com/294820044/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel