E17 is coming?? (Part 1)

merclude · Posted: Mon Nov 29, 2004 11:12 am Post subject:

having some issues building cvs, was hoping i could find some help here(im sure others will run into the same problem, at least i hope so!..sorry..heh..)

anyway, i was originally using the script to build from cvs that someone so kindly posted earlier, however there are a few things that fail, so im working my way downt he list building them manually, and at this point im on ecore..this is the error im getting:

gimpel · Posted: Mon Nov 29, 2004 12:02 pm Post subject:

chipi · n00b Joined: 05 Oct 2003 Posts: 62 Location: Israel

I'm sorry, but I can't get E17 to compile... I pulled the source from CVS just fine, and ./configure works fine too, but when I try to 'make' the code, I get

paneb · n00b Joined: 20 Mar 2004 Posts: 73

when i build E apps manually i type WANT_AUTOMAKE="1.8" before autogen.sh and it works..

gimpel · Posted: Mon Nov 29, 2004 12:43 pm Post subject:

not_registered · Tux's lil' helper Joined: 04 Feb 2003 Posts: 148

has anyone got the left mouse menu to show anything?
_________________
It's Floam, it's Floam. It's flying foam!

chipi · n00b Joined: 05 Oct 2003 Posts: 62 Location: Israel

damn, that was it. I should have done ./autogen again, not just ./configure.

I'm now gettine the same error coin got,

gimpel · Posted: Mon Nov 29, 2004 1:55 pm Post subject:

COiN3D · Posted: Mon Nov 29, 2004 2:10 pm Post subject:

Colddiver · n00b Joined: 06 Feb 2003 Posts: 22 Location: Canada

I also have the same problem as coin and I think that the problem might be related to automake/autoconf.

Seems like I only have autoconf 1.8.5 installed on my system. I looked into portage and there is a masked autoconf 1.7.9 that we could potentially install. I am just wondering if it is safe to have 2 versions of autoconf installed on the same system.

Colddiver

chipi · n00b Joined: 05 Oct 2003 Posts: 62 Location: Israel

There is no need to have them both, you can temporary install the older one over the newer, it shouldn't harm if you're just checking.

But, I doesn't look like the problem to me. I think we're having deps problems - something needs to be update from CVS, maybe ecore.

Colddiver · n00b Joined: 06 Feb 2003 Posts: 22 Location: Canada

Humm... The problem lies elsewhere. I have installed automake 1.7.9 and no changes. By looking more closely at the build process, I found several instances of these messages:

ERROR:
The edb-config development script was not found in your execute
path. This may mean one of several things
1. You may not have installed the edb-devel (or edb-dev)
packages.
2. You may have edb installed somewhere not covered by your path.

