so I will download Strawberry 32 bit this weekend and start from the beginningThe G::O::I build should then work for you, using the binaries you already have.
Just make sure you use those same binaries to build the Glib module (which is a pre-requisite for G::O::I). I was using a Glib module that had been built against different binaries - when I rebuilt Glib-1.301 against the same binaries most of my problems with G::O::I disappeared.
The only problem I now have (afaik) is that the typelib files are not being found by default, and I have to use the search_path option (mentioned near the beginning of the G::O::I docs) in order that they are found.
Of course, the test suites for both G::O::I and Gtk assume that the typelib files will be found ... and hence, the tests still fail for me.
When I find out how to properly handle these typelib files, I expect both G::O::I and Gtk3 to build, test, and install just fine.
BTW, when I build Glib-1.301, some of the tests fail. I just ignore those failures and install the module anyway.
Cheers,
Rob
Update: Found it:
set GI_TYPELIB_PATH=C:\usr\local\lib\girepository-1.0
Dunno why they have to keep that such a closely guarded secret.
Anyway, with that in place, G::O::I-0.020 builds, tests and installs fine.
*I* still have some issues because I pretty much need to rebuild Cairo against the same binaries that I used for G::O::I .... for the same reason that I needed to re-build Glib.
But
you should be right.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.