This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH 02/19] include: new header ctf-api.h
- From: Nick Clifton <nickc at redhat dot com>
- To: Nick Alcock <nick dot alcock at oracle dot com>, binutils at sourceware dot org
- Date: Thu, 2 May 2019 16:07:37 +0100
- Subject: Re: [PATCH 02/19] include: new header ctf-api.h
- References: <20190430225706.159422-1-nick.alcock@oracle.com> <20190430225706.159422-3-nick.alcock@oracle.com>
Hi Nick,
> This non-installed header is the means by which libctf consumers
> communicate with libctf.
By "non-installed" do you mean that it would not be placed into /usr/include ?
If so, then how do consumers know how to communicate with libctf, given that
they might be compiled without access to the ctf sources ?
> +/* Clients can open one or more CTF containers and obtain a pointer to an
> + opaque ctf_file_t. Types are identified by an opaque ctf_id_t token.
> + They can also open or create read-only archives of CTF containers in a
> + ctf_archive_t.
Are CTF archives just arbitrary collections of CTF containers or is there more
to them than that ?
Cheers
Nick