I agree I have been starting to relearn C and learn the *nux way of
doing things. It is kind of discouraging when the Qt examples that
were installed with Linux-Mandrake will not compile. (Oh no! "hello
world" doesn't work? I think something is wrong!) At least when you
are following the tutorial linked off the Qt home page (I think it is
also installed on the hard drive with the Qt lib when you select the
development install)
I haven't given up! I just have found other distractions right now.
I have the red book (Linux Programming) from Worx and will probably
dig into it when the snow flies.
I will have to check /etc/ld.do.conf, I know it isn't in the bash
profile. This is the newbie list right?
Thanks,
PBen
On Tue, 28 Sep 1999 06:12:04 +0000, Richard Adams
<[EMAIL PROTECTED]> wrote:
>Under normal curcumstancies its not so important as to where the libs
>are situated, its a question of the system knowing where they are,
>there are several ways of doing this,. For example in the systems
>/etc/profile or bash_profile depending on what distro is in use you
>can define lib paths in those files, another way would be to change
>paths in the Makefiles for programs needing those libs, putting the
>directory path in /etc/ld.do.conf and rerunning ldconfig, there are
>many ways.
>
>Its not what you do but HOW you do it.
>
>Realy the best way is to read the documentation in the to be made
>program first and understanding what the program expects to find and
>where it wants to look. You may have noticed that many programs say
>"ajust the Makefile accordingly" to point it to the correct lib paths.
>
