On Mon, Jun 09, 2003 at 06:55:50PM +0200, Michael Nordstrom wrote:
> Hmm, I don't think I want hard-coded paths in the code base when
> they can be avoided. This line is from armlets/armletldscript:
>
> SEARCH_DIR(/usr/arm-palmos/lib);
[...]
> - the viewer.rcp file doesn't depend directly on the source code
> in the armlets dir; it depends on the armlets.rcp file.
The configure.in patch searches for arm-palmos-gcc (only), which means
that you have decided (rightly IMHO :-)) to use prc-tools-arm, and not
hunt around for various home-grown arm-elf-gccs, such as the mess-heap
that is Palm(Source)'s ArmletTools. Having decided that, you might want
to use prc-tools's specific facilities for producing armlets, rather
than mucking about with your own hard-coded linker script, objcopy,
and PilRC.
Your build process can be as simple as
arm-palmos-gcc -nostartfiles -O2 -o search search.c
build-prc -o viewer.prc [...] search [...]
when you use STANDALONE_CODE_RESOURCE_ID(armDoSearch) in search.c. No
linker script, no explicit and direct linker invocation, no objcopy (and
hence better diagnostics), and no PilRC here. See the documentation for
details.
At that point, your armlet would consist of approximately one source
file (search.c, plus whatever endianness mucking header you might feel
the need for), so I'm not sure I see that you gain much by creating an
"armlets" subdirectory for it. But that's another story, I guess...
John
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
