[texworks] Call for Help: Mac builds

[Jonathan Kew]

On 6 Feb 2011, at 09:38, Bruno Voisin wrote:

> Le 5 févr. 2011 à 22:59, Bruno Voisin a écrit :
> 
>> You can try it by yourself at <https://files.me.com/bvoisin/44kjm2>.
> 
> Comparing this test build with the release build (0.3 r567), a striking difference is size: 75 MB for the release build, 4 MB for the test build.
> 
> It turns out the test build contains the bare minimum (the TeXworks binary TeXworks.app/Contents/MacOS/TeXworks and its icon),

(Just in case it's not obvious to everyone: this means it won't run "standalone", it requires the user to have Qt and other libs installed separately on their system. This is fine for the individual developer working on the program, but it's not suitable for general distribution.)

> whereas the release build contains much more:
> 
> TeXworks.app/Contents/Frameworks
> 
> drwxr-xr-x  4 bvoisin  staff      136 14 fév  2010 QtCore.framework
> drwxr-xr-x  4 bvoisin  staff      136 14 fév  2010 QtDBus.framework
> drwxr-xr-x  4 bvoisin  staff      136 14 fév  2010 QtGui.framework
> drwxr-xr-x  4 bvoisin  staff      136 14 fév  2010 QtNetwork.framework
> drwxr-xr-x  4 bvoisin  staff      136 14 fév  2010 QtOpenGL.framework
> drwxr-xr-x  4 bvoisin  staff      136 14 fév  2010 QtScript.framework
> drwxr-xr-x  4 bvoisin  staff      136 14 fév  2010 QtScriptTools.framework
> drwxr-xr-x  4 bvoisin  staff      136 14 fév  2010 QtXml.framework
> -rwxr-xr-x  1 bvoisin  staff  1068724 14 fév  2010 libfreetype.6.dylib
> -rwxr-xr-x  1 bvoisin  staff   658912 14 fév  2010 libhunspell-1.2.0.dylib
> -rwxr-xr-x  1 bvoisin  staff  1299472 14 fév  2010 libpoppler-qt4.3.dylib
> -rwxr-xr-x  1 bvoisin  staff  4526536 14 fév  2010 libpoppler.5.dylib
> 
> TeXworks.app/Contents/plugins
> 
> drwxr-xr-x  3 bvoisin  staff     102 14 fév  2010 accessible
> drwxr-xr-x  6 bvoisin  staff     204 14 fév  2010 codecs
> drwxr-xr-x  2 bvoisin  staff      68 14 fév  2010 designer
> drwxr-xr-x  4 bvoisin  staff     136 14 fév  2010 graphicssystems
> drwxr-xr-x  2 bvoisin  staff      68 14 fév  2010 iconengines
> drwxr-xr-x  7 bvoisin  staff     238 14 fév  2010 imageformats
> -rwxr-xr-x  1 bvoisin  staff  457400 14 fév  2010 libTWLuaPlugin.dylib
> -rwxr-xr-x  1 bvoisin  staff  164892 14 fév  2010 libTWPythonPlugin.dylib
> drwxr-xr-x  2 bvoisin  staff      68 14 fév  2010 phonon_backend
> drwxr-xr-x  3 bvoisin  staff     102 14 fév  2010 script
> drwxr-xr-x  2 bvoisin  staff      68 14 fév  2010 sqldrivers
> 
> TeXworks.app/Contents/poppler-data
> 
> -rw-r--r--   1 bvoisin  staff   1861 30 sep  2008 COPYING
> -rw-r--r--   1 bvoisin  staff  10359 30 sep  2008 Makefile
> -rw-r--r--   1 bvoisin  staff    919 30 sep  2008 README
> drwxr-xr-x   9 bvoisin  staff    306 30 sep  2008 cMap
> drwxr-xr-x   7 bvoisin  staff    238 30 sep  2008 cidToUnicode
> drwxr-xr-x   5 bvoisin  staff    170 30 sep  2008 nameToUnicode
> drwxr-xr-x  19 bvoisin  staff    646 30 sep  2008 unicodeMap
> 
> TeXworks.app/Contents/texworks-help
> 
> drwxr-xr-x  5 bvoisin  staff  170 10 sep  2009 TeXworks-manual
> 
> Whether this is the difference between a dynamic vs static build, or whether the files were put there manually by Jonathan, or how the compiler was told to put the files there at build time, I have no idea.

There's a Qt script called macdeployqt that deals with bundling the frameworks and dylibs into the application package, and editing the paths appropriately; it's documented somewhere on the Qt site.

The poppler-data and manual resources were copied into place by a local build script, IIRC.

JK