rosegarden-devel

When I press Preview with Lilypond under the File menu, I get :
KDialog
ERROR: LilyPond processing failed.
LilyPond output follows:
The output is totally blank giving no indication what the problem is.
On the other hand, I can do Export -> Export lilypond file ....
and it will export the file. Then I can run lilypond in a terminal on the
exported file and that will give me pdf and ps files from my input ly file.
It is only the Preview with Lilypond which fails.
The other problem is sometimes the preview command works. I haven't found
any connection to find out what causes it to work or fail.
I was wondering if I could somehow put a debugger on this to find out what
is going on. Likewise I would like to know if this is a known bug?
Ilan
--
View this message in context: http://www.nabble.com/Lilypond-print-preview-doesn%27t-work-in-Ubuntu-9.04-tp24265947p24265947.html
Sent from the Rosegarden - Dev mailing list archive at Nabble.com.

On Tuesday 30 June 2009, Ilan wrote:
> I was wondering if I could somehow put a debugger on this to find out what
> is going on. Likewise I would like to know if this is a known bug?
Ah. Ubuntu 9.04. Right. This kind of thing is why I've been in such a panic
to get the Qt4 port finished and released, before we ran out of time.
It's over a year later, the job isn't finished, and we ran out of time a
little while ago without realizing it. The problems will be starting
directly.
I haven't updated anything to 9.04 to have a look with my own eyes, but I
think what's going wrong is you no longer inhabit a world where the old KDE
3.x kdialog and dcop command line utilities exist. You obviously still have
KDE3 libraries, but probably couldn't install these old applications through
any reasonable amount of trickery.
This is bad, but there is no reasonable solution. It could be solved, yes,
but should I spend my time buying us six months of life for the old obsolete
code, or spend it getting the new code that much closer to release? I see
that the latter course is the only reasonable one to pursue under the
circumstances.
--
D. Michael McIntyre

My vote is without any doubt: forget the old code and work on the new
version.
What is interesting is that sometimes it actually works. This must mean that
all the required libraries are in fact in place. Maybe the order in which
things are
loaded makes the difference. I could investigate the problem, but it sounds
like
I would side track you from the main purpose of the new code.
The main point is the editor works so I can see the score and work on it.
If I REALLY need a particular version to Lilypond, I can export it and then
use
a terminal to print it. So a work around exists. Not as nice as a direct
Preview
Lilypond, but a work around.
Ilan
--
View this message in context: http://www.nabble.com/Lilypond-print-preview-doesn%27t-work-in-Ubuntu-9.04-tp24265947p24284209.html
Sent from the Rosegarden - Dev mailing list archive at Nabble.com.

On Wednesday 01 July 2009, Ilan wrote:
> My vote is without any doubt: forget the old code and work on the new
> version.
I should mention that while my replacement for this script doesn't do quite as
nice of a job, it does accomplish the basics with a native GUI, and it works
in the field. This one has been solved for some time now. I wish I could
say the same about the project packager script, which is a much uglier
version of the same problem.
> What is interesting is that sometimes it actually works. This must mean
> that all the required libraries are in fact in place. Maybe the order in
> which things are
> loaded makes the difference. I could investigate the problem, but it sounds
> like
> I would side track you from the main purpose of the new code.
I tested on an 8.10 box with KDE 4.2 from some backport repository. It
actually worked in spite of a string of errors about DCOP. It's mangled, but
not totally broken like I feared. Not on 8.10 anyway. It may be the rest of
the way broken by 9.04 though.
--
D. Michael McIntyre

On Wed, Jul 1, 2009 at 4:03 PM, Ilan<ilan.tal@...> wrote:
> My experience is mostly with c++ in the Windows world, but I am
> moving more and more towards Java to break my dependence upon
> Microsoft.
Don't move to Java, move to QT4!

On Wednesday 01 July 2009, Ilan wrote:
> I don't know if there is any way I could contribute to the development
> effort but I would be happy to do what I could.
I have all the major subprojects covered at the moment except for rewriting
the project packager script in real code. I doubt you'd be stepping forward
and raising your hand to tackle that monster, so the best thing I could think
of at this point is testing.
We're going to need a lot of serious field testing of the new Rosegarden
before we can hope to release it. It's not yet feature complete, and we
haven't yet fixed all the known bugs so far, but it wouldn't hurt to get more
people piddling with it and trying to do something useful, instead of just
knocking out random spot test blurbs the way I've been doing.
Of course the first problem that comes to mind is it doesn't do MIDI recording
yet. We really need to make fixing that bug a top priority. I suppose I
have to step back from this invitation while I go try once more to find
what's causing this to break, because it's kind of pointless to invite
testing until that much, at least, is actually working.
--
D. Michael McIntyre

