Enviroment variables problem

Hello,

I have such situation that I need to “tell” to one program’s make that /lib
path is the additional path for libs. How to set this enviroment variable
for all programs to search in this pointed path also. In real situation I
solved this problem in some hard way - configuring Makefile, but how to deal
with this scenario only “telling” that additional library path is for
example /lib ?

Best regards,
Darius

Hello,

I have such situation that I need to “tell” to one program’s make that
/lib
path is the additional path for libs. How to set this enviroment variable
for all programs to search in this pointed path also. In real situation I
solved this problem in some hard way - configuring Makefile, but how to
deal
with this scenario only “telling” that additional library path is for
example /lib ?

Can understand the question becouse of poor english ? or maybe i was boring
you with my stupid questions ? :slight_smile:)

Darius

“Darius” <alpha_byte@SAFe-mail.net> wrote in message
news:cicnmd$kio$1@inn.qnx.com

Hello,

I have such situation that I need to “tell” to one program’s make that
/lib
path is the additional path for libs. How to set this enviroment variable
for all programs to search in this pointed path also. In real situation I
solved this problem in some hard way - configuring Makefile, but how to
deal
with this scenario only “telling” that additional library path is for
example /lib ?

Can understand the question becouse of poor english ? or maybe i was
boring
you with my stupid questions ? > :slight_smile:> )

It’s not that the question are stupid, it’s because the answer are in the
documentation, which obvioulsy you haven’t taken the time to read. Then you
expect people that took the time to read the documentation to give you the
answer, which of course they could do but I suspect get tired of doing.

My 2 cents.

Darius

Hello,

It’s not that the question are stupid, it’s because the answer are in the
documentation, which obvioulsy you haven’t taken the time to read. Then
you
expect people that took the time to read the documentation to give you the
answer, which of course they could do but I suspect get tired of doing.

Guess you’re right. I don’t want thet people will look at the documentation
for me, but I have big problems with documentations - all I have is
programming related. Guess I need to look at the UNIX users guides.

Darius

Mario Charest <nowheretobefound@8thdimension.com> wrote:

MC > “Darius” <alpha_byte@SAFe-mail.net> wrote in message
MC > news:cicnmd$kio$1@inn.qnx.com

Hello,

I have such situation that I need to “tell” to one program’s make that
/lib
path is the additional path for libs. How to set this enviroment variable
for all programs to search in this pointed path also. In real situation I
solved this problem in some hard way - configuring Makefile, but how to
deal
with this scenario only “telling” that additional library path is for
example /lib ?

Can understand the question becouse of poor english ? or maybe i was
boring
you with my stupid questions ? > :slight_smile:> )

MC > It’s not that the question are stupid, it’s because the answer are in the
MC > documentation, which obvioulsy you haven’t taken the time to read. Then you
MC > expect people that took the time to read the documentation to give you the
MC > answer, which of course they could do but I suspect get tired of doing.

MC > My 2 cents.

Ouch Mario!

I’ve been playing with RTP for 3 years now and I still have a hard time
finding many things in the documentation. And it’s not so much that I’ve
learned how to use the documentation, it’s that I’ve learned how to do
what I need to do without requiring the documentation.

Somehow I always felt that the QNX 4 documenation was organized better.
I don’t know why, but things were always where I thought of looking first.

With QNX6 I usually have to look in several places to find out how to do
something. And much of the time I find my answers by going through old
newsgroup articles.

Bill Caroselli wrote:

Somehow I always felt that the QNX 4 documenation was organized better.
I don’t know why, but things were always where I thought of looking first.

With QNX6 I usually have to look in several places to find out how to do
something. And much of the time I find my answers by going through old
newsgroup articles.

You know you can send the docs folks at QNX feedback directly by
emailing the docs address here… :wink:


Chris Herborth (cherborth@qnx.com)
Never send a monster to do the work of an evil scientist.

Bill Caroselli <qtps@earthlink.net> wrote:

Somehow I always felt that the QNX 4 documenation was organized better.
I don’t know why, but things were always where I thought of looking first.

