Re: [avrdude-dev] minor updates for AUTHORS and configure.ac

[E. Weddington]

On 7 Jul 2004 at 16:22, Theodore A. Roth wrote:

> On Wed, 7 Jul 2004, E. Weddington wrote:
> 
>> > One can use the Cygwin environment (shell and programs) to build the
> > application. The application can be built in two separate ways:
> >
> > 1. One can "build for Cygwin", which implies that the resulting
> > application is linked to Cygwin DLLs.
> 
> This implies that $build == $host == '*-cygwin*'
> 
> > 2. One can "build for MinGW", which implies that the resulting
> > application is NOT linked to Cygwin DLLs and is completely a native
> > Win32 application. *Even though* we're using the Cygwin environment to
> > build it.
> 
> This implies $build == '*-cygwin*' and $host == '*-mingw32*', which is
> technically a cross compile then.
> 
> We should not even be using $target in configure.ac. We should be using
> $host instead. This was my mistake as I didn't quite understand the
> semantics of those (which changed from earlier versions of
> automake/autoconf).
> 
> >
> > The -mno-cygwin flag is the standard way of switching over to the
> > MinGW GCC compiler (that can come as a Cygwin package) and build and
> > link the application as a Win32 application. This flag is required if
> > we're going to be using the Win32 calls.
> 
> Again, this smells like a cross compile (as far as configure.ac is
> concerned).

I believe you're right on this. Technically it's a cross-compile.

> It should be up to the person doing the compiling if they wish wish to
> use the cygwin dll's or the native windows API. If you using cygwin to
> build for mingw32/native, you would then need to run configure giving
> both the build and the host args:
> 
>   ./configure --build=cygwin --host=mingw32 ...
> 
> Although, I'm not positive as to exactly what values should be given for
> --build and --host.
> 
> I assume that the -mno-cygwin is really only valid then if $build ==
> '*-cygwin' and $host does not.
> 

Hopefully this will help
>From what I have seen with building other packages, e.g. GCC, is they are 
configured as (from my own script):

----------------------
export CC="gcc -mno-cygwin"
export CXX="g++ -mno-cygwin"
../gcc-$version/configure \
    --prefix=$mixedinstalldir \
    --build=mingw32 \
    --host=mingw32 \
    --target=avr \
    --enable-languages=c,c++ \
    2>&1 | tee configure.log 
----------------------

Note that both the -mno-cygwin flag is required and the --build and --host 
configure flags are required. Perhaps this helps? I would certainly be fine if 
avrdude had to built in this manner to get the native Win32 app when using the 
Cygwin environment.

Eric