Re: [Mingw-cross-env-list] Question and Help

[Volker Grabsch]

Omar Andrés Zapata Mesa <address@hidden> schrieb:
>  I will work on this and I'll make a howto
When creating a howto, you might want to extend the existing tutorial

    http://mingw-cross-env.nongnu.org/#tutorial

with a new section:

    Step 5c: Cross compile your Project (CMake)

(I'd move the current Step 5c to 5d, and 5d to 5e.)

> and a cmake .find file,
> maybe you want put this contribution in your website and this will be my
> contribution to short-term.

Martin: Did you create some kind of .find file, too?

General questions:

Is there a good way to integrate such a file into Mingw-cross-env?
Or should we put it into the docs?
Or should we place it somewhere else and just link to it?
Or should we try to get it into the official CMake project?

> another thing is that we should standardize the path where to get the
> software installed by default, to write general cmake files.

I'm not a CMake expert at all, but I think a CMake file should
never depend on any absolute path. It should never make assumption
on where Mingw-cross-env is actually installed. Users are free to
install it into /opt/mingw/ as well as /home/foo/mingw-cross-env/.

Alternative suggestion: Is it possible to write it in a way that
it uses just one path, such as:

    cmake . -DCMAKE_FIND_ROOT_PATH=/MCE/usr/i686-pc-mingw32

That would solve the problem, too, wouldn't it?

Another possibility would be to check where i686-pc-mingw32-gcc
is installed. BTW, why can't we simply say:

    cmake . -DHOST=i686-pc-mingw32

and have cmake checking for ${HOST}-gcc and ${HOST}-pkg-config
in the ${PATH}?


Greets,

    Volker

-- 
Volker Grabsch
---<<(())>>---
Administrator
NotJustHosting GbR