With QNX6 I usually have to look in several places to find out how to do
something. And much of the time I find my answers by going through old
newsgroup articles.

Part of your problem with the Neutrino docs could be that there are
simply a lot more of them. I have a complete set of the printed Neutrino
docs, and they make a 30" stack of books, which is probably twice as
much as the QNX 4 docs – and there are some docs that we haven’t printed.

However (as Chris wrote), we’re interested in any suggestions that you
have for improving the docs.


Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

“Bill Caroselli” <qtps@earthlink.net> wrote in message
news:ciekl3$5kd$1@inn.qnx.com

Mario Charest <> nowheretobefound@8thdimension.com> > wrote:

MC > “Darius” <> alpha_byte@SAFe-mail.net> > wrote in message
MC > news:cicnmd$kio$> 1@inn.qnx.com> …
Hello,

I have such situation that I need to “tell” to one program’s make that
/lib
path is the additional path for libs. How to set this enviroment
variable
for all programs to search in this pointed path also. In real situation
I
solved this problem in some hard way - configuring Makefile, but how to
deal
with this scenario only “telling” that additional library path is for
example /lib ?

Can understand the question becouse of poor english ? or maybe i was
boring
you with my stupid questions ? > :slight_smile:> )

MC > It’s not that the question are stupid, it’s because the answer are in
the
MC > documentation, which obvioulsy you haven’t taken the time to read.
Then you
MC > expect people that took the time to read the documentation to give
you the
MC > answer, which of course they could do but I suspect get tired of
doing.

MC > My 2 cents.

Ouch Mario!

I didn’t mean any disrespect. Just trying to speak my mind.

Oh and Darius about your question. Modifing the makefile to specify the
library path is fine. Using an environment variable is not a good idea IMHO
because these are the type of config that gets lost over time. In 2 years
from now, if you try to rebuild the executable you’ll have to make sure that
environment variable is properly set.

If the makefile was generated by the IDE than it’s a different issue. There
is a setting in one of the windows to specify additionnal library path,
don’t recall where it is.

Chris Herborth <cherborth@qnx.com> wrote:
CH > Bill Caroselli wrote:

Somehow I always felt that the QNX 4 documenation was organized better.
I don’t know why, but things were always where I thought of looking first.

With QNX6 I usually have to look in several places to find out how to do
something. And much of the time I find my answers by going through old
newsgroup articles.

CH > You know you can send the docs folks at QNX feedback directly by
CH > emailing the docs address here… :wink:

It’s nothing specific that I can put my finger on. I don’t think it’s
like Steve said, that there is so much more documentation, because I felt
much stronger about this earlier on in my QNX6 learning curve.

It may just be that the QNX 4 philosophy was so ingrained in my mind that
I just naturally knew where everything was.

Overall, the QNX documentation is VERY GOOD and getting better with each
new release. Keep up the good work Steve et al.

I was simply trying to tell Mario not to be so hard on someone because
they couldn’t find something in the documentation. It takes some getting
used to.

I’m sure that the Photon folks thought I was a PITA over the last month
or two. Most of my QNX work has been under the hood, but I had to work on
a fairly substancial GUI project. I learned a hell of a lot about photon,
by asking.

Bill Caroselli <qtps@earthlink.net> wrote:

Chris Herborth <> cherborth@qnx.com> > wrote:
CH > Bill Caroselli wrote:
CH > You know you can send the docs folks at QNX feedback directly by
CH > emailing the docs address here… > :wink:

It’s nothing specific that I can put my finger on. I don’t think it’s
like Steve said, that there is so much more documentation, because I felt
much stronger about this earlier on in my QNX6 learning curve.

A thing that was (severely) missing in pre-6.3.0 docs was a Users Guide.
(And system administration guide, too.) QNX4 had these from quite early
on. QNX 6 now has them, and they should help, possibly a lot.

-David

QNX Training Services
http://www.qnx.com/services/training/
Please followup in this newsgroup if you have further questions.