Previously, Mike Davis wrote:
> Again, my
> problem is that I get an error listed below, when I try to use the
> "make" command ***from the command line***, ***not the IDE***.
And now he writes again:
> Again, (***AGAIN***) you really need to read what I wrote. I said IT
> WORKS (I did not say it did not work in my IDE). The IDE works fine.
> It is from the BASH COMMAND LINE THAT IT DOES NOT WORK!!!!!
[...]
> You are so defensive that you don't even read the details of what
> people write. That is a main source of problems.
Okay, so let's go back and reread the details of what you wrote. In
http://www.escribe.com/computing/pcpqa/m56887.html
you used the word "IDE" five times, and the words "make", "shell", and
"bash" a total of zero times. You also refered to "pass 1" and "pass 2"
frequently. It was unclear to me exactly what you meant by these
passes, but from the context it seemed to refer to the compiling and
linking phases of a build invoked from your IDE.
But apparently you were not talking about your IDE at all. Okay.
You did use the words "command line" once:
> In the IDE I added the -palmos3.5 to the parameter list of the
> command, for pass 2. that fixed pass 2 error in the IDE.
>
> But I'm not sure where that is done for command line operation.
>
> Pass 1 shows the *-gcc using -palmos3.5 but pass 2 does not.
At the time I replied (in part)
> Sounds like you've figured out how to fix the problem by yourself.
> If your IDE doesn't invoke prc-tools correctly then that's something
> you need to take up with your IDE's authors.
Let me now expand on that a little:
* If you told the IDE that you wanted to build with the 3.5 SDK and it
automatically added -palmos3.5 to the compile command (pass 1) but not
to the link command (pass 2), then that is a bug in the IDE because
you won't be able to link with (e.g.) the correct PalmOSGlue libraries
without correcting it manually.
* Your first paragraph showed that you had figured out how to provide an
SDK for the link command and thus suppress the warning. Your third
paragraph showed that you could see the exact difference between the
two command lines. So I assumed that, as a competent programmer, you
would be able to see how to apply your knowledge in the similar case
of a command line invoked from make or bash. Sorry if I assumed too
much :-).
* If you (or someone else -- I understand Mike's IDE does not use
makefiles itself, so he is probably not doing this) are using implicit
rules in a makefile, you probably know about the CFLAGS make variable,
via which you can communicate -palmosX flags to compile commands.
There is also a LDFLAGS variable which can be used similarly for link
rules with implicit commands.
* Incidentally, "sdkfind: warning: 'sdk' not found" is a *warning*, not
an error. If you are not actually linking with PalmOSGlue or the
like, then this warning at link compile does not cause any trouble.
If you do link with some SDK library, you'll also get a "library not
found" error, and the warning will help you understand why the library
was not found.
In short, as can be discerned from the prc-tools documentation, you can
add -palmosX options to link commands just as you can add them to compile
commands. As usual, you can add a -v option to any m68k-palmos-gcc
commands to see exactly what is going on.
Was that any clearer?
John "I'm impressed that you have been able to maintain this energy
level for several days now"
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
