Re: #include <rpmio.h> vs #include <rpm/rpmio.h>

[Jeff Johnson <jbj JBJ ORG>]

On Thu, Sep 21, 2000 at 08:21:32PM -0400, Alfredo Kengi Kojima wrote:
> 
> Hi
> 
> Is there a reason why rpmlib headers do things like:
> 
> #include <rpmio.h>
> #include <dbindex.h>
> #include <header.h>
> 

Yes. Adding <rpm/...> breaks building rpm itself.

> forcing progs that include them to pass -I/usr/include/rpm
> to gcc, instead of:
> 
> #include <rpm/rpmio.h>
> #include <rpm/dbindex.h>
> #include <rpm/header.h>
> 
> ?
> 

Yup, that's what you have to do.

> If no, is there any change that would be changed in the next
> releases?
> 

A partial fix (for gcc anyways) is to use
	#include "rpmio.h"
	#include "dbindex.h"
	#include "header.h"
which will search the same directory in which rpmlib.h was found, but
-I/usr/include/rpm is still preferred.

73 de Jeff

-- 
Jeff Johnson	ARS N3NPQ
jbj@jbj.org	(jbj@redhat.com)
Chapel Hill, NC