RE: [Madwifi-users] Compilation out-of-box on 3 platforms

[Pavel R. <pr...@gn...>]

Hello, Dustin!

On Thu, 2005-11-03 at 10:41 -0800, Dustin McIntire wrote:

> Thanks for the cross compile fix. The build change to use the CROSS_COMPILE
> argument works well for the kernel modules compilation.  I still need to
> define TOOLSPREFIX to build the madwifi tools however.  The CROSS_COMPILE
> argument doesn't get picked up during the tools build.

Correct, I'm confirming it.

> When I do a 'make
> all', which includes the tools directory, the TOOLSPREFIX argument is using
> the default value from the hal directory rather than the CROSS_COMPILE
> argument (logical since it is not a kernel build).

I don't see that.  tools/Makefile doesn't include any makefiles.  It can
only take TOOLSPREFIX from the command line or the environment.

What I could do would be to set TOOLSPREFIX to $(CROSS_COMPILE) in
tools/Makefile.  P.S. I'm applying it.  Thanks!

>   It's not a major issue,
> but I wanted to let you know that TOOLSPREFIX still needs to be defined in
> order to make the complete SW suite.

Since we have touched this topic, let me explain the motivation behind
the changes.

The main reason to redefine TOOLSPREFIX was to reduce dependency on the
Atheros *.inc files.  After my changes to x86_64-elf.inc were reverted
twice in a few days (first by creation of madwifi-ng, then in revision
1260) it became clear to me that the only way to win this
commit-and-revert battle was by a workaround.

My first approach was to set TOOLPREFIX to "", but it looked funky with
V=1, so I wanted to set TOOLPREFIX to $(EMPTY).  But then I realized
that $(CROSS_COMPILE) would be a more meaningful choice.

Ideally, the hal/public/*.inc files should be ignored and TARGET should
be set based on the contents of the Linux .config file (or maybe on
kernel CFLAGS).  But that would be quite a lot of work to verify it for
various ARM systems, so I'm not sure I'll be able to do it soon.

-- 
Regards,
Pavel Roskin