[Dev] I just had an aha! moment dealing with the RunChandler issue

[Mike Taylor]

I found out that the pythonw binary is actually nothing more than a script file in the Python 2.4 framework and when I saw that I just knew it had to be doable. So I went back to basics and compared what the pythonw was doing and our RunChandler was within a make install setup and found they were identical.

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
[EMAIL PROTECTED]
http://www.osafoundation.org

[EMAIL PROTECTED]
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29

That got me thinking that maybe the issue was simple and that while hunting for the solution down the other path I was hiding this solution so as a quick sanity test I hardcoded the path in RunChandler. After tracking down the import and file not found errors, I came to the realization that our dmg install manifest copies the Framework files into the locations required for an Application Bundle (the .app part) but does not fully copy the Framework files in the Resources/Library/ directory - it's mostly empty. After doing a quick test by copying the Framework files into the .app directory structure I was able to do ./release/RunChandler and it worked! Now I just need to muck around and find out if I can use a symlink (to avoid having duplicate files) or something similiar.

PGP.sig
Description: This is a digitally signed message part

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev