This one message has answers to questions/remarks from several mails.
On Tue, 2009-02-03 at 14:42 +0100, Vincent R. wrote:
> I feel a bit alone so Pedro if could take some time to give your opinion it
> would be great.
That's why I really want to put this in a public spot. Others will work
on/with this stuff if you give them a chance. That's part of the
"release early and often" philosophy.
My suggestion would be to add an "experimental" directory to the cegcc
svn, and add several directory trees to it :
experimental/src/gcc -> gcc from svn, to become gcc-4.4.0
experimental/src/binutils -> binutils-2.19
experimental/src/mingw -> mingw-64 I guess
experimental/src/build -> new build scripts
I would focus on getting arm-mingw32ce to work, not arm-cegcc .
In parallel, the current source tree can remain for a while.
On Tue, 2009-02-03 at 00:26 +0100, Vincent Torri wrote:
> 2) I've also read on the gcc main site that there is (will be) a
> support of plugins for gcc (finally, it stops being monolythic). Does
> it mean that the port of cegcc could use that plugin framework ?
It would depend on what the framework does. Too early to tell.
On Mon, 2009-02-02 at 23:48 +0100, Vincent R. wrote:
> On Mon, 02 Feb 2009 23:08:31 +0100, Danny Backx <danny.ba...@scarlet.be>
> wrote:
> > I'm inclined to put this work (based on the current gcc from their svn)
> > in our repository.
> Maybe you should wait some time we find a fix and with more testing ;-)
Actually I've asked this several times, with a couple of months between
the questions. The answer was always to wait for ... .
The current implementation of cegcc has been very successful. It's
getting very old though. We're spending time adding/fixing stuff which
is probably already done in the original code. So we're duplicating
efforts instead of helping to improve the original products.
Sometimes you have to stop doing that and move on.
Once more : is it the right time to start an experimental branch ?
Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel
