[Buildroot] [PATCH v2 3/3] pru-sample: add sample PRU application
arnout at mind.be
Tue Nov 29 23:41:22 UTC 2016
On 28-11-16 12:34, Ash Charles wrote:
> On Sun, Nov 27, 2016 at 8:47 AM, Thomas Petazzoni
> <thomas.petazzoni at free-electrons.com
> <mailto:thomas.petazzoni at free-electrons.com>> wrote:
>> Why is pru-software-support a host package? It really builds/installs
>> things for the target, even if the target is the PRU and not the ARM.
>> Was it made a host tool after a discussion with Arnout?
> It is really best described as a staging package for the PRU. There are only
> headers and a library used for static linking. IIRC, Arnout suggested that
> putting this as staging was confusing---these aren't for the target e.g.
> ARM---and suggested instead that we treat them as host tools along with the rest
> of the tool chain.
Yeah, but now I'm not so sure anymore.
Clearly, TI_CGT_PRU_INSTALLDIR is the equivalent of STAGING_DIR for the PRU. In
that sense, it makes sense to have TI_CGT_PRU_INSTALLDIR as a subdirectory of
HOST_DIR (just like STAGING_DIR is a subdirectory of HOST_DIR). And it anyway
has to be a subdirectory of HOST_DIR because the compiler executables are
installed there as well. For me, that was the reason to say that it should be a
However, we are indeed building for the target (kind of). and we are installing
into a staging directory (though it is not in STAGING_DIR). So it makes sense to
make it a target package, with INSTALL_STAGING = YES, but where the
INSTALL_STAGING step doesn't actually install in staging but in the 'PRU
staging' i.e. TI_CGT_PRU_INSTALLDIR.
Thomas, do you agree?
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
More information about the buildroot