[ardour-dev] latest CVS commit

Jan Depner eviltwin69 at cableone.net
Sat Feb 12 13:04:50 PST 2005


Paul,

    Can't compile.  Here are a handful of the first errors:

In file included from /data2/sound2/ardour/libs/gtkmm/src/gtk--.h:90,
                 from gtkmmext/doi.h:24,
                 from mwc.cc:22:
/data2/sound2/ardour/libs/gtkmm/src/gtk--/curve.h:6: error: syntax error
before
   `<<' token
In file included from
/data2/sound2/ardour/libs/gtkmm/src/gtk--/curve.h:34,
                 from /data2/sound2/ardour/libs/gtkmm/src/gtk--.h:90,
                 from gtkmmext/doi.h:24,
                 from mwc.cc:22:
/data2/sound2/ardour/libs/gtkmm/src/gtk--/drawingarea.h:33: error:
syntax error
   before `}' token
/data2/sound2/ardour/libs/gtkmm/src/gtk--/drawingarea.h:34: error:
syntax error
   before `*' token
In file included from /data2/sound2/ardour/libs/gtkmm/src/gtk--.h:106,
                 from gtkmmext/doi.h:24,
                 from mwc.cc:22:
/data2/sound2/ardour/libs/gtkmm/src/gtk--/ctree.h:82: error: syntax
error
   before `;' token
/data2/sound2/ardour/libs/gtkmm/src/gtk--/ctree.h:85: error: syntax
error
   before `{' token
/data2/sound2/ardour/libs/gtkmm/src/gtk--/ctree.h:94: error: ISO C++
forbids
   declaration of `BranchElem' with no type
/data2/sound2/ardour/libs/gtkmm/src/gtk--/ctree.h:421: error: syntax
error
   before `&' token
/data2/sound2/ardour/libs/gtkmm/src/gtk--/ctree.h:423: error: syntax
error
   before `&' token
/data2/sound2/ardour/libs/gtkmm/src/gtk--/ctree.h:424: error: syntax
error
   before `&' token
/data2/sound2/ardour/libs/gtkmm/src/gtk--/ctree.h: In member function
`void
   Gtk::RowList::push_front(...)':


    I'm using FC1 and PLanet CCRMA.  I always run autogen and
configure.  I'm seeing tons of patch stuff in the files.  Am I missing
something here?  Gotta go to practice, I'll check back later.

Jan


On Sat, 2005-02-12 at 12:26, Paul Davis wrote:
> I would appreciate it if CVS testers could give this a workout.  Just
> do "your usual" stuff with xfades, layers, overdubs, trimming, region
> motion etc. and make sure it works as expected. I have tested locally,
> and it appears OK, but I know that I am not an adequate regression
> test on my own.
> 
>    * significant reorganization of inter-object signalling
>        during region motion/trimming to scale correctly
>        (prompted by a brush-mode-edited session with
>         46 duplicate overlapping regions and 490
> 	crossfades).
> 
>    * add key actions for each snap-to setting
>    * add default keybindings for snap-to-beats (F9) and 
>       snap-to-bars (F10)
> 
>    * libardour: 0.869.0
>      ardour/gtk: 0.574.0
> _______________________________________________
> ardour-dev mailing list
> ardour-dev at lists.ardour.org
> http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org




More information about the Ardour-Dev mailing list