Auto including libraries

QNX Newsgroups (Archives) qdn.public.qnxrtp.devtools
1

In Watcom under QNX 4, there was a #pragma that could be included in header
files that would indicate that if this header file was included, then the
linker should auto include a certain library at link time.

Does a similiar option exist using gcc?

If so, what is it’s syntax?
(BTW, I don’t have the QNX 4 syntax in front of me or I would have tried
it.)

Where in the docs should I know to go look for this kind of information?
(I have always found it very easy to look things up in the QNX 4 docs. But
it seams that whenever I try to figure out something on my own in Neutrino,
I always end up looking in the wrong place.)

2

“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote in message
news:9q82kh$j49$3@inn.qnx.com…

In Watcom under QNX 4, there was a #pragma that could be included in
header
files that would indicate that if this header file was included, then the
linker should auto include a certain library at link time.

Does a similiar option exist using gcc?

Nope.

If so, what is it’s syntax?
(BTW, I don’t have the QNX 4 syntax in front of me or I would have tried
it.)

Where in the docs should I know to go look for this kind of information?
(I have always found it very easy to look things up in the QNX 4 docs.
But
it seams that whenever I try to figure out something on my own in
Neutrino,
I always end up looking in the wrong place.)

For gcc stuff, see the manuals at gcc.gnu.org. www.gnu.org also has full
manuals for all the GNU software in QNX. Categorisation has caused me
problems there. For example, docs for ld are in binutils.

Tom

3

“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
: In Watcom under QNX 4, there was a #pragma that could be included in header
: files that would indicate that if this header file was included, then the
: linker should auto include a certain library at link time.

: Does a similiar option exist using gcc?

: If so, what is it’s syntax?
: (BTW, I don’t have the QNX 4 syntax in front of me or I would have tried
: it.)

: Where in the docs should I know to go look for this kind of information?
: (I have always found it very easy to look things up in the QNX 4 docs. But
: it seams that whenever I try to figure out something on my own in Neutrino,
: I always end up looking in the wrong place.)

I can’t answer your question about the pragma, but I think you’d have to
look in the GNU docs for gcc.

As for the QNX 6 docs in general, I’m afraid they still have a way to go.
We keep hoping to have enough time to finish the Programmer’s Guide and
the Sys Admin guide, but those developers create new stuff faster than we
can document it!

However, if you have any feedback on the docs, or suggestions about how we
could improve them, please post your comments in one of the newsgroups.
Thanks.

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

4

Hi Steve

Please be assured that my comments are meant to be constructive.

You and your group are doing an excellent job. I started with QNX V2.
There documentation sucked at best. More often it was non-existant. Over
the years the QNX 4 documentation evolved to be very useful, and easy to
use, both as a tutorial and for reference.

I recognize, as others have already said in these newsgroups, that since I
came from QNX background, many things in Nto/RTP are organized differently
and therefore difficut for me to find then if I came from a Linux
background. Little by little I’m catching on in learning where to look for
what I need to know.

Perhaps some links from where us QNX old-timers would look for things to
where they are now located might help. I know that much of the
documentation still needs to be written, but much of it IS THERE. It just
seems to take forever for me to find what I’m looking for.

Also, I don’t know if it is my imagination or not but I find the global
searches from the helpviewer to be less usful in RTP then in Q4. I figure
that if I just don’t know where to look for something I should be able to do
a global search for a phrase in EVERY document and sooner or later find it.
With RTP I seam to get many more hits on my searches without actually
finding what I am looking for.

Regarding the fact that there is new software faster than you can document
it, I guess that this is a mixed blessing. I dig new software/gimicks. But
it does me no good if I don’t know it exists. Perhaps you should be willing
to post help pages that are less then polished with a disclaimer at the top
that this page is still a work in progress. I know that you do do that now
for some pages.

Another thought is that there are pages from QNX 4 that have never been
“ported” to RTP. Why not just provide them with a disclaimer that they are
for QNX 4 and should only be used as a guild but not be taken as reliable
for the RTP version of software.

Anyway, keep up the good work. We need you.

Bill Caroselli

“Steve Reid” <stever@qnx.com> wrote in message
news:9qenub$pk3$1@nntp.qnx.com…

“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote:
: In Watcom under QNX 4, there was a #pragma that could be included in
header
: files that would indicate that if this header file was included, then
the
: linker should auto include a certain library at link time.

: Does a similiar option exist using gcc?

