according to prctools docs
texi/prc-tools_5.html#SEC4
there is something like
There are also the following caveats:
* While describing the section attribute, the GCC manual suggests using the
linker to split an executable into sections. Just like `-ffunction-sections',
this doesn't work.
so i guess split by file won't work too. problem is that as far as i know
splitting to multiple segment is needed to be known at compile stage
Russell Cagle wrote:
> Hey all,
>
> I've written a multi-segment application, I think I've even answered a
> multi-segment question or two on this mailing list, but it's a confusing
> subject and now I have a multi-segment question of my own: has anyone
> had any success with the --split-by-file argument to the GCC linker?
> It's supposed to automatically split the application into sections by
> file, as the name says. It seems to work with the ARM linker but not
> with the m68k linker.
>
> Here's how I call it with the ARM linker:
> arm-palmos-gcc -fPIC -Os -Wl,--split-by-file=1 -march=armv4t
> -msingle-pic-base -Wl,--emit-relocs -nostartfiles -o $@ $(OBJS)
>
> I've tried lots of similar combinations with the m68k, but I always get
> the standard out-of-space error.
>
> What I'm trying to do is write some portable code, and it just bugs me
> to add Palm-specific declarations to every function. As another
> possible multi-segment workaround, I've downloaded Multilink, but it
> looks old and has lots of warnings about global variables. Is anyone
> out there still using Multilink, or should I give it a miss?
>
> I'd also consider using PODS if it would let me write ARM code for 5.x
> devices.
>
> Thanks,
> Russell
>
>
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
