On 9/29/05, Sebastian Dransfeld <[EMAIL PROTECTED]> wrote:
> Didier Casse wrote:
> > On 9/29/05, Sebastian Dransfeld <[EMAIL PROTECTED]> wrote:
> >
> >>Didier Casse wrote:
> >>
> >>>There's something wrong with the setup. Even though I followed the
> >>>INSTALL.txt and hacked the e_modules tree, I get this:
> >>>
> >>>make all-recursive
> >>>make[1]: Entering directory `/home/didier/rpmbuild/BUILD/e_modules-0.0.1'
> >>>Making all in src
> >>>make[2]: Entering directory
> >>>`/home/didier/rpmbuild/BUILD/e_modules-0.0.1/src'
> >>>Making all in modules
> >>>make[3]: Entering directory
> >>>`/home/didier/rpmbuild/BUILD/e_modules-0.0.1/src/modules'
> >>>Making all in calendar
> >>>make[4]: Entering directory
> >>>`/home/didier/rpmbuild/BUILD/e_modules-0.0.1/src/modules/calendar'
> >>>Making all in images
> >>>make[5]: Entering directory
> >>>`/home/didier/rpmbuild/BUILD/e_modules-0.0.1/src/modules/calendar/images'
> >>>cd ../../../.. && \
> >>> /bin/sh /opt/DEVEL/e17/apps/e_modules/missing --run automake-1.7
> >>>--gnu src/modules/calendar/images/Makefile
> >>>/bin/sh: /opt/DEVEL/e17/apps/e_modules/missing: No such file or directory
> >>>make[5]: *** [Makefile.in] Error 127
> >>>make[5]: Leaving directory
> >>>`/home/didier/rpmbuild/BUILD/e_modules-0.0.1/src/modules/calendar/images'
> >>>make[4]: *** [all-recursive] Error 1
> >>>make[4]: Leaving directory
> >>>`/home/didier/rpmbuild/BUILD/e_modules-0.0.1/src/modules/calendar'
> >>>make[3]: *** [all-recursive] Error 1
> >>>make[3]: Leaving directory
> >>>`/home/didier/rpmbuild/BUILD/e_modules-0.0.1/src/modules'
> >>>make[2]: *** [all-recursive] Error 1
> >>>make[2]: Leaving directory
> >>>`/home/didier/rpmbuild/BUILD/e_modules-0.0.1/src'
> >>>make[1]: *** [all-recursive] Error 1
> >>>make[1]: Leaving directory `/home/didier/rpmbuild/BUILD/e_modules-0.0.1'
> >>>make: *** [all] Error 2
> >>>
> >>>Now if we look closely, Where the heck did
> >>>"/opt/DEVEL/e17/apps/e_modules/" come from?!?!! :(
> >>>
> >>>In my src/modules/calendar/images/Makefile, this appear again!
> >>>
> >>>[SNIP]
> >>>ACLOCAL = ${SHELL} /opt/DEVEL/e17/apps/e_modules/missing --run aclocal-1.7
> >>>AMDEP_FALSE = #
> >>>AMDEP_TRUE =
> >>>AMTAR = ${SHELL} /opt/DEVEL/e17/apps/e_modules/missing --run tar
> >>>AR = ar
> >>>AUTOCONF = ${SHELL} /opt/DEVEL/e17/apps/e_modules/missing --run autoconf
> >>>AUTOHEADER = ${SHELL} /opt/DEVEL/e17/apps/e_modules/missing --run
> >>>autoheader
> >>>AUTOMAKE = ${SHELL} /opt/DEVEL/e17/apps/e_modules/missing --run
> >>>automake-1.7
> >>>[SNIP]
> >>>
> >>>Whereas if I look at other modules, e.g flame; The Makefile seems to be
> >>>correct:
> >>>
> >>>[SNIP]
> >>>ACLOCAL = ${SHELL} /home/didier/rpmbuild/BUILD/e_modules-0.0.1/missing
> >>>--run aclocal-1.9
> >>>AMDEP_FALSE = #
> >>>AMDEP_TRUE =
> >>>AMTAR = ${SHELL} /home/didier/rpmbuild/BUILD/e_modules-0.0.1/missing --run
> >>>tar
> >>>AR = ar
> >>>AUTOCONF = ${SHELL}
> >>>/home/didier/rpmbuild/BUILD/e_modules-0.0.1/missing --run autoconf
> >>>AUTOHEADER = ${SHELL}
> >>>/home/didier/rpmbuild/BUILD/e_modules-0.0.1/missing --run autoheader
> >>>AUTOMAKE = ${SHELL}
> >>>/home/didier/rpmbuild/BUILD/e_modules-0.0.1/missing --run automake-1.9
> >>>[SNIP]
> >>>
> >>>Any clues?
> >>
> >>Yes. Read again. Put it in e/src/modules not e_modules, and you have to
> >>run autogen.sh afterwards.
> >>
> >
> > Indeed I did read again and the INSTALL.txt says this:
> >
> > ---------------------------------------------------------------------------------------------------------------------------
> > Build this module as part of the e_modules (from cvs).
> >
> > These instructions are based off of essiene's article on modules on
> > the edevelop.org website, give it a read
> >
> > Get your copy of e_modules (src)
> >
> > Create a new directory called calendar in the src/modules directory.
> > [SNIP]
> > -------------------------------------------------------------------------------------------------------------------------
> >
> > If it refers to the built-in modules tree of e, it should state it
> > clearly. This is confusing man. :(
> >
> > For me and probably for others, they went straight for the e_modules.
>
> Sorry. Maybe I'm confused? There was some mails a while ago that
> mentioned this module, and I think they referred to the e modules.
> Anyway, you must run autogen.sh after adding the module, to make your
> own Makefile.in and Makefile.
>
Yes of course I ran autogen.sh again. I took a closer look and
realized that only
src/modules/calendar/images/Makefile is NOT created. Whereas
src/modules/calendar/Makefile and all others are altered by running
autogen.sh.
The src/modules/calendar/images/Makefile remains unchanged. Strange!
[SNIP]
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking for ecore-config... /usr/bin/ecore-config
checking for evas-config... /usr/bin/evas-config
checking for esmart-config... /usr/bin/esmart-config
checking for edje-config... /usr/bin/edje-config
checking for eet-config... /usr/bin/eet-config
checking for enlightenment-config... /usr/bin/enlightenment-config
configure: creating ./config.status
config.status: creating Makefile
config.status: creating data/Makefile
config.status: creating src/Makefile
config.status: creating src/modules/Makefile
config.status: creating src/modules/calendar/Makefile
config.status: creating src/modules/snow/Makefile
config.status: creating src/modules/notes/Makefile
config.status: creating src/modules/flame/Makefile
config.status: creating src/modules/monitor/Makefile
config.status: creating src/modules/weather/Makefile
config.status: creating src/modules/weather/images/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing default commands
Pff...
--
With kind regards,
Didier.
------------
Yum/apt repository for DR17/EFL: http://sps.nus.edu.sg/~didierbe
Didier F.B Casse
PhD candidate, Singapore Synchrotron Light Source (SSLS)
National University of Singapore.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
