e2fsprogs/lib/ext2fs/ext2fs.pc.in

prefix=@prefix@
exec_prefix=@exec_prefix@
libdir=@libdir@
includedir=@includedir@

Name: ext2fs
Description: Ext2fs library
Version: @E2FSPROGS_VERSION@
Requires.private: com_err
Cflags: -I${includedir}/ext2fs -I${includedir}
Libs: -L${libdir} -lext2fs
Add pkg-config files to e2fsprogs's libraries. 2005-01-26 20:59:25 +03:00			`prefix=@prefix@`
			`exec_prefix=@exec_prefix@`
			`libdir=@libdir@`
			`includedir=@includedir@`

			`Name: ext2fs`
			`Description: Ext2fs library`
			`Version: @E2FSPROGS_VERSION@`
Fix pkg-config files: use Requires.private and fix the include directory Addresses-Sourceforge-Bug: #2089537 Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 2008-09-03 05:20:44 +04:00			`Requires.private: com_err`
Change pkg-config files so that both <et/com_err.h> and <com_err.h> work Change the include path in the Cflags field so that #include <lib/foo.h> and <foo.h> will work. We had originally used a C flags which allowed <foo.h> to work, but many applications (especially those not using pkg-config) had been using the <lob/foo.h> formulation which didn't require an explicit -I{$includedir} option to the C compiler. If those applications then converted over to pkg-config, and the e2fsprogs libraries were installed with a prefix other than /usr, so that the header files were in some directory such as /usr/local/include, a program that used #include <lib/foo.h> would fail to compile. So change the pkg-config files to include both -I{$includedir} and -I{$includir}/lib. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 2012-05-14 20:45:54 +04:00			`Cflags: -I${includedir}/ext2fs -I${includedir}`
Add pkg-config files to e2fsprogs's libraries. 2005-01-26 20:59:25 +03:00			`Libs: -L${libdir} -lext2fs`