#77 MacCinePaint-native fails on Tiger

[Kai-Uwe Behrmann]

reportedly MacCinePaint's native gtk-osx build
does not run on mac os X Tiger.
As I dont have access to Tiger it is open how to deal with.

[David Burnett]

Logged In: YES
user_id=5758

It appears to be a clash of libJPEG's. The Console gives this error

/Applications/CinePaint.app/Contents/MacOS/cinepaint
dyld: Symbol not found: __cg_jpeg_resync_to_restart
Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
Expected in: /Applications/CinePaint.app/Contents/Resources/lib/libJPEG.dylib

/Applications/CinePaint.app/Contents/MacOS/cinepaint: line 19: 294 Trace/BPT trap $binpath/$exe $@

One way to solve this on Tiger is use DYLD_FALLBACK_FRAMEWORK_PATH and DYLD_FALLBACK_LIBRARY_PATH
instead of DYLD_LIBRARY_PATH, it may work on Panther too.

A quick modification to the script gives...

#!/bin/bash

TOP=/usr/local

cd $HOME

exe=cinepaint
echo $0
path="${0%/*}"
export RESOURCESPATH="${path%/*}/Resources"
binpath="$RESOURCESPATH$TOP/bin"
export DYLD_FALLBACK_LIBRARY_PATH="$RESOURCESPATH/lib:$RESOURCESPATH$TOP/lib":$DYLD_FALLBACK_LIBRARY_PATH
test -z $DYLD_FALLBACK_FRAMEWORK_PATH && \ export DYLD_FALLBACK_FRAMEWORK_PATH="${path%/*}/Frameworks" ||
export DYLD_FALLBACK_FRAMEWORK_PATH="${path%/*}/Frameworks:$DYLD_FALLBACK_LIBRARY_PATH"
export PATH=$binpath:$RESOURCESPATH/bin:$PATH:$TOP/bin
#set >> /tmp/test.txt
#echo $@ >> /tmp/test.txt
$binpath/$exe $@

There should probably be a test -z on both FALLBACK env variables...

[Kai-Uwe Behrmann]

Logged In: YES
user_id=634841

To make usage of the suggested CinePaint start script
copy it to CinePaint.app/Contents/MacOS/cinepaint.
Dont forget to set the script executeable:
chmod 0755 CinePaint.app/Contents/MacOS/cinepaint
. Report if it works to eighter the CinePaint email list,
here or me personally [ku point b at gmx point de].

[Kai-Uwe Behrmann]

cinepaint startup script v1.1

[Kai-Uwe Behrmann]

Logged In: YES
user_id=634841
Originator: YES

Fixed with release 0.21-2.1. This release includes just the proposed changes.