: If so, what is it’s syntax?
: (BTW, I don’t have the QNX 4 syntax in front of me or I would have tried
: it.)

: Where in the docs should I know to go look for this kind of information?
: (I have always found it very easy to look things up in the QNX 4 docs.
But
: it seams that whenever I try to figure out something on my own in
Neutrino,
: I always end up looking in the wrong place.)

I can’t answer your question about the pragma, but I think you’d have to
look in the GNU docs for gcc.

As for the QNX 6 docs in general, I’m afraid they still have a way to go.
We keep hoping to have enough time to finish the Programmer’s Guide and
the Sys Admin guide, but those developers create new stuff faster than we
can document it!

However, if you have any feedback on the docs, or suggestions about how we
could improve them, please post your comments in one of the newsgroups.
Thanks.

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

5

“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
: Hi Steve

: Please be assured that my comments are meant to be constructive.

: You and your group are doing an excellent job. I started with QNX V2.
: There documentation sucked at best. More often it was non-existant. Over
: the years the QNX 4 documentation evolved to be very useful, and easy to
: use, both as a tutorial and for reference.

Thanks. I’m glad we’re making progress!

: I recognize, as others have already said in these newsgroups, that since I
: came from QNX background, many things in Nto/RTP are organized differently
: and therefore difficut for me to find then if I came from a Linux
: background. Little by little I’m catching on in learning where to look for
: what I need to know.

: Perhaps some links from where us QNX old-timers would look for things to
: where they are now located might help. I know that much of the
: documentation still needs to be written, but much of it IS THERE. It just
: seems to take forever for me to find what I’m looking for.

That’s a good idea. Any links in particular? It can be difficult for us
to know how our users look at the docs and where they expect to find things.
Finding things becomes more of a problem as the docs get bigger, so any
suggestions are most welcome.

: Also, I don’t know if it is my imagination or not but I find the global
: searches from the helpviewer to be less usful in RTP then in Q4. I figure
: that if I just don’t know where to look for something I should be able to do
: a global search for a phrase in EVERY document and sooner or later find it.
: With RTP I seam to get many more hits on my searches without actually
: finding what I am looking for.

I found the QNX 4 search rather slow; running grep on the docs was much
faster. I haven’t used the QNX 6 search very much. Perhaps others can
comment on it.

Most of the books have an online keyword index (generated from the same
tags as the index in the printed books) that might help.

: Regarding the fact that there is new software faster than you can document
: it, I guess that this is a mixed blessing. I dig new software/gimicks. But
: it does me no good if I don’t know it exists. Perhaps you should be willing
: to post help pages that are less then polished with a disclaimer at the top
: that this page is still a work in progress. I know that you do do that now
: for some pages.

: Another thought is that there are pages from QNX 4 that have never been
: “ported” to RTP. Why not just provide them with a disclaimer that they are
: for QNX 4 and should only be used as a guild but not be taken as reliable
: for the RTP version of software.

Those are possibilities, but we’d have to be careful. The quality of the
docs affects people’s perception of the quality of the software.

: Anyway, keep up the good work. We need you.

Thank-you, and thanks for the feedback.

(Now, did anyone answer your original question?)

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

6

“Steve Reid” <stever@qnx.com> wrote in message
news:9qkgfd$ga5$1@nntp.qnx.com…

Thank-you, and thanks for the feedback.

(Now, did anyone answer your original question?)

Actually no. I’ve given up on it for now. As an independant developer I

can’t aford to stand still for too long. But let me re-ask now in case
anyone new has some advice.

In Watcom under QNX 4, there was a #pragma that could be included in header
files that would indicate that if this header file was included, then the
linker should auto include a certain library at link time.

Does a similiar option exist using gcc?

–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net

7

“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:

Does a similiar option exist using gcc?

No. gcc has never supported suck kind of options since gcc may run
under different systems and thehlinker may vary.

Also there are only a couple of pragma directives under gcc and
(I don’t remember them all) they should only change language
parameters.

–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net


–
Wave++

8

“Wave++” <wavexx@apexmail.com> wrote in message
news:9ql34k$eh1$2@inn.qnx.com…

No. gcc has never supported suck kind of options since gcc may run
under different systems and thehlinker may vary.

Also there are only a couple of pragma directives under gcc and
(I don’t remember them all) they should only change language
parameters.

Well, i don’t think that options sucks. ;~} I kind of liked it.

BTW, can you poit to a document that lists all of the gcc pragmas?

–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net

9

