Bug 781207 - papyrus-gtkmm does not compile on f16
Summary: papyrus-gtkmm does not compile on f16
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: papyrus
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-12 23:29 UTC by Ryan H. Lewis (rhl)
Modified: 2012-04-25 12:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-25 12:56:19 UTC
Type: ---

Attachments (Terms of Use)
Papyrus Compile Bugs (119.64 KB, application/octet-stream)
2012-01-12 23:29 UTC, Ryan H. Lewis (rhl) 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ryan H. Lewis (rhl) 2012-01-12 23:29:21 UTC 
Description of problem:
putting 
#include< papyrus-gtkmm.h> 
in a .cpp file causes it not compile.

Version-Release number of selected component (if applicable):
papyrus-0.13.3


How reproducible:
Always

Steps to Reproduce:
try to compile this program:

#include <papyrus-gtkmm.h>
int main(int argc, char *argv[]) { return 0; }

Actual results:
See attached papyrus-bug file

Expected results:
A compiled binary

Additional info:

I pulled the source for this library and compiled it. I am attempting to fix down some of the bugs: 
http://www.git.ryanlewis.net/cgit.cgi/libpapyrus
Comment 1 Ryan H. Lewis (rhl) 2012-01-12 23:29:55 UTC 
Created attachment 554953 [details]
Papyrus Compile Bugs
Comment 2 Ryan H. Lewis (rhl) 2012-01-13 00:15:45 UTC 
I made a few commits (see above link) which allow this code to compile now! However it seems to not actually work with the latest GTK:

Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported

I notice that the packages are now orphaned. I will try to email the developer to see what is going on here...
Note You need to log in before you can comment on or make changes to this bug.