PDA

View Full Version : How to install new theme



weapon-x
22nd July 2006, 08:06 AM
Hi friends as i m new to FC5 and linux i dont know how to install the themes and another
softwares in this Os .Can anybudy tell me how to install them with deatil information .
I try to read the README and intall file but cant understand it. :p

JoeyJoJoe
22nd July 2006, 01:38 PM
well, the file that is their is called a gziped tarball (that might not be spelt right but you get the idea).

to install it you will need to uncompress it firstly, you can do this from the terminal, or just right click on it and pick "extract here", this will create a folder where ever the file was (for example in your home directory or on your desktop.

OK, now you need to open up the terminal and "cd" into that directory - to do this you'll need to use a command which will take this form


cd /home/<user name>/QtCurve-Gtk2-0.39.1

for you if your user name is say "bob" then it'll be /home/bob/Qt....
Capital letters are important because linux treats the small and capital letters almost like different letters...

ok, now we're in that directory you'll need to type something like


./configure

make

(then you might need to use su to become root, if your not already)
make install


this is an example, it could be different for that file, but after you've extracted it you can open the file which will say exactly what you need to type which is called "install", but you should now know what to look for

weapon-x
23rd July 2006, 06:58 AM
Hi when i Use these steps i got this errors::
[root@localhost domino-0.2]# ./configure
checking build system type... i686-pc-linux-gnuoldld
checking host system type... i686-pc-linux-gnuoldld
checking target system type... i686-pc-linux-gnuoldld
checking for a BSD-compatible install... /usr/bin/install -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for kde-config... /usr/bin/kde-config
checking where to install... /usr (as returned by kde-config)
checking for style of include used by make... GNU
checking for gcc... no
checking for cc... no
checking for cc... no
checking for cl... no
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.
[root@localhost domino-0.2]# make
make: *** No targets specified and no makefile found. Stop.
[root@localhost domino-0.2]# make INSTALL
make: Nothing to be done for `INSTALL'.

JoeyJoJoe
23rd July 2006, 10:17 AM
hmm, I get the same thing and when I asked I was just told "it means you don't have the C compiler", I thought it was just something going a bit strange on my system, and I'm not too sure what library you need. It's a shame that FC5 doesn't come in built with this considering the close connection to GNU.

Someone else might be able to provide some better info, but I searched round in yum for you and this seemed like it might be what you need;


gcc-objc++.i386 4.1.1-1.fc5 updates
Matched from:
gcc-objc++
Objective-C++ support for GCC
gcc-objc++ package provides Objective-C++ support for the GCC.
http://gcc.gnu.org

but don't hold me to that.
Other than that is this in yum? programs that are in yum are so much easier to get and keep up to date. Also you can get more themes doing "yum install gnome-themes-extras" and if you don't already have it you could try "yum install gnome-themes"

weapon-x
23rd July 2006, 10:47 AM
hmm, I get the same thing and when I asked I was just told "it means you don't have the C compiler", I thought it was just something going a bit strange on my system, and I'm not too sure what library you need. It's a shame that FC5 doesn't come in built with this considering the close connection to GNU.

Someone else might be able to provide some better info, but I searched round in yum for you and this seemed like it might be what you need;


gcc-objc++.i386 4.1.1-1.fc5 updates
Matched from:
gcc-objc++
Objective-C++ support for GCC
gcc-objc++ package provides Objective-C++ support for the GCC.
http://gcc.gnu.org

but don't hold me to that.
Other than that is this in yum? programs that are in yum are so much easier to get and keep up to date. Also you can get more themes doing "yum install gnome-themes-extras" and if you don't already have it you could try "yum install gnome-themes"
where i put this code

JoeyJoJoe
23rd July 2006, 10:58 AM
if you go to Applications > Accessories > terminal then it opens up a window which you can type in, if you want to use


yum install gnome-themes-extras

then first type


su - (the space and hyphen are important)
then type in your root password, the one that you set when you first installed the system
then type the line "yum install gnome-themes-extras"

if you want to try and get that library (it might work) do the su - thing to become root and then type


yum install gcc-objc++.i386

weapon-x
31st July 2006, 07:29 AM
if you go to Applications > Accessories > terminal then it opens up a window which you can type in, if you want to use


yum install gnome-themes-extras

then first type


su - (the space and hyphen are important)
then type in your root password, the one that you set when you first installed the system
then type the line "yum install gnome-themes-extras"

if you want to try and get that library (it might work) do the su - thing to become root and then type


yum install gcc-objc++.i386
I have install gcc-objc++.i386 now it shows this when i type ./configure :----
[root@localhost Themes]# cd /download/Themes/QtCurve
[root@localhost QtCurve]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking for a sed that does not truncate output...
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
appending configuration tag "GCJ" to libtool
checking if gcj supports -fno-rtti -fno-exceptions... (cached) no
checking for gcj option to produce PIC... -fPIC
checking if gcj PIC flag -fPIC works... no
checking if gcj supports -c -o file.o... no
checking whether the gcj linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking for pkg-config... no
./configure: line 15293: no: command not found
configure: error: Gtk2.x not installed
[root@localhost QtCurve]# make
make: *** No targets specified and no makefile found. Stop.
[root@localhost QtCurve]# make INSTALL
make: Nothing to be done for `INSTALL'.
[root@localhost QtCurve]# make install
make: *** No rule to make target `install'. Stop.

spyder0101
18th August 2006, 07:19 PM
is there a way to do that withoug using the command line?

JoeyJoJoe
18th August 2006, 07:49 PM
hmm, no I don't think so, I'd try using


yum install gnome-themes-extras

is easy to do and gives you some themes which you probs won't have, getting the library for the install always seems confusing to me so I've given up installing that way