On 6/2/06, John Whitley <[EMAIL PROTECTED]> wrote:
> Oleg Kourapov wrote:
> >>> The package is ready but it suffers from installation issues which I
> >>> reported to Alex as early as April or March but he hasn't still sent
> >>> me any fixes. If anyone else is willing to help me bring Instiki
> >>> 0.11
> >>> to OS X users, I'll report those issues immediately for their
> >>> review.
>
> I can help out with this, too.

Thanks!

> > Clean install of Instiki 0.11 w/ruby 1.8.4 (bundled in my app) gives
> > me the  "undefined method `files_path' for nil:NilClass" error, which
> > has been previously mentioned on this list already. Recommendations
> > were to install SWIG package and my question is to help me confirm
> > this and (if this is indeed the case) bundle SWIG with Instiki package
> > for Mac OS X. Another hint I could take is how to make all this
> > (Instiki.app + ruby + swig) into a Universal Binary.
>
> To reiterate: the error "undefined method `files_path' for
> nil:NilClass" is ActiveRecord complaining, ultimately because the DB-
> backend (in this case sqlite3) is broken.

I see. I've screwed up myself a bit by keeping essentially 2 versions
of Instiki 0.11 on my Mac - one is an upgrade of 0.10.2 and another
one is a straight build of my Xcode project. Upgraded one works ok (it
uses my system-wide ruby with sqllite module built with SWIG) but the
build suffers from this 'files_path' issue because it uses a
self-contained ruby package.

> SWIG is definitely required for sqlite3 on OS X.  I've even filed a
> bug against DarwinPorts for the missing depends on the rb-sqlite3
> port on this very topic...
>
> Let me know if you have success with adding SWIG; I'll look into what
> we can do to offer Universal Binary support.  It would help if you
> can outline your current packaging steps.  For example, do you custom
> build all of the required executables and libraries?  Or can you just
> copy over from a third-party installation such as DarwinPorts?

As mentioned above I had success adding SWIG, just didn't realize it
was required for every build (really stupid of me) and de-installed it
after first successful compilation. I'll try to include it into
Instiki.app as well. As for the second question, I copy all custom
pre-built executables and libraries from a separate directory during
the packaging process in my Xcode project.

-- 
Oleg "2sheds" Kourapov
mailto:[EMAIL PROTECTED]
http://www.2sheds.ru
_______________________________________________
Instiki-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/instiki-users

Reply via email to