Waf does not honour pkg-config settings when cross-compiling

Bug #1188587 reported by Paweł Forysiuk
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Midori Web Browser
Won't Fix

Bug Description

When cross compiling prefixed pkg-config program should be used for example i686-w64-mingw32-pkg-config when compiling for 32 bits. Waf does not honour this setting by implicitly using native version of pkg-config

114: wscript
    conf.check_tool ('vala')

in .waf-1.5.19-d046dea57dbefcabd071866ac51eb518/wafadmin/Tools/vala.py
call pkg-config implicitly when checking for gobject and gthread
thus prepending native paths to includes, which in turn breaks the build.

Current workaround is to user PKG_CONFIG_LIBDIR env variable which is honoured with internal check vala tool.

Proper way is to use prefixed pkg-config everywhere.

Tags: win32 waf
Revision history for this message
Paweł Forysiuk (tuxator) wrote :
Revision history for this message
Paweł Forysiuk (tuxator) wrote :

Attached patch is WIP (assumes cross compilation) and does not fix the issue with internal checks

Changed in midori:
status: New → Confirmed
Revision history for this message
Cris Dywan (kalikiana) wrote :

This is essentially obsolete - we'll do whatever's needed with cmake now.

Changed in midori:
status: Confirmed → Won't Fix
tags: added: waf
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.