Why do you go on an on about word counts, etc. Why not just quote what I said? Here it is fully in context.
"It compiles just fine but apparently in the linking process it can't find the SDK. I had the same problem when my IDE tried to build an application. Pass 1 worked fine but pass 2 failed to find the SDK, with the same error listed below. 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." Notice that I said I fixed the problem as far as the IDE was concerned. I then went on to say that it still did not work at the Command Level. But you took this to mean that the IDE is still not working. But again, there is no point in going on because no matter what I say or where I point to the problem, you come back like it's something to do with the IDE or my "stupidity." Or Aaron saying things like "not idiot proof." IF I'm not running the IDE and am trying to execute "make" from a BASH shell, how can it be an IDE problem. If I follow the directions, as written, and don't violate the instructions, how can it be "stupidity?" I only mentioned the IDE to show what I had to do to get it working. It was a point of information that I thought you could use, to help resolve the problem. But I guess I'll drop the matter and just deal with others, since this is such a burden for you and Aaron. You even say you get tired of the "same old questions" but then say, "this is the only case of this in history of prc-tools", so it can hardly be "same old questions", can it. Anyway, I won't bother you any further. You can have the last word on this subject. > 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/ > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
