On Wed, Apr 11, 2012 at 12:02:11PM -0400, Daniel Johnson wrote:
> On Apr 11, 2012, at 11:04 AM, Daniel Macks wrote:
>
> > Isn't the actual only difference between "framework" and "library" the
> > difference between using -F/-framework vs -L/-l flags when linking? And the
> > binary library ins
On Apr 11, 2012, at 11:04 AM, Daniel Macks wrote:
> Isn't the actual only difference between "framework" and "library" the
> difference between using -F/-framework vs -L/-l flags when linking? And the
> binary library inside .framework is really just a .dylib by a different
> filenaming scheme
On Wed, Apr 11, 2012 at 11:04:05AM -0400, Daniel Macks wrote:
> Isn't the actual only difference between "framework" and "library" the
> difference between using -F/-framework vs -L/-l flags when linking? And
> the binary library inside .framework is really just a .dylib by a
> different file
Isn't the actual only difference between "framework" and "library" the
difference between using -F/-framework vs -L/-l flags when linking? And
the binary library inside .framework is really just a .dylib by a
different filenaming scheme. I can't envision any way that the linker
flags or filenam
Daniel and Daniel,
While creating test packaging for a wxcocoa923-py package for use
with relax-py, I discovered that the cocoa build of wxPython 9.2.3.1
issues an error message, when running its demos, that access to the
screen requires a framework build of python for the cocoa support.
Since Ma
