Very Computer

by **icefo** » Tue, 09 Mar 1999 04:00:00

How do I complile anything?? I downloaded kedit, kmail, etc. there is
no Makefile that I can just "make". I run progrp and then tmake, but
then I get a *.moc file not found when I then "make" it. I have heard
of automoc, and automake and other stuff. What are they???? How do I
get them??? The web site that linked to automake went to a 404. Why
isn't there a page up to discribe all these problems? Why do we have to
come to a newsgroup? Why has these kinds of questions been asked
countless times in the message boards, but I STILL don't have a clue.
Help me please!

by **William DeBrin** » Tue, 09 Mar 1999 04:00:00

If you're new to KDE or Linux in general, and if you're using a distrinution
that supports RPM (i.e. RedHat) it may be easier to download KDE in RPM
format. That way you can use the rpm command (rpm -Uvh) or the glint
utility to install KDE without having to compile.

If you must compile, download each of the components (i.e.
kdebase-1.1.tar.gz) then execute the following commands for each one

# gunzip [package name].tar.gz
# tar xvf [package name].tar
# cd [package name directory]
# ./configure
# make
# make install

You will need QT before installing KDE.

See http://www.kde.org/documentation/en/general/faq/index-4.html - most, if
not all, of your questions should be answered there

Good luck
William

> How do I complile anything?? I downloaded kedit, kmail, etc. there is
> no Makefile that I can just "make". I run progrp and then tmake, but
> then I get a *.moc file not found when I then "make" it. I have heard
> of automoc, and automake and other stuff. What are they???? How do I
> get them??? The web site that linked to automake went to a 404. Why
> isn't there a page up to discribe all these problems? Why do we have to
> come to a newsgroup? Why has these kinds of questions been asked
> countless times in the message boards, but I STILL don't have a clue.
> Help me please!

by **icefo** » Tue, 09 Mar 1999 04:00:00

I am new to Linux, but not that new. I have the latest and greatest QT
allready. I want to be able to compile to the program without using ./config.
Or if I have to use ./config, where can I find out more information about this
program? What does it do and why? can't I just make a Makefile on my own and
make it?

Quote:> # cd [package name directory]
> # ./configure
> # make
> # make install

> > How do I complile anything?? I downloaded kedit, kmail, etc. there is
> > no Makefile that I can just "make". I run progrp and then tmake, but
> > then I get a *.moc file not found when I then "make" it. I have heard
> > of automoc, and automake and other stuff. What are they???? How do I
> > get them??? The web site that linked to automake went to a 404. Why
> > isn't there a page up to discribe all these problems? Why do we have to
> > come to a newsgroup? Why has these kinds of questions been asked
> > countless times in the message boards, but I STILL don't have a clue.
> > Help me please!

by **Mike Khali** » Tue, 09 Mar 1999 04:00:00

>I am new to Linux, but not that new. I have the latest and greatest QT
>allready. I want to be able to compile to the program without using ./config.
>Or if I have to use ./config, where can I find out more information about this
>program? What does it do and why? can't I just make a Makefile on my own and
>make it?

It generates a makefile. A solaris box and a linux box probably require two
makefiles. I put things in /usr/local that others put in / or /usr. It
figures this out, and it give you flexibility in define things for yourself
(do ./configure --help to see the options). The idea is to make a source
portable and non-platform specific. Sure you could write your own makefile,
but then again you could use a screwdriver to cut down a tree.

by **icefo** » Tue, 09 Mar 1999 04:00:00

That wasn't my point. yes I want portability. So to make a make file I use tmake,
then just make. Why do I need ./config?? What does it do?

> >I am new to Linux, but not that new. I have the latest and greatest QT
> >allready. I want to be able to compile to the program without using ./config.
> >Or if I have to use ./config, where can I find out more information about this
> >program? What does it do and why? can't I just make a Makefile on my own and
> >make it?

> It generates a makefile. A solaris box and a linux box probably require two
> makefiles. I put things in /usr/local that others put in / or /usr. It
> figures this out, and it give you flexibility in define things for yourself
> (do ./configure --help to see the options). The idea is to make a source
> portable and non-platform specific. Sure you could write your own makefile,
> but then again you could use a screwdriver to cut down a tree.

by **Mike Khali** » Tue, 09 Mar 1999 04:00:00

>That wasn't my point. yes I want portability. So to make a make file I use tmake,
>then just make. Why do I need ./config?? What does it do?

Just what I said. It generates a makefile. Tmake is just a different way
to do the same thing. However, tmake is less used, not available on many
systems, and less powerful. configure files can easily be generated
by gnu-autoconf, which is shipped with all linux distributions I've seen,
and a number of commercial unices as well. In contrast, tmake is only
availbale on a subset of all systems which ship with qt. It very
non-standard and is really only meant as a helper for developers.
Furthermore the configure scripts allow for a great number of options.
--prefix is probably the most pervasive and most useful to me. I use a
system of package management known as encap. In the encap system, all
programs are installed in a seperate directory, such as
/usr/local/encap/qt-1.42. Then use an encap-1.1 compliant package manager,
the subdirs of this directory have their respective files linked into
/usr/local, so /usr/local/encap/qt-1.42/bin/moc is linked to from
/usr/local/bin/moc. When I upgrade, I simply use the package manager to
unlink and link in the new package. It is very clean. Configure scripts
are emensely useful with a system like this. Otherwise one needs to
hardcode the prefix, and I need then to read through the makefile and find
the appropriate lines to alter so that it appropriately installs into a
subtree of the encap tree. That's a pain in the ass. --prefix makes it
trivial. Another use of configure scripts is to allow you to choose which
options you may or may not wish to compile into an application. For the
best example of this, go grab the mozilla source. It has tons of options to
turn on and off through flags to configure. I guess in summary RTFM, and
pass --help to .configure and see the multiple options and configurability
the scripts give you, and you will soon understand why they are used.

by **icefo** » Tue, 09 Mar 1999 04:00:00

ok, so I have a program that I wish to compile. It uses Qt etc. Asuming all the code
works I jsut go to the dir where all the files are and type

autoconfig
./config
make

And then it will make me a program?

> >That wasn't my point. yes I want portability. So to make a make file I use tmake,
> >then just make. Why do I need ./config?? What does it do?

> Just what I said. It generates a makefile. Tmake is just a different way
> to do the same thing. However, tmake is less used, not available on many
> systems, and less powerful. configure files can easily be generated
> by gnu-autoconf, which is shipped with all linux distributions I've seen,
> and a number of commercial unices as well. In contrast, tmake is only
> availbale on a subset of all systems which ship with qt. It very
> non-standard and is really only meant as a helper for developers.
> Furthermore the configure scripts allow for a great number of options.
> --prefix is probably the most pervasive and most useful to me. I use a
> system of package management known as encap. In the encap system, all
> programs are installed in a seperate directory, such as
> /usr/local/encap/qt-1.42. Then use an encap-1.1 compliant package manager,
> the subdirs of this directory have their respective files linked into
> /usr/local, so /usr/local/encap/qt-1.42/bin/moc is linked to from
> /usr/local/bin/moc. When I upgrade, I simply use the package manager to
> unlink and link in the new package. It is very clean. Configure scripts
> are emensely useful with a system like this. Otherwise one needs to
> hardcode the prefix, and I need then to read through the makefile and find
> the appropriate lines to alter so that it appropriately installs into a
> subtree of the encap tree. That's a pain in the ass. --prefix makes it
> trivial. Another use of configure scripts is to allow you to choose which
> options you may or may not wish to compile into an application. For the
> best example of this, go grab the mozilla source. It has tons of options to
> turn on and off through flags to configure. I guess in summary RTFM, and
> pass --help to .configure and see the multiple options and configurability
> the scripts give you, and you will soon understand why they are used.

by **icefo** » Tue, 09 Mar 1999 04:00:00

wait I see that doesn't do squat. I guess I have to make a autoconfig.in file or somthing
from the looks of it. Going hunting for the manual now. Oh goody another 30 page on-line
manual to read. Once I am done with that I will try the thing again......

> ok, so I have a program that I wish to compile. It uses Qt etc. Asuming all the code
> works I jsut go to the dir where all the files are and type

> autoconfig
> ./config
> make

> And then it will make me a program?

by **Tony Smol** » Tue, 09 Mar 1999 04:00:00

>ok, so I have a program that I wish to compile. It uses Qt etc. Asuming all the code
>works I jsut go to the dir where all the files are and type

>autoconfig
>./config
>make

>And then it will make me a program?

Your overcomplicating it.

it's:

./configure
make

by **icefo** » Thu, 11 Mar 1999 04:00:00

I MADE the program so I have to autoconfig it

> >ok, so I have a program that I wish to compile. It uses Qt etc. Asuming all the code
> >works I jsut go to the dir where all the files are and type

> >autoconfig
> >./config
> >make

> >And then it will make me a program?

> Your overcomplicating it.

> it's:

> ./configure
> make

Very Computer

Newbie

Newbie

Newbie

Newbie

Newbie

Newbie

Newbie

Newbie

Newbie

Newbie

Newbie