FS#25590 - [seed] wrong reference to seed.h

Attached to Project: Arch Linux
Opened by bongo (bongo) - Monday, 15 August 2011, 20:39 GMT
Last edited by Allan McRae (Allan) - Saturday, 16 June 2012, 08:16 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ionut Biru (wonder)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
when using seed 3.0.0-1 by including <seed-module.h> a compilation error occurs.
/usr/include/seed-gtk3/seed-module.h:23:29: fatal error: ../libseed/seed.h: No such file or directory
changing the include in this line to "seed.h" fixes the problem, since the dir structure has changed obviously.


Additional info:
Package version: 3.0.0-1

Steps to reproduce:
install seed from extra;
include header in a c program
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 16 June 2012, 08:16 GMT
Reason for closing:  No response
Comment by Ionut Biru (wonder) - Monday, 15 August 2011, 20:48 GMT
what is your compilation command?

i guess you didn't used the right flags. just for record, you need to use pkg-config seed --cflags to get them
Comment by Jan de Groot (JGC) - Tuesday, 16 August 2011, 05:27 GMT
This is obviously an upstream bug in the seed-module.h includefile. The file includes "../libseed/seed.h", which is right when seed-module is still inside the source tarball. As there's no libseed directory in the installed package file, the seed.h file isn't found when seed-module.h is included.

Looking at documentation, seed-module.h is a public header that should be usable:
http://developer.gnome.org/seed/unstable/seed-Modules.html
Comment by Ionut Biru (wonder) - Tuesday, 16 August 2011, 07:54 GMT
is not yet fixed upstream and i didn't find any reports.

Can you please report it upstream at http://bugzilla.gnome.org and paste the link here?
Comment by Allan McRae (Allan) - Saturday, 28 April 2012, 15:33 GMT
Anyone report upstream? The issue is still present.

Loading...