| I certainly acknowledge that the autotools build system is not working;
that is why I am investigating SCons.
I also acknowledge that I originally suggested that you work in your own
area. Obviously, I now think that this was a mistake.
The question whether autotools works, or not, is however ENTIRELY
INDEPENDENT of where you keep your work. Consequently, the build system is
a red herring.
Most of the directory structure and code changes that have caused CVS to
diverge from your sources have to do with getting plugin opcodes loading
and running on Windows, and other code-related changes, anyway, not with
the build system.
You could continue to work in CVS and put your own makefiles (called
Makefile.jpff or Makefile.linux .win32 .darwin or something so they will
not be overwritten by autotools) into CVS.
How would you feel about merging your sources into CVS and putting your own
build system in place there as well? Then if scons or autotools or
something actually works, you can adopt it later.
Just as you have tried to accept changes, so have I tried to minimize the
impact of what I am doing - though it may not seem like it - by keeping the
directory structure you had established, consulting with you, and so on.
Original Message:
-----------------
From: John ffitch jpff@cs.bath.ac.uk
Date: Sat, 13 Mar 2004 16:34:15 +0000 (GMT)
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4311] RE: Further updates
On Sat, 13 Mar 2004, gogins@pipeline.com wrote:
> The problem is that by working in your own area and only making file
> releases of Csound 5 sources available, with no clear method of accepting
> contributions from others, you in effect become the only "real" Csound 5
> developer - whether this is your intention or not.
I object very deeply to this remark. I have been attempting to take
all the changes until doing so DESTROYED by tree. For example I jave
just attempted to get in sync on my other main machine (cage) and it
updates, and then autoreconf fails. So I have a choise of doing
nothing or making a working system. Which would you choose?
>
> The alternatives that I can see are:
>
> 1. You are indeed the only developer who does substantial work in Csound
5,
> and I move my work on Csound 5 to the Silence CVS repository in
> SourceForge, which branches the Csound 5 code base.
>
> 2. You set up _another_ shared source repository (i.e. non CVS) that you,
> I, and other developers can safely and conveniently use.
That is just repeating the mistakes of the past
>
> 3. You merge your sources into Csound 5 CVS, learn to use it safely, and
> work there along with myself and, I hope, other developers. I much prefer
> this alternative.
>
How? Your files do not compile. They do not even create a
./configure This is the case on 3 different machines with 3 differnt
operating systems.
> Which do you prefer? Or do you have another solution?
I would much prefer a return to a world before the configuration
tools, the need for which I have never seen.
I have managed to get almost back in step with 4.23 but I cannot even
see where the problems lie with csound5
I am not sure why it is I who has to find a solution!
==John ff
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ . |