The only reference I could find to John's message is on the prc-tools 
release note page:

        <http://prc-tools.sf.net/releases.html>

where he says that m68k-palmos-obj-res is no longer needed to convert 
bfd files into something that build-prc can read because build-prc 
can read bfd files directly now. (But since my local e-mail archives 
only go back to March and the change in question was made 13 months 
before that, I might have to go back to my older e-mail archives to 
find an actual announcement.)

As well there was the following posting to this list:

At 4:59 PM -0400 8/31/01, Kelly Morrison wrote:
>3. As Foster points out in his book, don't forget to remove (or comment out)
>the m68k-palmos-obj-res rule and the lines that mention the .grc files.
>
>4. Finally, the rule that calls build-prc in the example in the Foster book
>didn't work for me. It recommended something like:
>    myapp.prc: myapp
>       build-prc myapp.prc "My App" LFlb myapp.def myapp *.bin
>
>    I had to use the following to get mine to work:
>    $(PRC): $(APP) bin.stamp
>       $(BUILDPRC) $(DEF) $(APP) *.bin
>
>    where $(BUILDPRC) is the build-prc tool; $(DEF) is my .def file; $(APP)
>is my application name; and $(PRC) is the final result.

I'm not too familiar with the prc-tools build process, but perhaps 
there's something in there that makes sense to you.

-- Keith


At 3:26 PM +1100 12/5/01, Michael Glickman wrote:
>In one of recent messages (sorry for no reference)
>John Marshall mentioned that m68k-palmos-obj-res
>is included only for backward compatibility, and
>we all can live happily without it.
>
>So I did. I commented out the line related
>to m68k-palmos-obj-res and removed *.grc from
>build-prc (otherwise it complains).
>Indeed .prc was created witout errors.
>
>I successfully installed prc into pose,
>but when I tried launching, I got pose error:
>
>       The application cannot be launched
>       because of a system error
>
>I returned back to 'old-style' pattern and everything
>was nice again.
>
>Looking forward to your anticipated comments.
>
>M.

-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/tech/support/forums/

Reply via email to