You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by Boris Kolpackov <bo...@codesynthesis.com> on 2007/11/28 10:35:50 UTC
Removing autotools-generated files from the repository
Hi,
I would like to remove the automake and autoconf-generated files
from the trunk. The problem with keeping them in the repository
is that if one configures in the maintainer's mode (and that's
what most of the people checking out from the repository will
do) then the build blows unless you have the exact same version
of autotools as the one with which files in the repository were
generated. This means that you have to reconfigure against your
local version of autotools before you can proceed.
If there are not objections, then I will remove configure,
Makefile.in, etc.
Boris
--
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Removing autotools-generated files from the repository
Posted by Boris Kolpackov <bo...@codesynthesis.com>.
Hi Alberto,
Alberto Massari <am...@datadirect.com> writes:
> Ok, if this is the way it should work, let's do it...
Great. I agree with Ronald that it is quite easy to bootstrap
the checked-out source code on, say, a GNU/Linux box and then
copy it onto other machines that you need to test. It also
should be considerably faster than checking out the source
tree from SVN every time.
Also, to clear any confusion, the released source distributions
will be fully bootstrapped and contain all the necessary scripts.
Thanks,
Boris
--
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
RE: Removing autotools-generated files from the repository
Posted by Scott Cantor <ca...@osu.edu>.
> To support building on systems without auto* I usually include the
> generated files into the distribution. Thus a "make dist" on an automake
> supporting system, a copy of the tar and a "configure && make" on the
> critical system is sufficient.
Oh, right. We're talking about subversion, not the distribution. make dist
always includes all the generated files, that's all done automatically by
automake, minus a few files that I think you have to add to EXTRA_DIST.
I would add that the concerns about out of date autotools are pretty much
confined to old versions of an OS (as in circa 2002). Anything recent Linux
is plenty new enough, and anything you get for Solaris these days is also
fine.
-- Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Removing autotools-generated files from the repository
Posted by Alberto Massari <am...@datadirect.com>.
Ok, if this is the way it should work, let's do it...
Alberto
Ronald Lamprecht wrote:
> Hi,
>
> Scott Cantor wrote:
>>> if I get it right, these errors only appears when the maintainer
>>> mode is
>>> active
>>
>> Nope. You should never check in generated files, it's simply not how
>> it's
>> done. It causes constant problems with the scripts being out of date and
>> refusing to regenerate. It's a giant PITA on the few projects I have
>> to work
>> on that check in either configure or libtool.
>
> I do never checke in the generated files into the repository.
>
>>> (btw, what does this mode add to the build log?). Could we force
>>> a reconf when the mode is enabled? I fear that requiring automake to be
>>> installed on a system could cause headaches (at least to me) when
>>> testing the build on systems that don't have the full GNU stack
>>> installed.
>>
>> It never has for me.
>
> To support building on systems without auto* I usually include the
> generated files into the distribution. Thus a "make dist" on an
> automake supporting system, a copy of the tar and a "configure &&
> make" on the critical system is sufficient.
>
> Greets,
>
> Ronald
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: c-dev-help@xerces.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Removing autotools-generated files from the repository
Posted by Ronald Lamprecht <R....@T-Online.de>.
Hi,
Scott Cantor wrote:
>> if I get it right, these errors only appears when the maintainer mode is
>> active
>
> Nope. You should never check in generated files, it's simply not how it's
> done. It causes constant problems with the scripts being out of date and
> refusing to regenerate. It's a giant PITA on the few projects I have to work
> on that check in either configure or libtool.
I do never checke in the generated files into the repository.
>> (btw, what does this mode add to the build log?). Could we force
>> a reconf when the mode is enabled? I fear that requiring automake to be
>> installed on a system could cause headaches (at least to me) when
>> testing the build on systems that don't have the full GNU stack installed.
>
> It never has for me.
To support building on systems without auto* I usually include the
generated files into the distribution. Thus a "make dist" on an automake
supporting system, a copy of the tar and a "configure && make" on the
critical system is sufficient.
Greets,
Ronald
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
RE: Removing autotools-generated files from the repository
Posted by Scott Cantor <ca...@osu.edu>.
> if I get it right, these errors only appears when the maintainer mode is
> active
Nope. You should never check in generated files, it's simply not how it's
done. It causes constant problems with the scripts being out of date and
refusing to regenerate. It's a giant PITA on the few projects I have to work
on that check in either configure or libtool.
> (btw, what does this mode add to the build log?). Could we force
> a reconf when the mode is enabled? I fear that requiring automake to be
> installed on a system could cause headaches (at least to me) when
> testing the build on systems that don't have the full GNU stack installed.
It never has for me.
-- Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Removing autotools-generated files from the repository
Posted by Alberto Massari <am...@datadirect.com>.
Hi Boris,
if I get it right, these errors only appears when the maintainer mode is
active (btw, what does this mode add to the build log?). Could we force
a reconf when the mode is enabled? I fear that requiring automake to be
installed on a system could cause headaches (at least to me) when
testing the build on systems that don't have the full GNU stack installed.
Alberto
Boris Kolpackov wrote:
> Hi Alberto,
>
> Alberto Massari <am...@datadirect.com> writes:
>
>
>> there used to be problems with automake older than a certain version,
>> and having the preprocessed files helped working on the code even if the
>> developer didn't have that specific version (clearly, if he was not
>> touching the makefiles).
>> So, by removing the preprocessed files, we are putting even more
>> constraints on the developer's toolset (have automake, and have it
>> updated). What kind of errors do you find when using a different version
>> of automake?
>>
>
> They were some criptic automake errors that were gone once I
> regenerated configure, etc., by running the reconf script.
> They were caused by the version mispatch and the maintainers
> mode option.
>
> I think it is better to require a developer to have reasonable
> autotools version than to have the build process fail with some
> cryptic error message (no, it does not say "Hey, update your
> autotools and run reconf!" ;-)) and let the developer wonder
> what to do next.
>
> Plus it is a fairly common practice not to keep autotools-generated
> scripts in the repository, so I don't think it will surprise anybody.
>
> Boris
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Removing autotools-generated files from the repository
Posted by Boris Kolpackov <bo...@codesynthesis.com>.
Hi Alberto,
Alberto Massari <am...@datadirect.com> writes:
> there used to be problems with automake older than a certain version,
> and having the preprocessed files helped working on the code even if the
> developer didn't have that specific version (clearly, if he was not
> touching the makefiles).
> So, by removing the preprocessed files, we are putting even more
> constraints on the developer's toolset (have automake, and have it
> updated). What kind of errors do you find when using a different version
> of automake?
They were some criptic automake errors that were gone once I
regenerated configure, etc., by running the reconf script.
They were caused by the version mispatch and the maintainers
mode option.
I think it is better to require a developer to have reasonable
autotools version than to have the build process fail with some
cryptic error message (no, it does not say "Hey, update your
autotools and run reconf!" ;-)) and let the developer wonder
what to do next.
Plus it is a fairly common practice not to keep autotools-generated
scripts in the repository, so I don't think it will surprise anybody.
Boris
--
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: Removing autotools-generated files from the repository
Posted by Alberto Massari <am...@datadirect.com>.
Boris,
there used to be problems with automake older than a certain version,
and having the preprocessed files helped working on the code even if the
developer didn't have that specific version (clearly, if he was not
touching the makefiles).
So, by removing the preprocessed files, we are putting even more
constraints on the developer's toolset (have automake, and have it
updated). What kind of errors do you find when using a different version
of automake?
Alberto
Boris Kolpackov wrote:
> Hi,
>
> I would like to remove the automake and autoconf-generated files
> from the trunk. The problem with keeping them in the repository
> is that if one configures in the maintainer's mode (and that's
> what most of the people checking out from the repository will
> do) then the build blows unless you have the exact same version
> of autotools as the one with which files in the repository were
> generated. This means that you have to reconfigure against your
> local version of autotools before you can proceed.
>
> If there are not objections, then I will remove configure,
> Makefile.in, etc.
>
> Boris
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org