Michael,
It seems to me that testing would be a good way to get my hands dirty,
as they say. I am downloading the qt4 branch as I write.
You said that there isn't much point in my trying to test anything until
the MIDI record actually works. While this is true, at least I can get
the feeling of what is involved to build the new software. Also I can
have a peek at it so it won't be totally new.
Then when you tell me there is something to test, I'll have something
to beat on.
If I have troubles building the version, I may be back with questions.
Ilan
--
View this message in context: http://www.nabble.com/Lilypond-print-preview-doesn%27t-work-in-Ubuntu-9.04-tp24265947p24424266.html
Sent from the Rosegarden - Dev mailing list archive at Nabble.com.

I find this with Google:
The aclocal program creates the file `aclocal.m4' by combining stock
installed macros, user defined macros and the contents of `acinclude.m4' to
define all of the macros required by `configure.in' in a single file.
aclocal was created as a fix for some missing functionality in Autoconf, and
as such we consider it a wart. In due course aclocal itself will disappear,
and Autoconf will perform the same function unaided.
user input files optional input process output files
================ ============== ======= ============
acinclude.m4 - - - - -.
V
.-------,
configure.in ------------------------>|aclocal|
{user macro files} ->| |------> aclocal.m4
`-------'
Maybe Ubuntu decided that it is time for it to disappear? Is there a way to
make bootstrap.sh use Autoconf instead?
Ilan
--
View this message in context: http://www.nabble.com/Lilypond-print-preview-doesn%27t-work-in-Ubuntu-9.04-tp24265947p24424572.html
Sent from the Rosegarden - Dev mailing list archive at Nabble.com.

On Fri, Jul 10, 2009 at 10:41 AM, Ilan<ilan.tal@...> wrote:
>
> Sorry that I'm back sooner than expected. What is aclocal?
> I looked in the Synaptic package manager and I don't see it.
It's in the "automake" package in Ubuntu (for some reason).
Chris

On Friday 10 July 2009, Chris Cannam wrote:
> > Sorry that I'm back sooner than expected. What is aclocal?
> > I looked in the Synaptic package manager and I don't see it.
>
> It's in the "automake" package in Ubuntu (for some reason).
Yeah, and Chris (Fryer) also needed to install some weird X11 package to
provide... I forget what.
I added a table to the "contributing" page at
http://www.rosegardenmusic.com/wiki/dev:contributing a few days ago, intended
to answer this sort of question in the future.
It was xutils-dev to get makedepend, I see looking now.
The chart isn't complete, and I think I kind of dropped that ball and got
sidetracked. Everyone else should please feel free to edit that page.
--
D. Michael McIntyre

On Fri, Jul 10, 2009 at 3:39 PM, Ilan<ilan.tal@...> wrote:
>
> Thanks Chris. Can I be so bold as to ask for some more help?
> The config isn't working. I looked in the log and there was a ton of files
> where it failed.
Try also installing the following Ubuntu packages (or meta-packages):
build-essential xutils-dev ladspa-sdk dssi-dev libasound-dev liblo-dev
liblrdf-dev fftw3-dev libqt4-dev libjack-dev
You'll have some of them already no doubt, but there's no harm in
asking apt to install them all, it'll just skip the ones you already
have.
Chris

On Friday 10 July 2009, Ilan wrote:
> I put in all of what you suggested. Then it complained about LIRC
> which I also put in.
It looks like you installed the end user package, not the -dev package. You
want -dev versions of all this stuff. Looks like
liblircclient-dev
in this case
--
D. Michael McIntyre

On Fri, Jul 10, 2009 at 4:35 PM, Ilan<ilan.tal@...> wrote:
>
> Thanks again Chris. It doesn't yet work and I'll include the config.log file.
> First of all it complains about a missing header file:
>
> conftest.cpp:8:28: error: ac_nonexistent.h: No such file or directory
>
> I put in all of what you suggested. Then it complained about LIRC
> which I also put in. LIRC had a dialog box where it asked me how to
> configure it. Since I didn't have a clue, I just used the defaults.
> It is still complaining, so something maybe isn't configured correctly.
Sorry, you need the liblircclient-dev package.
The ac_nonexistent.h error is a red herring -- it's supposed to be
nonexistent. Your problem is just the lack of the lirc client library
headers (as opposed to the lirc server).
Chris

Dear Ilan,
You wrote:
> This time it is my fault. I didn't find any fftw3, so I
> installed fftw.
> Maybe I want that root-plugin-fftw3?
> I doubt it is the documentation it is complaining about.
> Here is the config.log again
This one always trips me up.
In Ubuntu 9.04 it is:
libffw3-dev
Sincerely,
Julie S.