[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Denemo-devel] 0.7.10
Re: [Denemo-devel] 0.7.10
Mon, 04 Aug 2008 15:27:35 -0500
I seem to be missing the function list-tree. It fails to compile at line
1021 on lyparserfuncs.c. Here is the compile error:
/libgdk_pixbuf-2.0.so /usr/lib/libpangocairo-1.0.so /usr/lib/libpango-1.0.so
/usr/lib/libcairo.so /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so -ldl
/usr/lib/libglib-2.0.so /usr/lib/libaubio.so /usr/lib/libportaudio.so -lm
external.o: In function `get_temp_filename':
/home/jjbenham/src/denemo.git/denemo/src/external.c:119: warning: the
use of `tempnam' is dangerous, better use `mkstemp'
lyparserfuncs.o: In function `create_score':
reference to `list_tree'
collect2: ld returned 1 exit status
make: *** [denemo] Error 1
make: Leaving directory `/home/jjbenham/src/denemo.git/denemo/src'
make: *** [all-recursive] Error 1
make: Leaving directory `/home/jjbenham/src/denemo.git/denemo'
make: *** [all] Error 2
While we are at it .... are we using tempnam instead of mkstemp for
windows compatibility? If not maybe we should change that for this
On Mon, 2008-08-04 at 19:43 +0100, Richard Shann wrote:
> I've just pushed the first tranche of work for the 0.7.10 release. It
> could be quite buggy, as I have been learning git and have not had an
> easy time of the merge process. I think I need the newer version of git
> with git-mergetool in it. Looking at the gitweb using the browser, I
> realize how little I understand git as yet - this push has changed
> almost every source file but that is not obvious from the front page...
> About this work, there *may* be regressions.
> Specifically, Roy: apologies if I have damaged any of your work, I have
> checked it over, but there may have been things you were watching for
> that I have missed. Jean-Rene`: apologies for once more making the
> keymap setting poorly placed in the code; I will work on getting the
> initialization done before the first music score is created (so avoiding
> the ugly initialization inside newview(). But I know Jeremiah is waiting
> to get a sight of this work, and it does mean that we have now just one
> set of GtkActions to deal with, which is an improvement in the code.
> Most of the work is invisible, but you will see that we now have tabs
> for new pieces of music, rather than separate windows (the tabs should
> vanish when there is only one of them - to be fixed), and the LilyPond
> parser is now handling multiple score blocks and the \bar directives at
> the end of pieces as well as picking up some of the LilyPond directives
> (much more to come on this).
> Denemo-devel mailing list