[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 143482] automake, autoconf, libtools, gcc,
From:       Matthew Brand <matthewabrand () yahoo ! co ! uk>
Date:       2007-03-26 12:53:27
Message-ID: 20070326125327.5393.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=143482         




------- Additional Comments From matthewabrand yahoo co uk  2007-03-26 14:53 -------
I agree that it would be unwise to force installation of these items whenever \
kdevelop is installed. However, maybe some kind of information would be pretty \
useful.  
The thing is, when you install kdevelop, it does come with those examples (like \
"simple Hello World"). I reckon that the first thing most new users will do is try to \
compile and run the "simple hello world" program, I did. Surely kdevelop ought to be \
able to build and run it's own shipped examples "out of the box" with as little pain \
as possible, especially when they are tagged with the word "simple". I just think it \
would be helpful to add some kind of warning (inside kdevelop) that tells new users \
that they cannot expect that to happen without installing those other bits of \
software.

It really is not obvious at all to us guys who are trying it out for the first time  \
that we need to seperately install gcc, g++, automake, autoconf and libtools in order \
to be able to compile c++ code in a c++ IDE. I had not even heard of automake, \
autoconf and libtools before today.

In my opinion, it is a bug that you can't run the examples "out of the box" and that \
no warning or information is given to point you in the right direction. I think that \
a lot of people will have simply given up and tried something else the moment that \
the program failed to compile it's own "simple hello world" program.

I'm not going to "reopen Bug". In the end it is your program so it is up to you. I am \
just providing polite feedback as requested. I am happy that I have got my copy \
working now, but thought these changes might help other new users to get started in \
compiling their c++ code using kdevelop.

All the best,
Matthew.


[prev in list] [next in list] [prev in thread] [next in thread]