Hi, Long -

Sounds right - that's how I installed ferret on my WinXP system.

Jack

On May 20, 4:23 pm, "Long Nguyen" <[EMAIL PROTECTED]> wrote:
> You might need to download the Windows-specific version of the gem and
> install it manually:
>
> 1. Go tohttp://rubyforge.org/frs/?group_id=1028
> 2. Download 
> ferret-0.11.6-mswin32.gem<http://rubyforge.org/frs/download.php/34135/ferret-0.11.6-mswin32.gem>
> 3. Run
>     gem install ferret-0.11.6-mswin32.gem
>
> I'm guessing that this includes pre-compiled binaries in case you don't have
> a Windows SDK installed (which would include nmake, C compiler, development
> libraries and header files, etc.).
>
> I don't have a Windows setup to test this out.  Can any Windows users verify
> or correct these instructions?
>
> Long
>
> On Tue, May 20, 2008 at 1:29 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
>
>
>
>
>
> > Long,
> > Here is the message when I try to install the 'ferret' gem in Netbeans
> > 6.1;
> > ERROR:  Error installing ferret:
> >        ERROR: Failed to build gem native extension.
>
> > C:/Rails/ruby/bin/ruby.exe extconf.rb install ferret --no-rdoc --no-ri
> > --version > 0
>
> > nmake
> > 'nmake' is not recognized as an internal or external command,
> > operable program or batch file.
>
> > Gem files will remain installed in C:/Rails/ruby/lib/ruby/gems/1.8/
> > gems/ferret-0.11.6 for inspection.
> > Results logged to C:/Rails/ruby/lib/ruby/gems/1.8/gems/ferret-0.11.6/
> > ext/gem_make.out
> > When I go into the gem_make.out file it reads;
> > C:/Rails/ruby/bin/ruby.exe extconf.rb install ferret --no-rdoc --no-ri
> > --version > 0
>
> > nmake
> > 'nmake' is not recognized as an internal or external command,
> > operable program or batch file.
> > I am developing on a Windows XP sp2.
> > Thank you,
> > Kathleen
>
> > On May 20, 1:02 pm, "Long Nguyen" <[EMAIL PROTECTED]> wrote:
> > > What nmake errors are you getting with the ferret gem installation? You
> > > might have to go into the directory where the gem is being installed (the
> > > output should have the path) in order to get a build log.
>
> > > FYI, whenever possible we've included the gems/plug-ins that Insoshi
> > depends
> > > on under the vendor/ directory.  The exceptions are the gems that require
> > > some native platform build as part of the install.  Ferret is one of
> > those
> > > exceptions.  (acts_as_ferret depends on ferret but doesn't have a native
> > > build itself.)
>
> > > Long
>
> > > On Tue, May 20, 2008 at 11:04 AM, [EMAIL PROTECTED] <
> > [EMAIL PROTECTED]>
> > > wrote:
>
> > > > Michael,
> > > > Please forgive my not finding the link, it was there and I am on my
> > > > way!
> > > > I was able to perform the Git operation to retrieve your source code
> > > > thanks to a fine explanation on your part.
> > > > I am now trying to run the RAKE operation and stumble on this line;
> > > > rake aborted!
> > > > no such file to load -- ferret
> > > > I am developing in Netbeans 6.1 and observed two GEMS available to
> > > > download. One is a acts_as_ferret and the other is simply 'ferret'? I
> > > > was able to run and install the acts_as_ferret successfully and then
> > > > thought I'd try the 'ferret' which will not install do to an 'nmake'
> > > > error. I've gone to the \vendor\plugins\acts_as_ferret.doc and observe
> > > > that the 'require' statement should be loaded in the environment.rb
> > > > file of which I've done ex:require 'acts_as_ferret'. I still am unable
> > > > to get the RAKE to run?
> > > > Can you suggest a course of action?
> > > > Thank you,
> > > > Kathleen
>
> > > > On May 18, 11:12 am, "Michael Hartl" <[EMAIL PROTECTED]> wrote:
> > > > > Which link is dead?  The docs link itself?  It seems to work fine for
> > me.
>
> > > > > Michael
>
> > > > > On Sun, May 18, 2008 at 10:08 AM, [EMAIL PROTECTED]
>
> > > > > <[EMAIL PROTECTED]> wrote:
>
> > > > > > Long,
> > > > > > I went tohttp://docs.insoshi.comandfounda dead link. Is this the
> > > > > > one you meant to find the Git download?
> > > > > > Would you be so kind as to provide the link?
> > > > > > Kathleen
>
> > > > > > On May 17, 10:48 pm, "Long Nguyen" <[EMAIL PROTECTED]>
> > wrote:
> > > > > >> We don't have plans for an SVN repository.
>
> > > > > >> If you've already installed Git on your XP system, then you've
> > > > actually
> > > > > >> completed the hardest part of getting started. You should be able
> > to
> > > > follow
> > > > > >> our documentation (docs.insoshi.com) to clone the  Insoshi
> > repository
> > > > and
> > > > > >> get started with branching and working in your local repository.
>
> > > > > >> And use your local repository to get comfortable with Git.  You
> > really
> > > > can't
> > > > > >> do anything too horrible.
>
> > > > > >> If you have any questions, feel free to post them up to the group.
>
> > > > > >> On Sat, May 17, 2008 at 4:49 PM, [EMAIL PROTECTED] <
> > > > [EMAIL PROTECTED]>
> > > > > >> wrote:
>
> > > > > >> > I've honestly installed Git on my Windows XP machine but haven't
> > had
> > > > > >> > the courage to use it. I've developed a few projects using
> > > > TortoiseSVN
> > > > > >> > and will continue to use this until I have no other options.
> > > > > >> > Is there an SVN location where I might download and start
> > becoming
> > > > > >> > involved in this project?
> > > > > >> > Thank you,
> > > > > >> > Kathleen
>
> > > > > >> --
> > > > > >> Long Nguyen
> > > > > >> [EMAIL PROTECTED] Hide quoted text -
>
> > > > > - Show quoted text -
>
> > > --
> > > Long Nguyen
> > > [EMAIL PROTECTED] Hide quoted text -
>
> > > - Show quoted text -
>
> --
> Long Nguyen
> [EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
Insoshi developer site: http://dogfood.insoshi.com/
Insoshi documentation: http://docs.insoshi.com/

You received this message because you are subscribed to the Google
Groups "Insoshi" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/insoshi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to