“Steve Reid” <stever@qnx.com> wrote in message
news:9qkgfd$ga5$1@nntp.qnx.com…

That’s a good idea. Any links in particular? It can be difficult for us
to know how our users look at the docs and where they expect to find
things.
Finding things becomes more of a problem as the docs get bigger, so any
suggestions are most welcome.

I would like to see all of the gcc & g++ options on an easily accessable
page.

Also, I have not found any helpviewer pages for USING many of the Photon
apps; i.e. ped and pfm. There are pages that have the command line options.
On closer look, there used to be a “Photon Utilities” section,ut that whole
section does not exist in the RTP docs.

–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net

10

“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
: I would like to see all of the gcc & g++ options on an easily accessable
: page.

I assume you’d like a short description of the options, not just a list.

: Also, I have not found any helpviewer pages for USING many of the Photon
: apps; i.e. ped and pfm. There are pages that have the command line options.
: On closer look, there used to be a “Photon Utilities” section,ut that whole
: section does not exist in the RTP docs.

The usage information (for pfm, anyway) was in the Photon 1.14 User’s Guide.
Management decided that QNX 6 didn’t need a User’s Guide. We’d need to
give them a convincing business case for writing one.

Note that the Sys Admin guide covers a bit of the user interface, but this
book still needs a lot of work, and isn’t shipped yet. You can look at it on
the QDN website.

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

11

“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:

BTW, can you poit to a document that lists all of the gcc pragmas?

http://www.gnu.org/software/gcc/onlinedocs/

:slight_smile:

–
Wojtek Lerch QNX Software Systems Ltd.

12

“Steve Reid” <stever@qnx.com> wrote in message
news:9qmufi$254$1@nntp.qnx.com…

The usage information (for pfm, anyway) was in the Photon 1.14 User’s
Guide.
Management decided that QNX 6 didn’t need a User’s Guide. We’d need to
give them a convincing business case for writing one.

This was my original point. There is a lot of good documentation on QNX V4

& Photon for QNX V4 that doesn’t exist on RTP. And “Yes”, I can go look
there but anyone that only has RTP can’t.

Does comeone really need to make a business case for doing a COPY of a few
files from Q4 to RTP? I do understand the liability issues. But I do think
that a disclaimer at the top of the document that says, “This document is
copied from QNX Version 4 and has not yet been corrected for use under the
Neutrino/RTP system. It is being provided now as a guide to the use of this
program but should not be assumed to be absoutely accurate for the
Neutrino/RTP version of this program. A Neutrino/RTP version of tyhis
documentation will be made available as soon as possible.”

I also understand your statement that to someone new, ‘the perception of the
quality of the documentation will effect the perception of the quality of
the software’. I feel that an admittedly not up to date version of the
documentation will have a slightly better effect on that perception then
missing documentation. But I huess that that is a very subjectinve point of
view.

Just my $0.02 worth.

–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net

13

“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
: This was my original point. There is a lot of good documentation on QNX V4
: & Photon for QNX V4 that doesn’t exist on RTP. And “Yes”, I can go look
: there but anyone that only has RTP can’t.

The Photon 1.14 docs are on the QDN website, if that’s any help.

: Does comeone really need to make a business case for doing a COPY of a few
: files from Q4 to RTP? I do understand the liability issues. But I do think
: that a disclaimer at the top of the document that says, “This document is
: copied from QNX Version 4 and has not yet been corrected for use under the
: Neutrino/RTP system. It is being provided now as a guide to the use of this
: program but should not be assumed to be absoutely accurate for the
: Neutrino/RTP version of this program. A Neutrino/RTP version of tyhis
: documentation will be made available as soon as possible.”

I meant that we’d need a good business case to create a User’s Guide specific
to QNX 6. Given TechPub’s limited resources, I’m afraid it isn’t going to
happen soon.

Supplying the Photon 1.14 User’s Guide could imply that we were planning to
produce a new version. However, feel free to consult the QNX 4 and
Photon 1.14 docs and extrapolate to QNX 6 – as if you need my permission!

: I also understand your statement that to someone new, ‘the perception of the
: quality of the documentation will effect the perception of the quality of
: the software’. I feel that an admittedly not up to date version of the
: documentation will have a slightly better effect on that perception then
: missing documentation. But I huess that that is a very subjectinve point of
: view.

Neither one is quite as good as complete, up-to-date docs, is it? :slight_smile:

Nevertheless, we’re working hard at keeping up. Thanks again for the
feedback.

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