If this is the case make sure you have the packages installed, AND
that the edb-config script is in your execute path (see your
shell's manual page on setting the $PATH environment variable), OR
alternatively, specify the script to use with --with-edb-config.
configure: error: Fatal Error: no edb-config detected.

I got the same error for evas-config & edb-config. So this seems to be a PATH problem then.

Colddiver

chipi · n00b Joined: 05 Oct 2003 Posts: 62 Location: Israel

Do you have edb-config? I do, but I can't see where you saw that error message. My 'make' error says nothing about edb-config.

merclude · Posted: Mon Nov 29, 2004 2:59 pm Post subject:

well, ill reply to myself here, turns out i had an old evas still installed(even though i installed the evas from cvs) unmerging evas then installing from cvs fixed it.
_________________
-merc
my site: http://escalated.net

Colddiver · n00b Joined: 06 Feb 2003 Posts: 22 Location: Canada

I used the bash script posted on the previous page and it did compile edb, eet and other stuff.

I added /usr/local/bin to my PATH and I got this:

checking for evas-config... no
./configure: line 1: --cflags: command not found
./configure: line 1: --libs: command not found
checking for ecore-config... no
./configure: line 1: --cflags: command not found
./configure: line 1: --libs: command not found
checking for edje-config... no
./configure: line 1: --cflags: command not found
./configure: line 1: --libs: command not found
checking for eet-config... /usr/local/bin/eet-config
checking for embryo-config... /usr/local/bin/embryo-config
./configure: line 1: --prefix: command not found
./configure: line 1: --prefix: command not found
configure: creating ./config.status

So it seems that either some stuff did not compile or that there are still a few missing PATH variables. I'm gonna have to investigate this further.

Colddiver

Colddiver · n00b Joined: 06 Feb 2003 Posts: 22 Location: Canada

Well... As it turns out, quite a few thing did not compile because of the PATH problem. I am now building manually everything that came after Imlib2 in the bash script. Hopefully, this will work.

Colddiver

Colddiver · n00b Joined: 06 Feb 2003 Posts: 22 Location: Canada

Seems OK so far...

It is confirmed, several things did not build because of the PATH problem. I'm now half way into the process and everything has built cleanly so far.

I would suggest adding a check for /usr/local/bin in the PATH variable into the bash shell script.

Colddiver

Colddiver · n00b Joined: 06 Feb 2003 Posts: 22 Location: Canada

A few more issues...

evoak refused to compile because Edje_Edit.h is missing. And the bad part is that I couldn't find it anywhere (I only found Edje.h). Searching for Edje_Edit.h on google, I found that the content of Edje_Edit.h was merged into edje_private.h.

I thus did:
cp /root/e17/libs/edje/src/lib/edje_private.h /usr/local/include/Edje_Edit.h

And tried make again for evoak. It worked.

Now, entrance failed at the configure script because it couldn't find Ecore_Evas:

checking for evas-config... /usr/local/bin/evas-config
checking for evas - version >= 1.0.0... ./configure: line 4599: test: 1_pre13: integer expression expected
yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking Ecore.h usability... yes
checking Ecore.h presence... yes
checking for Ecore.h... yes
checking for ecore_list_new in -lecore... yes
checking Ecore_Evas.h usability... yes
checking Ecore_Evas.h presence... yes
checking for Ecore_Evas.h... yes
checking for ecore_evas_init in -lecore_evas... no
configure: error: Cannot find Ecore_Evas!

I unfortunately don't know how to fix this one so I skipped it. I was able to compile e without any problems.

So, to summarize, here is what I did:

1. Installed the masked automake-1.7.9 (and dependency)
2. Add /usr/local/bin to my PATH by doing: export PATH=/usr/local/bin:$PATH

3. Fixed the Edje_Edit.h missing header problem by doing:
cp /root/e17/libs/edje/src/lib/edje_private.h /usr/local/include/Edje_Edit.h

Note: I could probably just have re-run the bash script at this point

4. Set up both WANT_AUTOMAKE and WANT_AUTOCONF by doing:
export WANT_AUTOMAKE=1.7
export WANT_AUTOCONF=2.5

5. Ran ./autogen.sh followed my make && make install for everything after Imlib2 in the bash script.

Doing this, everything compiled except entrance.

If you follow this procedure, it might be a good idea now to unmerge automake-1.7.9 just to be on the safe side.

Now I need to start playing with this thing!

Colddiver

jxn · Guru Joined: 27 Aug 2004 Posts: 327 Location: south dakota

vrln · Guru Joined: 11 Sep 2004 Posts: 534 Location: Finland

KingPunk · Posted: Mon Nov 29, 2004 7:08 pm Post subject:

Luxus · Posted: Mon Nov 29, 2004 9:12 pm Post subject:

whats about a cvs ebuild? nobody here who can create it?

altrent · n00b Joined: 03 Mar 2004 Posts: 55

Same error here:

vrln · Guru Joined: 11 Sep 2004 Posts: 534 Location: Finland

gimpel · Posted: Mon Nov 29, 2004 11:21 pm Post subject: