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

[Earnie B. <ea...@us...>]

Quoting Hin-Tak Leung <hin...@ya...>:

> Hi,
>
> So I e-mailed mingw-editor@ about the cross-compiler entry in the FAQ being
> out-dated and ended up joining. So I can think of adding/updating 3 entries:
>
> (1) the fact that the FAQ itself is out-dated and more information is to be
> found at the Wiki

The website itself is sorely out dated.  The Wiki FAQ _is_ currently 
the FAQ and the website needs to point to it.

> (2) about cross-compiler binaries - I know of two other places R and Wine
>  (www.r-project.org and www.winehq.org) which refers to link to some 
> binaries and probably a bit more on the x86 script.

I don't do cross builds so I'm not helpful here.

> (3) the location of cvs is not clear - some is on sourceforge but 
> out-of-date,
> some is on cygwin.org , and it is not mentioned on the web site.
>

Cygwin cvs is the storage for mingw-runtime and w32api, everything else 
MinGW or MSYS is in the SF cvs.  However, MinGW's cvs doesn't contain 
all the source for all the binaries delivered, for instance you will 
not find binutils or GCC; there is no point for it, they have CVS 
storage in their respective projects.  I chose to store the MSYS 
specific packages in CVS because their were changes specific to MSYS 
and I wanted to keep the history of the changes.

> So, anybody has any other FAQs? (such as (3) - I was told it has been 
> discussed
>  - but the whole point of an FAQ is one doesn't need to search, even if it is
> in the archive)

The FAQ could even point to an archive entry so I disagree slightly.  
The point of pasting Frequently Asked Questions in a FAQ page is so 
that you can say it has been asked before go read the answer here.

>
> 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 
> interests -

Not an interest for MinGW.

> involves tracking down a change between mingw 3.10 and 3.11 which triggers
> a bug in wine, and it is important to be able to swap versions of the
> cross tool in and out cleanly.

That has been discussed and fixed.

> 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=$RPM_INSTALL_ROOT" step and some slightly
> different config.

The prefix variable is lower case for all autoconf created configure 
scripts.  I'm not sure what you're hinting at is missing.  Are you 
thinking RPM packaging?  If so, we're not really interested.

Earnie Boyd
--
Please post responsibly:
* Use text posts instead of html; many list members just trash mail with html.
* Do not use multipart mime to send both text and html versions.
* Do not top post replies; post inline with the parts you are responding to.
* Trim the post replies; remove irrelevant information from the quoted 
article.
* Original posters:
  ** Provide small complete examples of the problem.
  ** Provide the full command that produced errors.
  ** Provide the versions of the software used.