[Bug 281173] Mk/bsd.wx.mk: WXRC_CMD sets wrong value for x11-toolkits/wxgtk32

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 31 Aug 2024 18:40:11 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281173

            Bug ID: 281173
           Summary: Mk/bsd.wx.mk: WXRC_CMD sets wrong value for
                    x11-toolkits/wxgtk32
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Ports Framework
          Assignee: portmgr@FreeBSD.org
          Reporter: rhurlin@FreeBSD.org
                CC: ports-bugs@FreeBSD.org

Created attachment 253226
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253226&action=edit
Patch to fix WXRC_CMD for versions > 3.0

There are currently two versions of the wxWidgets in the ports, 3.0 and 3.2.
Both versions contain a wxrc binary for compiling binary resource files, which
is named differently in the versions:

#pkg info -l wx30-gtk3-3.0.5.1_5 wx32-gtk3-3.2.4_2  | grep wxrc
        /usr/local/bin/wxrc-gtk3u-3.0
        /usr/local/bin/wxrc-3.2


In Mk/bsd.wx.mk there is a logic to query the path and file name of the WX
compiler and pass it in WXRC_CMD. However, Mk/bsd.wx.mk only determines the
correct file for wx 3.0, for wx 3.2 the naming of the file is incorrect:

#cd databases/pgadmin3
#make -V WXRC_CMD
/usr/local/bin/wxrc-gtk3u-3.0

#cd cad/kicad-devel
#make -V WXRC_CMD
/usr/local/bin/wxrc-gtk3u-3.2

In the latter case, the correct designation should be /usr/local/bin/wxrc-3.2.

Attached is a patch for Mk/bsd.wx.mk, which returns the correct naming for wx
3.2.


It would actually be nice if this value were returned via wx-config. But even
this does not work as expected between the wx versions, so that it cannot be
used in Mk/bsd.wx.mk:

#wxgtk3u-3.0-config --utility=wxrc
[returns no value]

#wxgtk3u-3.2-config --utility=wxrc
/usr/local/bin/wxrc-3.2

-- 
You are receiving this mail because:
You are on the CC list for the bug.