Building for release on OS X/Intel

Using the jbk (Jean Krohn) account on the osx-intel-build machine (see ProductionTestingHardware).

Building Openlibraries

Open a new terminal.

# Go to the local repository
$ cd /Users/jbk/src/openlibraries-cvs

# Update the local repository to latest
$ cvs update -r stable-release-2007_10_11

# cleaning before building
$ make distclean
$ cd src
$ make distclean
$ cd ..

# (may take a while)
$ ./bootstrap

# needed so that the configure will be able to find libtiff and libjpeg
$ export LD_LIBRARY_PATH=/opt/local/lib

$ ./configure --prefix=/opt/local --with-boostprefix=/opt/local --enable-openalframework --with-pythonversion=2.4
--with-glewprefix=/opt/local --with-qtinclude=/Developer/qt/include --with-qtlib=/Developer/qt/lib --disable-gpl
--disable-mlt --disable-cg --disable-ofx

# build. This may fail, in which case just verify that the error is in 'test', no 'src'.
make

# install openlibraries in /opt/local (will ask for the user password).
# This may fail as well in test (not a problem).
sudo make install

Building Jahwidgets

Open a new terminal.

$ cd /Users/jbk/src/jah-cvs

# update the local Jah repository to latest.
# In case of problem, make sure that CVS properly got jahwidgets, jahtools and installer.
# If cvs gets stuck in resources, Ctrl+C it...
$ cvs update 

$ cd jahwidgets

# cleaning before building
$ make clean

• verify that in src/qt3/config.pri, the variable CONFIG contains 'release', and not 'debug'

# build
$ make

Building Cinecode v1

Open a new terminal.

# set up some environment variables
$ . cinecode_env

# go to the local cinecode v1 repository
$ cd cinecode-v1

# update the local repository
$ svn update

Read CinecodeReleaseFixes and apply to cinecode.py

# build the theme
$ cd theme
$ make clean
$ qmake && make
$ cd ..

# build and package the app. The argument (e.g. 1.0.0, 2.0.0 or 3.1.4) is the version used for the packaging.
# This command will first ask for a password ('cinecode') to create the cinecode.car file.
# And will then ask whether to overwrite the setup.py file, twice (accept in both cases).
# If this fails, try again.
$ ./create_app 1.0.0

You should now have a cinecode_i386_1.0.0.dmg file in the current directory (/Users/jbk/cinecode-v1), which is your cinecode package.

Building Cinecode v2

The process is the same as for Cinecode v1, just replacing cinecode-v1 by cinecode-v2 and giving an other, appropriate version parameter to ./create_app .