Re: help cross compiling again

[Tor Lillqvist <tml iki fi>]

Usually the corrent thing when replying to a message sent to a mailing
list is not to reply personally to the sender, unless your message
really *is* strictly personal.

I am not replying to your messages in order to give you technical
support person-to-person. The point is that messages to the list might
benefit others, too, and get archived. Adding back gtk-app-devel-list.

Marcelo Armengot writes:
> > -Ic:/devel/target/gtk+-2.10.7/include/gtk-2.0 
> > -Ic:/devel/target/gtk+-2.10.7/lib/gtk-2.0/include 
> > -Ic:/devel/target/atk-1.12.3/include/atk-1.0 

I write: 
> > You didn't edit the .pc files as I told you some mails ago...

Marcelo Armengot writes:
> Yes, I created a symbolic link from /devel/target to
> /op/cross-tools/mingw...

Eeek! Please note the "c:" part in the pkg-config output. Note that
the colon is in no way special on Linux. The -I options above do *not*
refer to absolute (Unix) paths. You can't get away with adding just
one symbolic link from /devel/target. The -I options, on Unix, do
*not* refer to an (absolute) pathname /devel/target, but what on Unix
would be a *relative* pathname c:/devel/target.

If you still insist on not editing the .pc files, you will need to
create a subfolder c:/devel and the symbolic link c:/devel/target in
every folder where you cross-build, including the .libs subfolders
that libtool might be using. Sounds extremely silly to me. 

And do you really have gtk+-2.10.7 and atk-1.12.3 (etc) folders under
/opt/cross-tools/mingw? That's a bit unusual, do you really want to
have different folders for each version?

In fact, after reading your message, I think I should change from
using a regular and predictable prefix
(c:/devel/target/$MODULE-$VERSION) in my win32 package builds to
something more random, in order to hint people even more strongly that
they are *not* supposed to actually have such paths on their machines.

--tml