[wx-dev] Making a Mac PKG for wxWidgets

[Anders F Björklund]

Vadim Zeitlin wrote:

> AFB> By hand, using the configure scripts and Apple PackageMaker.
> AFB> That is, I took the /usr/local install and rebundled it...
>
>  I hoped to have a script/makefile rule to be able to do it 
> automatically,
> it's not really practical to do it by hand.

It's getting there, the PackageMaker.app is scriptable too - if you 
generate
all the little XML files and all the other little handholding that it 
needs.

Ditto for generating disk images, and that it is done by the "hdiutil" 
tool.
(my "rpm2pkg" program uses both of these to automate the RPM->DMG 
process)

>  Sorry, I should have written install_name_tool instead of otool. But 
> what
> I really meant is that you can't use exactly the same package as a
> standalone framework and a private one and your reply seems to confirm 
> it,
> or am I missing something again?

It will use the traditional framework paths after the one coded into it,
that is if it can't find it in the @executable_path/../Frameworks 
path...
I believe the same thing goes for the dynamic libraries too, first 
search
the absolute path that it's linked to - then search the 
DYLD_LIBRARY_PATH.

Moral of the story is to always name them with @executable_path, I 
guess ?
(For instance SDL.framework also uses a @executable_path/../Frameworks 
path)

>  I think having a framework that you can just drop somewhere on your 
> system
> is the thing which counts, i.e. I believe most Mac people would be
> comfortable with DMG. PKG doesn't really add much.

Nope, we can save that for accessing the /usr instead - if even wanted.

Most "Mac people" would probably prefer Xcode templates or a ReadMe.rtf
rather than just using the wx-config, but that can come (much) later...

> AFB> That's probably a good idea. Any idea how one can add it there ?
>
>  Just configure --with-opengl

Yes, but that will generate a separate library. I meant in the core 
itself ?
There can only be one main library in a .framework, in any practical 
way...

> AFB> The only downside to adding it is that I think you need to add the
> AFB> AGL and OpenGL frameworks to your apps, or risk that pesky error
> AFB> about "indirectly included" libraries ? (but I might be wrong...)
>
>  Sorry, I don't really know what do you mean here?

If I add it to the core lib, and people link to that but not OpenGL,
then it might show link errors since the wx lib will use gl symbols.
And those symbols are "indirectly" referenced, by the wx framework ?

--anders