[U-Boot] why is there no ".u-boot.map.cmd" generated?
short followup to earlier question ... i was going to check the file .u-boot.map.cmd to see which command was used to generate it but, unlike numerous other files of that form, that file has no associated .cmd file. any reason for that?
rday
Hi Robert,
On Mon, Apr 8, 2019 at 4:51 AM Robert P. J. Day rpjday@crashcourse.ca wrote:
short followup to earlier question ... i was going to check the file .u-boot.map.cmd to see which command was used to generate it but, unlike numerous other files of that form, that file has no associated .cmd file. any reason for that?
The reason is that u-boot.map isn't a target, you can't run 'make u-boot.map'. It gets generated as side-effect of the final link (see cmd_u_boot__ in the main Makefile). You can see the command that generates it in .uboot.cmd.
On Mon, 8 Apr 2019, Chris Packham wrote:
Hi Robert,
On Mon, Apr 8, 2019 at 4:51 AM Robert P. J. Day rpjday@crashcourse.ca wrote:
short followup to earlier question ... i was going to check the file .u-boot.map.cmd to see which command was used to generate it but, unlike numerous other files of that form, that file has no associated .cmd file. any reason for that?
The reason is that u-boot.map isn't a target, you can't run 'make u-boot.map'. It gets generated as side-effect of the final link (see cmd_u_boot__ in the main Makefile). You can see the command that generates it in .uboot.cmd.
ah, understood.
rday
On Mon, 8 Apr 2019, Chris Packham wrote:
Hi Robert,
On Mon, Apr 8, 2019 at 4:51 AM Robert P. J. Day rpjday@crashcourse.ca wrote:
short followup to earlier question ... i was going to check the file .u-boot.map.cmd to see which command was used to generate it but, unlike numerous other files of that form, that file has no associated .cmd file. any reason for that?
The reason is that u-boot.map isn't a target, you can't run 'make u-boot.map'. It gets generated as side-effect of the final link (see cmd_u_boot__ in the main Makefile). You can see the command that generates it in .uboot.cmd.
ok, i see how it works (i think). this is the first time i've actually taken a close look at those .u-boot.*.cmd files. just to confirm, each of those files represents a *single* command executed to produce one (or more) of the final artifacts of the build process. and in the case of u-boot.map, it's the "-Map u-boot.map" option to the linker that specifies the output for the map file.
it all makes sense once one is clued in. thanks for that.
rday
p.s. i may have more occasional questions that seem trivially obvious to others, as i am currently digging into parts of u-boot i've never hacked around in before.
participants (2)
-
Chris Packham -
Robert P. J. Day