Re: [Nautilus-list] problems building from cvs

[Darin Adler <darin eazel com>]

on 4/22/01 3:30 PM, Ryan Muldoon at rpmuldoon students wisc edu wrote:

> I am having trouble with the autogen.sh script when I do a fresh
> checkout of nautilus from cvs.  I have the suggested versions of
> automake and autoconf, so I am not quite sure what is wrong.  Basically,
> what happens is that configure.in gets deleted somewhere during the
> execution of the script, so autoconf can't make a configure script.  As
> a result, automake can't run, and I don't have any Makefiles.  Is there
> a solution to this problem?  I'd imagine that it is something dumb and
> common that I am just not noticing.  I'd really appreciate some help, as
> doing this is kind of impeding my ability to test a patch I made.

There's no dumb common error I know of that leads to this problem. To help,
I'd need a bit more to go on than this high-level description.

> Also - is there something like eazel-hacking for general consumption?

Many folks outside Eazel use eazel-hacking, but I'm not sure you'd like it.
It has a lot of "opinions" about how you set up your system.

> I'd like to be able to try and mess around with working on Nautilus more
> often, especially as my semester is over in a few weeks.  But, I'd
> prefer to keep testing/source builds seperate from my "stable"

My solution to this problem is to work without a file manager, so I have no
"stable" version of Nautilus at all. Given how Nautilus uses CORBA, I think
this is the only practical solution. The two copies of Nautilus are not
going to stay out of each other's way.

    -- Darin