Re: Other standard GNU tools and alternate linker files

On 5/22/22 13:11, Duane Ellis wrote:

This isn't going to be a complete answer, just some pointers.

> So – in the Embedded world
> 
> Question #1
> 
> Often one uses the “OBJCOPY” tool – or something else to post process 
> the executable (ELF) into a BIN or a HEX file – how should that be handled.
> 
> NOTE: It seems this and many other similar things should be detected as 
> part of Scons but is not
> 
> Examples include:  NM, LD, OBJCOPY, OBJDUMP, STRIP, etc.
> 
> How would you suggest handling their uses?


Take a look at AddPostAction (and AddPreAction) for some simple stuff. 
It's a bit of a difference whether the processing happens in-place, or 
produces a new file - in the latter case you'd want a way to define that 
such a target is to be created, because it's no longer the same as the 
target of Program or whatever builder you used.


> Question #2
> 
>                  The Linux Kernel uses a reasonably nice GUI based 
> CONFIG tool.

There isn't one of those.

You can specify a whole bunch of variables on the commandline and 
process them, and decide what to do with the outcomes.  You can 
eventually store that information in a file (it's actually a Python 
script as well) so it doesn't have to be retyped each time.  Presumably 
it wouldn't be hard to write a front-end that sets up that file, but one 
isn't provided. Maybe scan this section (or the whole chapter):

https://scons.org/doc/4.3.0/HTML/scons-user/ch10.html
_______________________________________________
Scons-users mailing list
[email protected]
https://pairlist4.pair.net/mailman/listinfo/scons-users