Re: [MinGW-dvlpr] FAQs and cross rpms, etc

[Michael G. <mg...@te...>]

> > (3) the location of cvs is not clear - some is on sourceforge but=20
> > out-of-date,
> > some is on cygwin.org , and it is not mentioned on the web site.
>=20
> Cygwin cvs is the storage for mingw-runtime and w32api, everything else=20
> MinGW or MSYS is in the SF cvs.  However, MinGW's cvs doesn't contain=20
> all the source for all the binaries delivered, for instance you will=20
> not find binutils or GCC; there is no point for it, they have CVS=20
> storage in their respective projects.  I chose to store the MSYS=20
> specific packages in CVS because their were changes specific to MSYS=20
> and I wanted to keep the history of the changes.

While I (kind of) know this for a long time I think a central place
with collected URLs of all repositories involved might be helpful,
especially since the stuff isn't located in a single repo and at
least one repo had been moved some time ago.
[at least I had once searched a repo and finally found it or so I
thought only to discover after having checked out that it isn't all
I was looking for -- the whole process was time consuming and
frustrating]

> > On a separate note, has anybody thought of providing rpm's for the
> > cross-tools? (it could be an FAQ as well.) That's one of my recent=20
> > interests -
>=20
> Not an interest for MinGW.

There is the recently considerably revamped set of scripts that
creates the crosstools which works very well. Not the same as RPMs but
IMO close (and from a developers POV with some benefits :)

> > involves tracking down a change between mingw 3.10 and 3.11 which trigg=
ers
> > a bug in wine, and it is important to be able to swap versions of the
> > cross tool in and out cleanly.
>=20
> That has been discussed and fixed.

I do have installed several versions of the crosstools on my machine
installed in parallel and do think that's superior to have to un/install
them via rpm.
[I have them in seperate dirs and use a symbolic link to choose the
version I'm currently using -- works like a charm]

> > I don't really like what the packaging
> > linked from wine-devel doc does (installing binaries first before
> > upgrading/building), and I am thinking of adapting the cross-script
> > for that purpose.adapting the cross script - what it is missing is
> > just an additional "make PREFIX=3D$RPM_INSTALL_ROOT" step and some slig=
htly
> > different config.

I'm not sure I understand this.
Care to explain (e.g. with an example as to what you wish to achieve) ?

Anyway, if you are looking for rpms, they aren't that difficult to
create though as I tried to explain above I'm not sure I'd prefer them
over the mechanism I'm using now. But you may try to convince me... ;-)

Best,
Michael
=2D-=20
 Vote against SPAM - see http://www.politik-digital.de/spam/
 Michael Gerdau       email: mg...@te...
 GPG-keys available on request or at public keyserver