Re: [Ekiga-devel-list] testing a modied ekiga at another machine

[Vineet Menon <mvineetmenon gmail com>]

So, there isn't a way to just "compile at one end-execute at another end" approach for what I am doing?

Regards,

Vineet Menon

On 12 March 2012 17:03, Chris Vine <chris cvine freeserve co uk> wrote:

On Mon, 12 Mar 2012 16:34:06 +0530
Vineet Menon <mvineetmenon gmail com> wrote:
> Okay..I guess u got me wrong!!
> So, lemme say that again,
> What i was doing was this,
>
> ON MAIN MACHINE
> *******for ptlib***********
> ./configure
> make
> make install
>
> *****for opal*****
> ./configure
> make
> make install
> ****** for ekiga******
> ./configure
> make
> make install
>
> ON REMOTE MACHINE
>
> *****copy files entirely including ptlib, opal and ekiga
> precompiled*** scp [main-machine-ip] [remote-machine-ip]
>
>
> ***ptlib***
> /* since it was precompiled*/
> make install                                              $$ could do
> that successfully$$$
>
> **opal**
> /* since it was precompiled*/
> make install                                             $$ resulted
> in errors "unable to find ptlib"$$

Quite possibly you have different PKG_CONFIG_PATH values in the two
machines.

However, what you are doing is 50% pointless, because ptlib is an opal
dependency and opal will recompile itself at the 'make install'
stage on the remote machine, because your installation of ptlib will
trigger opal's time stamps.

Chris