freeride-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [FR-devel] source browser


From: Hal E. Fulton
Subject: Re: [FR-devel] source browser
Date: Tue, 17 Sep 2002 03:50:35 -0500

----- Original Message -----
From: "Laurent Julliard" <address@hidden>
To: <address@hidden>
Sent: Tuesday, September 17, 2002 3:06 AM
Subject: Re: [FR-devel] source browser


> If you work on this I also suggest that you install the ripper
> extension in your Ruby tree. This is the first time we have to use a C
> based extension with FreeRIDE (ripper) and before we commit it in the
> FreeRIDE CVS repo I'd prefer that
>
> a) we validate that ripper works fine on both Linux and Windows
> b) we agree on where to put files in the CVS repo

Hmm, I thought ripper was pure Ruby. I guess I will
have to grab the C source and compile it? Or is this
bison output that is being compiled?

> For b) and based on the structure we have right now ripper.rb should
> go in freeride/redist and ripper.so should go in
> freeride/so/i686-linux for the Linux version and
> freeride/so/i686-mswin32 for the Windows version (mswin32).
>
> However given how Ruby organizes extensions I really wonder if we need
> to have a separate so/ directory or if i686-linux/ and i686-mswin32/
> directories should not simply be located under redist. What do you think ?
>
> In any case the run.bat needs to be modified to include a platform
> specific include path based on the RUBY_PLATFORM constant.

I have no idea how it should be structured.
Rich, Curt?


Hal







reply via email to

[Prev in Thread] Current Thread [Next in Thread]