[gentoo-amd64] Re: Cross compiler for Windows

[Duncan]

Mansour Al Akeel posted on Mon, 17 Aug 2009 19:54:49 -0300 as excerpted:

> I am trying but, I can not find any complete documentation for windows.
> I haven't used overlays before, and it looks like there's a need to use
> it. I am following http://en.gentoo-wiki.com/wiki/Crossdev and when I
> use the layman overlay, I need to create make.conf for that overlay ??
> What do I put in that make.conf. It's going to be for windows !!

As with Paul, I've never done the MS Windows compilation thing (I don't 
do proprietary at all, as I refuse to accept responsibility in the form 
of a liability waiver for a "black box" I can't inspect the contents of; 
since nearly all software freedomware and servantware alike disclaims 
liability, that means I don't run servantware/proprietaryware at all... 
unless of course someone else agreed to take that liability... and of 
course the fact that someone wants to deprive me of my four freedoms when 
running their software doesn't help either), however...

I HAVE used overlays and layman.  You really should read the layman 
manpage, as it gives all the details and there's really no replacement 
for reading the documentation.

However, layman really doesn't use a whole new make.conf.  It just sets 
one variable in a file which should be chained onto your normal make.conf 
using the source directive.

IOW, assuming you've left the make_conf: setting in /etc/layman/
layman.cfg at its default (%(storage)s/make.conf, where storage is /usr/
portage/local/layman, making the make_conf setting really /usr/portage/
local/layman/make.conf), you then add the following to the bottom of your 
normal /etc/make.conf to chain layman's make.conf to it:

source /usr/portage/local/layman/make.conf

Layman's make.conf you won't edit directly.  Layman will do that 
automatically when you add overlays using the layman --add <overlay> 
command, or delete them using layman --delete <overlay>.

As I said, while the file is still called make.conf by default, it's 
really not a a whole new make.conf.  All it sets is the single 
PORTDIR_OVERLAY variable, no others, and you don't even need to worry 
about that as it handles it automatically during normal layman 
operation.  It's not a whole make.conf on its own, nor does it act as 
one, as it's entirely ignored unless you add the appropriate source 
directive to the end of your normal make.conf, which simply tells portage 
to include this second file as if it were part of the first.

But read the manpage, particularly (for this aspect) the 
"Handling /etc/make.conf" section, which explains it.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman