[MacPorts] #19583: py26-wxpython wrongfully decides to build himself universal

[MacPorts]

#19583: py26-wxpython wrongfully decides to build himself universal
---------------------------------+------------------------------------------
  Reporter:  vince@…             |       Owner:  macports-tickets@…                   
      Type:  defect              |      Status:  closed                               
  Priority:  Normal              |   Milestone:                                       
 Component:  ports               |     Version:  1.7.1                                
Resolution:  fixed               |    Keywords:                                       
      Port:  py26-wxpython       |  
---------------------------------+------------------------------------------

Old description:

> Ok, gotcha. Sorry for the noise.

New description:

 While wxwidgets is not universal (yet), because of dependencies on Carbon
 and Quicktime, py26-wxpython, when compiled on a universal python 2.6
 environnement, tries to build himself universal, probably because it picks
 up the flags used for python 2.6 compiling during setup. Consequency: it
 fails miserably here:

 {{{
 src/mac/_gdi_wrap.cpp: In function 'PyObject*
 _wrap_Font_MacGetATSUFontID(PyObject*, PyObject*)':
 src/mac/_gdi_wrap.cpp:15883: error: 'class wxFont' has no member named
 'MacGetATSUFontID'
 }}}

 because in the definition of the wxFont class, we read:

 {{{
 #ifndef __LP64__
     // 'old' Quickdraw accessors
     short MacGetFontNum() const;
     short MacGetFontSize() const;
     wxByte  MacGetFontStyle() const;

     // 'new' ATSUI accessors
     wxUint32 MacGetATSUFontID() const;
     wxUint32 MacGetATSUAdditionalQDStyles() const;
     wxUint16 MacGetThemeFontID() const ;

     // Returns an ATSUStyle not ATSUStyle*
     void* MacGetATSUStyle() const ;
 #else
     const void * MacGetCTFont() const;
     // soon to be removed for 64bit, Returns an ATSUStyle not ATSUStyle*
     void* MacGetATSUStyle() const ;
 #endif
 }}}

 the wxFont class not being the same on 32 and 64-bit mode.

 Any idea to patch this up?

--

Comment(by ryandesign@…):

 I'm setting the ticket description back to what it originally was and
 moving your note into [comment:3 your comment above].

 I'm not sure though from the text in this ticket what the resolution to
 this issue turned out to be.

-- 
Ticket URL: <http://trac.macports.org/ticket/19583#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS