Ok, this is getting a little too complicated for me.
Bottom line: Does it even make sense to write a script that after
compilation creates a dir named wxLua.framework, copies all the bits,
and create the links? Basically, we rewrite copydylibs.command to make
this dir structure, similar to wxLua-2.4.1-tiger.dmg, but following
the Framework dirs. Then... we have to worry about how and where to
install it and the apps.
If mimicking a Framework dir structure makes sense could you suggest a
structure you think would be good? I get the impression that the
full-blown framework not what you think is right, but how about a
pseudo-framework like dir structure that wraps everything, includes,
libs, apps and the installer creates links to parts within it.
If not, that's fine and copydylibs.command can be updated and we'll
stick with the dir structure of wxLua-2.4.1-tiger.dmg.
Regards,
John
ps. I responded to some things below, but it seems like there's too
many little bits and the real question is simply "wxLua-2.4.1-tiger
structure or some new dir structure?"
On Jan 19, 2008 2:56 PM, Anders F Björklund <[EMAIL PROTECTED]> wrote:
> John Labenski wrote:
> > I have to look into the universal build, I think there's something on
> > the wxWiki?
>
> I have no idea, have my stuff at http://www.algonet.se/~afb/wx/
Thanks, I'll check it out.
> > Someone mentioned python's Framework method which looks very useful,
> > but I cannot find any description of what a Framework is besides how
> > to create one using XCode. Is there a specification for it outside of
> > using XCode?
>
> There should be some system docs like "anatomy of a bundle" etc
> http://developer.apple.com/documentation/CoreFoundation/Conceptual/
> CFBundles
>
> > Could it more easily solve the copydylibs.command problem of how to
> > make the wxLua libs accessible?
>
> Using dylibs isn't really a problem, more of a design decision.
You mean dir design right?
I am under the impression that the dir structure of
wxLua-2.4.1-tiger.dmg is non-standard, but to me it looks a little bit
like a Framework and if we just move things around inside we can just
call it a framework.
> Both wxWidgets and wxLua could be made to use framework bundles
> instead, but so far it hasn't been worth the hassle of doing so
> (in addition, having it conform more to one specific platform
> doesn't really fit into the cross-platformness of wx - IMHO)
>
> Like
> http://wiki.gnustep.org/index.php/
> User_FAQ#Why_not_use_framework_bundles.3F
Well, I use the term Framework loosely, I guess I'm seeing it as a way
to package up a lot of files in a single dir in some semi-standard
way.
I don't know if we care that the binary wxLua packages are different
in MSW, Linux, and OSX? Ideally we have an installer for MSW (or just
a zip of *.exe, docs, and samples), Linux has rpms or debian/Ubuntu
packages, and OSX has ??? and that's what's unclear to me.
> > When we install we create
> >
> > /System/Library/Frameworks/wxLua.framework/Versions/
> > ./Current -> 2.8.7
> > ./2.8.7/
> > ./bin/ : has lua executable
>
> Not sure if you actually need this ? If you do, it goes in "Tools".
>
> > ./include/wxlua2.8.7 : has wxLua's headers
>
> This should go in "Headers", with versioning provided by "Versions".
>
> > ./lib/wxlua2.8.7 : has wxLua's libs
>
> This should go in "wxLua", so must be one monolithic shared library.
>
> > ./apps/ : has wxLua.app and others
>
> I think the applications should go outside of the framework bundle.
>
> > ./docs/
To be more clear, the wxLua.framework will be just like
/System/Library/Frameworks/Python.framework or some other framework
(maybe you know another?) that makes sense.
> Again, not sure if needed. Usually provided outside of frameworks,
> but I suppose you could put some docs in there for Xcode browser.
>
> > Then add links from /$prefix/include, /$prefix/lib, and I guess
> > /Applications/wxLua.app to wxLua.framework/.../apps/wxLua.app.
Like python does, these links are where we get Unix-like compatibility
from our Framework package.
> > 1) Do we provide yes/no options for putting it into /Applications?
>
> They can also go into ~/Applications, if not having admin privileges
>
> > 2) Do we provide yes/no option for putting it into
> > /System/Library/Frameworks?
>
> This should be /Library/Frameworks, but could also be ~/Library too.
>
> > 3) Look at /Applications/iPhoto/Contents/Frameworks, since we have a
> > few apps do we instead put a link in the app to the framework?
> > wxLua.app/Contents/Frameworks/wxLua.framework -> some good place
> > to put wxLua.framework. This is as opposed to putting the apps into
> > the wxLua.framework as above.
>
> If you put the framework in a central location, then it doesn't have
> to be bundled with each and every application... Same goes for wxMac.
> So instead of the symlink in Frameworks, you don't have to do anything.
> Normally, it will then find it along the regular framework search path.
>
> Applications / wxLua.app -> Frameworks / wxLua.framework -> wxWidgets
>
> Note that the name of the framework dictates the name of the includes,
> so if you use "wxLua.framework" you need to include <wxLua/wxlua.h>
> For instance OpenGL is normally in a directory "GL", but on the mac
> it's in a framework so all gl programs must change to <OpenGL/gl.h>
This is bad, but if we have the wxLua.framework/2.8.7/include/ and
also install to $prefix/include/wxlua2.8.7 people can use that as they
would for python.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
wxlua-users mailing list
wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
