mingw-cross-env-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] pg_config question


From: Tony Theodore
Subject: Re: [Mingw-cross-env-list] pg_config question
Date: Sun, 21 Feb 2010 16:32:04 +1100

On 21 February 2010 13:28, Tony Theodore <address@hidden> wrote:
> On 21 February 2010 10:58, Volker Grabsch <address@hidden> wrote:
>> Mark Brand <address@hidden> schrieb:
>>> I'm just wondering if it shouldn't be installed as:
>>>
>>> usr/bin/i686-pc-mingw32-pg_config
>>>
>>> instead of
>>>
>>> usr/i686-pc-mingw32/bin/pg_config
>>>
>>> Or is there a reason for its current location?
>>
>> You're right. I fixed that:
>>
>> http://hg.savannah.gnu.org/hgweb/mingw-cross-env/rev/a0219f812af5
>
> I'm a little confused again, does this mean the other *-configs need
> to change also? The guidelines thread (*) suggests they should. I'm
> looking at sdl_mixer.mk to check my understanding.
>
> libmikmod-config should be moved to usr/bin with a prefix.
>
> sdl and smpeg have the --with-xxx-prefix option, so their respective
> -config scripts will not be found if they are moved. Would we move
> them and create a symlink, leave them where they are, or move them and
> pass the variable directly with SDL_CONFIG='$(TARGET)-sdl-config'. The
> latter seems to be the correct way.

So, I think I'm on the edge of understanding something.
Mingw-cross-env does something closer to the Canadian Cross (1) by
creating a pseudo system that then is the host for the final target.
This hidden "host" executes natively, but isn't actually part of the
native system or the target system. I think this is the source of most
of my confusion.

Tony

(1) http://www.airs.com/ian/configure/configure_6.html




reply via email to

[Prev in Thread] Current Thread [Next in Thread]