Overriding linkcmds?
James Fitzsimons
james.fitzsimons at gmail.com
Thu Feb 6 21:03:17 UTC 2014
Thanks for your replies guys,
Sebastian - I'll see if I can figure out how to work that into my makefile.
I suppose I could try using the CFLAGS_FOR_TARGET again like I did with the
header include path....
Peter - I'm targeting a M68332 (specifically the mrm332 bsp). Ideally I'd
like a simple makefile switch I can turn on or off to target RAM or ROM,
but if it's too difficult I'll just cheat and rename my linker scripts
depending on where I want to load my code to.
Cheers,
James Fitzsimons
On 7 February 2014 00:41, Peter Dufault <dufault at hda.com> wrote:
> What target are you using? On the MPC5554 I use the MMU to swap the flash
> and the RAM so it winds up being the same image. Of course it means my
> development system needs to be loaded with RAM.
>
> On Feb 6, 2014, at 04:37 , James Fitzsimons <james.fitzsimons at gmail.com>
> wrote:
>
> Hi all,
>
> I'm slowly trying to figure out the RTEMS build process and how to bend it
> to my will!
>
> I have two linker scripts, one for running out of RAM, and one for running
> out of ROM.
>
> Is there anyway to override which linker file will be used in your
> makefile?
>
> I found the following in my gcc-target-default.cfg
>
> #
> # Allow user to override link commands (to build a prom image, perhaps)
> #
> ifndef LINKCMDS
> LINKCMDS=$(PROJECT_RELEASE)/lib/linkcmds
> endif
>
> But overriding LINKCMDS and specifying a different linker script in my
> makefile didn't work.
>
> Any advice would be gratefully received.
>
> Thanks and regards,
> James Fitzsimons
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users
>
>
> Peter
> -----------------
> Peter Dufault
> HD Associates, Inc. Software and System Engineering
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20140207/8ed353db/attachment-0001.html>
More information about the users
mailing list