Thanks guys. That worked.
Jim
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn
Berto wrote:
> OK now it compiled.!!
>
> i established the PKG_CONFIG_PATH variable with export to
> /usr/local/lib/pkgconfig
>
Exactly how do you do this? I can't get e to compile either - for the
same reasons.
Thanks,
Jim
> and compiled everything from the beginning
>
> thanks to every
OK now it compiled.!!
i established the PKG_CONFIG_PATH variable with export to
/usr/local/lib/pkgconfig
and compiled everything from the beginning
thanks to everybody
pd: the last version of e16 its very good too ;)
-
Take
On Fr, 23.03.07 21:41 Berto <[EMAIL PROTECTED]> wrote:
> thanks for your fast reply
> i dont have that man page :( ?
>
> I'm doing export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
>
> [...]
> checking pkg-config is at least version 0.9.0... yes
> checking for EDJE... configure: error: Package
thanks for your fast reply
i dont have that man page :( ?
I'm doing export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
[...]
checking pkg-config is at least version 0.9.0... yes
checking for EDJE... configure: error: Package requirements (
evas >= 0.9.9
ecore-evas >= 0.9.9
ecore-job >= 0.9
Berto, il 23/03/2007 21:12, scrisse:
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
from "man pkg-config":
pkg-config retrieves information about packages from special
metadata files. These files are named after the package, wi
i compiled that libraries as always, they are an /usr/local/libs
what changed...this never happened to me before ??
what do i need to export ?
thanks in advance...
[]
checking whether to build edje_cc... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least versio
