Re: [Ekiga-devel-list] Cross-compiling ekiga for win32

[Michael Rickmann <mrickma gwdg de>]

Am Montag, den 29.06.2009, 14:19 +0200 schrieb Julien Puydt:
> Michael Rickmann a écrit :
> > <big snip>
> 
> I pushed all your changes in.
Thanks, I will test it as soon as possible. It should be ok, one never
knows.
> 
> There's something I don't get : why do you want to download ekiga if you 
> already have it on disk?
make tries to move the download if it finds it at the most probable
location:
ifeq ($(wildcard $(SRCDIR)/$(EKIGA_ARCHIVE)),)
ifneq ($(wildcard $(BUILDROOT)/../$(EKIGA_ARCHIVE)/.git),)
update-ekiga:
	echo --- Moving Ekiga master...
	$(MV) $(BUILDROOT)/../$(EKIGA_ARCHIVE) $(SRCDIR)
else
....
I and the Makefile are just used to have all sources in one subdir.

> Perhaps it's something you don't know about autotools : they allow 
> out-of-tree builds. You have your sources in $WHATEVER_DIR, but want to 
> build in $THIS_DIR :
> $ mkdir -p $THIS_DIR
> $ cd $THIS_DIR
> $ $WHATEVER_DIR/configure $CONFFLAGS
> $ make
> 
> This will build the usual program ; if in another console you do :
> $ ~/bin/setup_for_cross_compile
> $ mkdir -p $(THIS_DIR)_cross
> $ cd $(THIS_DIR)_cross
> $ $WHATEVER_DIR/configure $CROSS_CONFFLAGS
> $ make
> 
> Then the same sources will be built with very different options in 
> different directories.
> 
Now I remember, I used that when I was building the cross tools myself,
gcc uses that scheme.

> Hope this helps,
> 
It may come in the next revision of the Makefile for a couple of
sources. For those sources, which we are working on, copying the source
and building in tree was what the Makefile was providing for up to now,
but building from a separate git clone may be even easier.

> Snark
> _______________________________________________
Thanks
Michael