Re: Lilypond build dependency tlasm
In this case the problem seems the font used rather than in the naming. Immanuel On Wed, Sep 7, 2022 at 12:02 PM David Kastrup wrote: > > Lukas-Fabian Moser writes: > > > Hi Andrew, > > > > Am 07.09.22 um 10:19 schrieb Andrew Bernard: > >> I cant find out what tlasm is. It's a missing dependency for the > >> build. Google's indexing of billions of pages produces nothing, > >> unless I am dreaming. Could somebody help me understand what this > >> program is and where to find it? > >> > >> ../configure outputs: > >> > >> ERROR: Please install required programs: t1asm > > > > t1asm != tlasm (in uppercase: T1ASM != TLASM) > > There are things like imprudent naming choices that are mistakes waiting > to happen. > > I called an early utility of mine "Preview-LaTeX" and realized with the > first vanity searches that web search engines generally ignore case. > And that I was not exactly entering an empty search space. > > Well, I've dropped the capitalization since then, and clearly by now > that tool (that ended up quite elaborate partly due to a host of > contributors) dominates the search space. > > But "is this a good idea?" is something people should really consider > when coining terms that other people will have to use as a reference. > > -- > David Kastrup > -- -- A man must either resolve to point out nothing new or to become a slave to defend it. -- Sir Isaac Newton
Re: Should we be touching goops?
> On Fri, Jun 3, 2022 at 7:21 AM David Kastrup wrote: > Programming languages don't offer different types for distances, > positions, weights, forces, whatnot. It's safe to say that programming languages don't typically don't offer much in the way of types, they do however usually allow you to define your own types and encourage you to do that to ensure type safety and code clarity. > When I equate various amounts of > power, the numbers don't demand that I get every part of > > 1 kg m²/s² = 1 V A s > > signed off by the compiler. I can rearrange terms perfectly well from > > a + b - c = a - c + b = (-c) + b + a > > without worrying about order of execution to make sure that every > intermediate term has a well-defined physical meaning. Well this isn't even true of numbers in typical programming languages. 1. your rearrangement might be silently ignored by the programming language because it doesn't ensure an order of evaluation. 2. your rearrangement might change the value of the result or give undefined behaviour. > Frankly, that's academic. It reminds me of the excessive amount of > energy placed into keeping the mathematics(!) of location vectors and > difference vectors separate. Location vectors and Difference vectors are not kept separate as far as I can tell. Affine space keeps points separate from differences of points which are vectors. So does common parlance for places/distances and time points/durations. Paris is not a distance and a week is not a time point. Immanuel -- -- A man must either resolve to point out nothing new or to become a slave to defend it. -- Sir Isaac Newton
Re: Point an Click & emacs
I could add it to the lilypond emacs code that is already there, and do a small writeup in the docs. Shall I make a pull request? Immanuel On Sun, May 22, 2022 at 2:36 PM Luca Fascione wrote: > > Maybe we could see if we can rope Immanuel to contribute a short segment to > the user docs? > > L > > On Sun, 22 May 2022, 14:17 Jean Abou Samra, wrote: >> >> Le 21/05/2022 à 22:38, Luca Fascione a écrit : >> > Jean, I think this is a BWV1079... >> >> >> :-) >> >> If the goal is to make this method known to other users, >> the lilypond-user list would be a better place. >> >> Best, >> Jean >> -- -- A man must either resolve to point out nothing new or to become a slave to defend it. -- Sir Isaac Newton
Point an Click & emacs
Today I found out it's quite easy to get point and click working with emacs as pdf viewer when using the pdf-tools package. 1. Install pdf-tools: https://github.com/politza/pdf-tools It's available as a package in emacs. 2. put this in your .emacs config >>> (defconst lilypond-filename-rx (rx (seq string-start (group (1+ print)) ":" (group (1+ digit)) ":" (group (1+ digit)) ":" (group (1+ digit)) string-end))) (defun lilypond-pdf-links-browse-uri-function (uri) "Check if the link starts with texedit and just reroute to emacs. Otherwise call pdf-links-browse-uri-default." (cl-check-type uri string) (let* ((obj (url-generic-parse-url uri)) (match (string-match lilypond-filename-rx (url-filename obj (unless match (message "Could not match %s" (url-filename obj))) (let* ((filename (match-string 1 (url-filename obj))) (line (string-to-number (match-string 2 (url-filename obj (pos (string-to-number (match-string 3 (url-filename obj (buf (or (find-buffer-visiting filename) (find-file-noselect filename (pop-to-buffer buf) (goto-char (point-min)) (forward-line (1- line)) (forward-char pos (setq pdf-links-browse-uri-function 'lilypond-pdf-links-browse-uri-function) >>> 3. Open a lilypond generated pdf with \PointAndClickOn and click away. The code might need some refining but it does work here quite well. Immanuel -- -- A man must either resolve to point out nothing new or to become a slave to defend it. -- Sir Isaac Newton
Mentor program
A mentor system is mentioned here: https://lilypond.org/doc/v2.23/Documentation/contributor/mentors Unfortunately it does not address how one goes about finding such a mentor. Immanuel -- -- Researching the dual problem of finding the function that has a given point as fixpoint.
Re: how to build lilypond in debug mode?
I don't think that that is how it's supposed to work in autotools in general, but if it works: great! Immanuel On Fri, Jul 26, 2013 at 8:59 AM, Benkő Pál wrote: > > pass the debug flags to the configure call. > > CXXFLAGS=-ggdb3 ./configure > > you can also build a profiling build throught the same mechanism. > > > > The --with-debug or like switches that a configure call supports should > > refer to > > extra debugging checks in the code switched on. > > even better: configure with --disable-optimising, see > > http://lilypond.org/doc/v2.17/Documentation/contributor/debugging-c_002b_002b-code > > p > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: how to build lilypond in debug mode?
pass the debug flags to the configure call. CXXFLAGS=-ggdb3 ./configure you can also build a profiling build throught the same mechanism. The --with-debug or like switches that a configure call supports should refer to extra debugging checks in the code switched on. i On Fri, Jul 26, 2013 at 7:33 AM, Frédéric Bron wrote: > Hi, > I would like to run lilypond in gdb to understand what happens when using > ties. > How can I build lilypond for that? > When I run configure --help, it says it is built with debug info by > default: > "--enable-debugging compile with debugging info. Default: on" > But when I run gdb, I get some strange errors (see below). > Frédéric > > gdb) run toto2.ly > Starting program: > /home/fred/lilypond/build-2013-07-25_11-30/lily/out/lilypond toto2.ly > Traceback (most recent call last): > File "/usr/share/gdb/auto-load/usr/lib64/ > libgobject-2.0.so.0.3600.3-gdb.py", > line 9, in > from gobject import register > File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in > import gdb.backtrace > ImportError: No module named backtrace > Traceback (most recent call last): > File "/usr/share/gdb/auto-load/usr/lib64/ > libgobject-2.0.so.0.3600.3-gdb.py", > line 9, in > from gobject import register > File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in > import gdb.backtrace > ImportError: No module named backtrace > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > Missing separate debuginfo for /lib64/libgraphite2.so.3 > Try: yum --disablerepo='*' --enablerepo='*debug*' install > /usr/lib/debug/.build-id/a1/aa32c91bc181cb69ebc81bbfd03a1349ea4e33.debug > GNU LilyPond 2.17.23 > warning: not relocating, no 2.17.23/ or current/ found under > /home/fred/lilypond/build-2013-07-25_11-30/lily/share/lilypond/ > ERROR: In procedure primitive-load-path: > ERROR: Unable to find file "lily.scm" in load path > [Inferior 1 (process 9056) exited with code 01] > Missing separate debuginfos, use: debuginfo-install > compat-guile18-1.8.8-6.fc19.x86_64 expat-2.1.0-5.fc19.x86_64 > fontconfig-2.10.93-1.fc19.x86_64 freetype-2.4.11-6.fc19.x86_64 > glib2-2.36.3-2.fc19.x86_64 glibc-2.17-11.fc19.x86_64 > gmp-5.1.1-2.fc19.x86_64 harfbuzz-0.9.18-3.fc19.x86_64 > libffi-3.0.13-4.fc19.x86_64 libgcc-4.8.1-1.fc19.x86_64 > libstdc++-4.8.1-1.fc19.x86_64 libtool-ltdl-2.4.2-16.fc19.x86_64 > nss-softokn-freebl-3.15.1-1.fc19.x86_64 pango-1.34.1-1.fc19.x86_64 > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: upgrade to c++11
On Sun, Jul 14, 2013 at 9:58 PM, David Kastrup wrote: > immanuel litzroth writes: > > > On Sun, Jul 14, 2013 at 9:20 PM, David Kastrup wrote: > > > >> They are also humongous, which means a quite larger amount of work > >> for GUB. > >> > > What do you mean with humongous? Boost is large because it has a lot > > of stuff. > > What's your point? "has a lot of stuff" is not independently useful. > Well, I don't know GUB so I have idea as to the work involved or whether it would even make sense. I do know that writing stuff that boost has on offer is a very bad idea. I also have some experience with c++11 and that has been really good. That's all folks. i ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: upgrade to c++11
On Sun, Jul 14, 2013 at 9:20 PM, David Kastrup wrote: > Frédéric Bron writes: > > >> Change them so that they will fail using anything but C++11? That > >> sounds like it would not buy us anything but trouble at the current > >> point of time. > > > > OK, I forget that. > > I see that boost is not used. Is it deliberate? These are c++03 > > libraries and most of them have been the source of the new standard. > > "source of standard" means that they are liable to change particularly > in the course of becoming part of a standard. They are very stable, getting a library in boost is not for the faint of heart. > > They are pretty well supported by distributions and work on windows, > > mac, linux. > > They are also humongous, which means a quite larger amount of work for > GUB. > What do you mean with humongous? Boost is large because it has a lot of stuff. Most of it is very stable and well documented. Interdependencies are minimal. Not using boost in any new reasonable sized C++ development project is a mistake, I've seen it happen. As to using them in lilypond I can't say what the effort/payoff would be. Also we have some phd's working here. I wouldn't overestimate the quality of their code. i ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: upgrade to c++11
> > g++ defaults to the C++ standard of 2003. 2 years ago a new standard > has been published with a log of improvements. > We've been using selected features from C++11 for a while now, and we are very happy with the improvements. Features like strongly typed enums are worth the switch alone. Today the g++ commands in the build process of lilypond do not specify > any standard so that it defaults to c++03. > Could we switch to c++11? > Well if you want full c++11 you're gonna have to use gcc 4.8(.1) which is probably a bit too close to the edge for most people/distributions. You could look at this page and figure out which features you want to use and what minimum version of the compiler you want to support: http://gcc.gnu.org/projects/cxx0x.html I suspect that a test would be required. Can somebody tell me where I > should add the option -std=c++11 to test this? > For example, can I just replace the following line of aclocal.m4: > CFLAGS=" -pipe $CFLAGS" > by > CFLAGS=" -pipe -std=c++11 $CFLAGS" > CXXFLAGS would be the place to put that flag on an autotoolized build you could just run CXXFLAGS="..." ./configure ... Be prepared for lots of deprecated warnings because even std::auto_ptr should be replaced by std::unique_ptr. Immanuel On Sun, Jul 14, 2013 at 6:05 PM, Frédéric Bron wrote: > Hi, > > g++ defaults to the C++ standard of 2003. 2 years ago a new standard > has been published with a log of improvements. > Today the g++ commands in the build process of lilypond do not specify > any standard so that it defaults to c++03. > Could we switch to c++11? > I suspect that a test would be required. Can somebody tell me where I > should add the option -std=c++11 to test this? > For example, can I just replace the following line of aclocal.m4: > CFLAGS=" -pipe $CFLAGS" > by > CFLAGS=" -pipe -std=c++11 $CFLAGS" > > Regards, > > Frédéric > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
