2000-12-08 14:54:42 -08:00
|
|
|
dnl Process this file with autoconf to produce a configure script.
|
|
|
|
|
|
2002-01-16 09:31:38 -08:00
|
|
|
AC_INIT
|
2001-07-30 09:59:37 -07:00
|
|
|
|
|
|
|
|
ENLIGHTENMENT_MAJOR=0
|
|
|
|
|
ENLIGHTENMENT_MINOR=17
|
|
|
|
|
ENLIGHTENMENT_MICRO=pre_0
|
|
|
|
|
ENLIGHTENMENT_VERSION=$ENLIGHTENMENT_MAJOR.$ENLIGHTENMENT_MINOR.$ENLIGHTENMENT_MICRO
|
|
|
|
|
|
|
|
|
|
VERSION=$ENLIGHTENMENT_VERSION
|
|
|
|
|
|
|
|
|
|
AM_INIT_AUTOMAKE(enlightenment, $VERSION)
|
2000-12-08 14:54:42 -08:00
|
|
|
AM_CONFIG_HEADER(config.h)
|
|
|
|
|
|
2001-07-30 09:59:37 -07:00
|
|
|
AC_DEFINE_UNQUOTED(ENLIGHTENMENT_VERSION, "$ENLIGHTENMENT_VERSION")
|
|
|
|
|
AC_SUBST(ENLIGHTENMENT_VERSION)
|
|
|
|
|
AC_DEFINE_UNQUOTED(ENLIGHTENMENT_MAJOR, "$ENLIGHTENMENT_MAJOR")
|
|
|
|
|
AC_SUBST(ENLIGHTENMENT_MAJOR)
|
|
|
|
|
AC_DEFINE_UNQUOTED(ENLIGHTENMENT_MINOR, "$ENLIGHTENMENT_MINOR")
|
|
|
|
|
AC_SUBST(ENLIGHTENMENT_MINOR)
|
|
|
|
|
AC_DEFINE_UNQUOTED(ENLIGHTENMENT_MICRO, "$ENLIGHTENMENT_MICRO")
|
|
|
|
|
AC_SUBST(ENLIGHTENMENT_MICRO)
|
|
|
|
|
|
2000-12-08 14:54:42 -08:00
|
|
|
AC_ISC_POSIX
|
|
|
|
|
AC_PROG_CC
|
|
|
|
|
AM_PROG_CC_STDC
|
|
|
|
|
AC_HEADER_STDC
|
Sorry guys.. I had to revert a bunch of changes.. that's life.. but READ the
following (it's in the README now)
-------------------------------------------------------------------------------
Enlightenment 0.17.0 CVS Code....
-------------------------------------------------------------------------------
The Rasterman - raster@valinux.com, raster@rasterman.com
*******************************************************************************
**************** READ THIS! It is of the UTMOST IMPORTANCE! *******************
*******************************************************************************
This is the source code for Enlightenment 0.17 - If you got this you got it
from Enlightenment's CVS repository - or from someone who took it out of
the CVS repository.
The CVS repository is full of code *IN DEVELOPMENT* - that often means it's
in the middle of being worked on and may install strange things in strange
places, make a mess, and may not even be compatible with a final release. If
you at all use this code, you are HEAVILY URGED, when it is finally released,
to remove all traces of anything this CVS code base has installed on your
system (it is COMPLETELY up to you to keep track of that - do NOT expect any
help), and then install the full release on a cleaned system. Don't come
asking "can I just keep using CVS" oonce things are released - thqat is the
reason I pu this paragraph here - so you don't ask. The asnwer is the same
as above - if there is a proper final release use that. CVS is really only
for those havily hacking on the code.
Now we have that warning over and done with. How to build and install from
CVS?
$ ./autogen.sh && make
$ su
Password:
<- as root ->
# make install
You should be able to use the binary of enlightenment as a window manager.
you might be advised for cleanliness to do
$ ./autogen.sh --prefix=/usr/local/e-17
so it installs relative to the /usr/local/e-17 directory and keeps all the
e-17 development code and data in that tree so it is easily removed when the
time codes.
NOTES: Read these carefully!
Enlightenment does not check for previously running Window Managers right
now - so you need to make sure no other WM is running - E will not do that
for you.
Enlightenment has no menus or keybindings or any way of launching
applications right now - you'll have to figure out an alternative way of
doing it.
Enlightenment only handles a small subset of ICCCM and thus will have bugs -
some applications will not behave correctly and may apear in odd spots or
not resize or place themselves properly etc. Expect this - it's code being
worked on. Just be happy it does as much as it already does.
Enlightenment RELIES on lots of libraires that have been written. Ecore,
Ebits, Evas, Edb, Imlib2 just to mention a few. Especially Ebits, Ecore and
Evas change in CVS often - you will need the absolute latest of these if you
wish Enlightenment 0.17 code to run properly or compile. If you update
Enlightenment from CVS update these too to get any changes they have in
their trees.
If you plan on working on the code... STOP! don't rush in and work on it -
even if you have CVS commit access - EXPECT me (Raster) to revert any changes
you make if you do this - regardless of the changes and how much work you
put into them. First read the code well and LEARN it. If you have questions
about some of the more obscure hidden program flow - ASK - but don't go
tampering with it - Enlightenment 0.17's code is much more complex and
intricate than E 0.16 - but at the same time it's much cleaner and more
object oriented. Learn it well first. Some parts of E 0.17 are "hacked" with
hard-coded stuff, just so, for now, it works. They will be virtualized and
imporved over time. If you have plans - tell me about them first - discuss
them before you go impliment them. I know I already have a lot of the
components of E 0.17's code planned in my head - but I won't get to them for
a while - and if people go impliment or hack bad stuff in, it means I have to
spend lots of time fixing something that is bad in the first place, or we
end up doing duplicate work. There *IS* a plan - believe it or not - but to
be honest - it's more complex and large than I can just write down in a
README, so talk about your ideas first. I'm going to be ruthless in keeping
the code neat, clean and free of nasty hacks (except ones I put in as
temporary stop-gap measures to make the thing work - since I know where
those are and what I need to do to do it right). If you can't find me or I
don't reply to your e-mail - don't get impatient - just wait. I currently
have no network access at home, so I'm doing a chunk of code offline. I'll
get to your mail and queries as time allows.
If you have problems with the code or bugs to report, kindly forward them to
/dev/null (the code is in now way or form ready for bug reports - I don't
want crap filling my mailbox).
I hope that clears things up for now.
SVN revision: 3976
2000-12-11 12:08:38 -08:00
|
|
|
AC_C_CONST
|
|
|
|
|
AM_ENABLE_SHARED
|
|
|
|
|
AM_PROG_LIBTOOL
|
2000-12-08 14:54:42 -08:00
|
|
|
|
|
|
|
|
AM_WITH_DMALLOC
|
|
|
|
|
|
|
|
|
|
dnl Add the languages which your application supports here.
|
|
|
|
|
ALL_LINGUAS=""
|
|
|
|
|
|
|
|
|
|
dnl Set PACKAGE_LOCALE_DIR in config.h.
|
|
|
|
|
if test "x${prefix}" = "xNONE"; then
|
|
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_LOCALE_DIR, "${ac_default_prefix}/${DATADIRNAME}/locale")
|
|
|
|
|
else
|
|
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_LOCALE_DIR, "${prefix}/${DATADIRNAME}/locale")
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
dnl Set PACKAGE_DATA_DIR in config.h.
|
|
|
|
|
if test "x${datadir}" = 'x${prefix}/share'; then
|
|
|
|
|
if test "x${prefix}" = "xNONE"; then
|
|
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_DATA_DIR, "${ac_default_prefix}/share/${PACKAGE}")
|
|
|
|
|
else
|
|
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_DATA_DIR, "${prefix}/share/${PACKAGE}")
|
|
|
|
|
fi
|
|
|
|
|
else
|
|
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_DATA_DIR, "${datadir}/${PACKAGE}")
|
|
|
|
|
fi
|
|
|
|
|
|
2000-12-08 17:29:47 -08:00
|
|
|
dnl Set PACKAGE_BIN_DIR in config.h.
|
|
|
|
|
if test "x${datadir}" = 'x${prefix}/bin'; then
|
|
|
|
|
if test "x${prefix}" = "xNONE"; then
|
Sorry guys.. I had to revert a bunch of changes.. that's life.. but READ the
following (it's in the README now)
-------------------------------------------------------------------------------
Enlightenment 0.17.0 CVS Code....
-------------------------------------------------------------------------------
The Rasterman - raster@valinux.com, raster@rasterman.com
*******************************************************************************
**************** READ THIS! It is of the UTMOST IMPORTANCE! *******************
*******************************************************************************
This is the source code for Enlightenment 0.17 - If you got this you got it
from Enlightenment's CVS repository - or from someone who took it out of
the CVS repository.
The CVS repository is full of code *IN DEVELOPMENT* - that often means it's
in the middle of being worked on and may install strange things in strange
places, make a mess, and may not even be compatible with a final release. If
you at all use this code, you are HEAVILY URGED, when it is finally released,
to remove all traces of anything this CVS code base has installed on your
system (it is COMPLETELY up to you to keep track of that - do NOT expect any
help), and then install the full release on a cleaned system. Don't come
asking "can I just keep using CVS" oonce things are released - thqat is the
reason I pu this paragraph here - so you don't ask. The asnwer is the same
as above - if there is a proper final release use that. CVS is really only
for those havily hacking on the code.
Now we have that warning over and done with. How to build and install from
CVS?
$ ./autogen.sh && make
$ su
Password:
<- as root ->
# make install
You should be able to use the binary of enlightenment as a window manager.
you might be advised for cleanliness to do
$ ./autogen.sh --prefix=/usr/local/e-17
so it installs relative to the /usr/local/e-17 directory and keeps all the
e-17 development code and data in that tree so it is easily removed when the
time codes.
NOTES: Read these carefully!
Enlightenment does not check for previously running Window Managers right
now - so you need to make sure no other WM is running - E will not do that
for you.
Enlightenment has no menus or keybindings or any way of launching
applications right now - you'll have to figure out an alternative way of
doing it.
Enlightenment only handles a small subset of ICCCM and thus will have bugs -
some applications will not behave correctly and may apear in odd spots or
not resize or place themselves properly etc. Expect this - it's code being
worked on. Just be happy it does as much as it already does.
Enlightenment RELIES on lots of libraires that have been written. Ecore,
Ebits, Evas, Edb, Imlib2 just to mention a few. Especially Ebits, Ecore and
Evas change in CVS often - you will need the absolute latest of these if you
wish Enlightenment 0.17 code to run properly or compile. If you update
Enlightenment from CVS update these too to get any changes they have in
their trees.
If you plan on working on the code... STOP! don't rush in and work on it -
even if you have CVS commit access - EXPECT me (Raster) to revert any changes
you make if you do this - regardless of the changes and how much work you
put into them. First read the code well and LEARN it. If you have questions
about some of the more obscure hidden program flow - ASK - but don't go
tampering with it - Enlightenment 0.17's code is much more complex and
intricate than E 0.16 - but at the same time it's much cleaner and more
object oriented. Learn it well first. Some parts of E 0.17 are "hacked" with
hard-coded stuff, just so, for now, it works. They will be virtualized and
imporved over time. If you have plans - tell me about them first - discuss
them before you go impliment them. I know I already have a lot of the
components of E 0.17's code planned in my head - but I won't get to them for
a while - and if people go impliment or hack bad stuff in, it means I have to
spend lots of time fixing something that is bad in the first place, or we
end up doing duplicate work. There *IS* a plan - believe it or not - but to
be honest - it's more complex and large than I can just write down in a
README, so talk about your ideas first. I'm going to be ruthless in keeping
the code neat, clean and free of nasty hacks (except ones I put in as
temporary stop-gap measures to make the thing work - since I know where
those are and what I need to do to do it right). If you can't find me or I
don't reply to your e-mail - don't get impatient - just wait. I currently
have no network access at home, so I'm doing a chunk of code offline. I'll
get to your mail and queries as time allows.
If you have problems with the code or bugs to report, kindly forward them to
/dev/null (the code is in now way or form ready for bug reports - I don't
want crap filling my mailbox).
I hope that clears things up for now.
SVN revision: 3976
2000-12-11 12:08:38 -08:00
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_BIN_DIR, "${ac_default_prefix}/bin")
|
2000-12-08 17:29:47 -08:00
|
|
|
else
|
Sorry guys.. I had to revert a bunch of changes.. that's life.. but READ the
following (it's in the README now)
-------------------------------------------------------------------------------
Enlightenment 0.17.0 CVS Code....
-------------------------------------------------------------------------------
The Rasterman - raster@valinux.com, raster@rasterman.com
*******************************************************************************
**************** READ THIS! It is of the UTMOST IMPORTANCE! *******************
*******************************************************************************
This is the source code for Enlightenment 0.17 - If you got this you got it
from Enlightenment's CVS repository - or from someone who took it out of
the CVS repository.
The CVS repository is full of code *IN DEVELOPMENT* - that often means it's
in the middle of being worked on and may install strange things in strange
places, make a mess, and may not even be compatible with a final release. If
you at all use this code, you are HEAVILY URGED, when it is finally released,
to remove all traces of anything this CVS code base has installed on your
system (it is COMPLETELY up to you to keep track of that - do NOT expect any
help), and then install the full release on a cleaned system. Don't come
asking "can I just keep using CVS" oonce things are released - thqat is the
reason I pu this paragraph here - so you don't ask. The asnwer is the same
as above - if there is a proper final release use that. CVS is really only
for those havily hacking on the code.
Now we have that warning over and done with. How to build and install from
CVS?
$ ./autogen.sh && make
$ su
Password:
<- as root ->
# make install
You should be able to use the binary of enlightenment as a window manager.
you might be advised for cleanliness to do
$ ./autogen.sh --prefix=/usr/local/e-17
so it installs relative to the /usr/local/e-17 directory and keeps all the
e-17 development code and data in that tree so it is easily removed when the
time codes.
NOTES: Read these carefully!
Enlightenment does not check for previously running Window Managers right
now - so you need to make sure no other WM is running - E will not do that
for you.
Enlightenment has no menus or keybindings or any way of launching
applications right now - you'll have to figure out an alternative way of
doing it.
Enlightenment only handles a small subset of ICCCM and thus will have bugs -
some applications will not behave correctly and may apear in odd spots or
not resize or place themselves properly etc. Expect this - it's code being
worked on. Just be happy it does as much as it already does.
Enlightenment RELIES on lots of libraires that have been written. Ecore,
Ebits, Evas, Edb, Imlib2 just to mention a few. Especially Ebits, Ecore and
Evas change in CVS often - you will need the absolute latest of these if you
wish Enlightenment 0.17 code to run properly or compile. If you update
Enlightenment from CVS update these too to get any changes they have in
their trees.
If you plan on working on the code... STOP! don't rush in and work on it -
even if you have CVS commit access - EXPECT me (Raster) to revert any changes
you make if you do this - regardless of the changes and how much work you
put into them. First read the code well and LEARN it. If you have questions
about some of the more obscure hidden program flow - ASK - but don't go
tampering with it - Enlightenment 0.17's code is much more complex and
intricate than E 0.16 - but at the same time it's much cleaner and more
object oriented. Learn it well first. Some parts of E 0.17 are "hacked" with
hard-coded stuff, just so, for now, it works. They will be virtualized and
imporved over time. If you have plans - tell me about them first - discuss
them before you go impliment them. I know I already have a lot of the
components of E 0.17's code planned in my head - but I won't get to them for
a while - and if people go impliment or hack bad stuff in, it means I have to
spend lots of time fixing something that is bad in the first place, or we
end up doing duplicate work. There *IS* a plan - believe it or not - but to
be honest - it's more complex and large than I can just write down in a
README, so talk about your ideas first. I'm going to be ruthless in keeping
the code neat, clean and free of nasty hacks (except ones I put in as
temporary stop-gap measures to make the thing work - since I know where
those are and what I need to do to do it right). If you can't find me or I
don't reply to your e-mail - don't get impatient - just wait. I currently
have no network access at home, so I'm doing a chunk of code offline. I'll
get to your mail and queries as time allows.
If you have problems with the code or bugs to report, kindly forward them to
/dev/null (the code is in now way or form ready for bug reports - I don't
want crap filling my mailbox).
I hope that clears things up for now.
SVN revision: 3976
2000-12-11 12:08:38 -08:00
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_BIN_DIR, "${prefix}/bin")
|
2000-12-08 17:29:47 -08:00
|
|
|
fi
|
|
|
|
|
else
|
Sorry guys.. I had to revert a bunch of changes.. that's life.. but READ the
following (it's in the README now)
-------------------------------------------------------------------------------
Enlightenment 0.17.0 CVS Code....
-------------------------------------------------------------------------------
The Rasterman - raster@valinux.com, raster@rasterman.com
*******************************************************************************
**************** READ THIS! It is of the UTMOST IMPORTANCE! *******************
*******************************************************************************
This is the source code for Enlightenment 0.17 - If you got this you got it
from Enlightenment's CVS repository - or from someone who took it out of
the CVS repository.
The CVS repository is full of code *IN DEVELOPMENT* - that often means it's
in the middle of being worked on and may install strange things in strange
places, make a mess, and may not even be compatible with a final release. If
you at all use this code, you are HEAVILY URGED, when it is finally released,
to remove all traces of anything this CVS code base has installed on your
system (it is COMPLETELY up to you to keep track of that - do NOT expect any
help), and then install the full release on a cleaned system. Don't come
asking "can I just keep using CVS" oonce things are released - thqat is the
reason I pu this paragraph here - so you don't ask. The asnwer is the same
as above - if there is a proper final release use that. CVS is really only
for those havily hacking on the code.
Now we have that warning over and done with. How to build and install from
CVS?
$ ./autogen.sh && make
$ su
Password:
<- as root ->
# make install
You should be able to use the binary of enlightenment as a window manager.
you might be advised for cleanliness to do
$ ./autogen.sh --prefix=/usr/local/e-17
so it installs relative to the /usr/local/e-17 directory and keeps all the
e-17 development code and data in that tree so it is easily removed when the
time codes.
NOTES: Read these carefully!
Enlightenment does not check for previously running Window Managers right
now - so you need to make sure no other WM is running - E will not do that
for you.
Enlightenment has no menus or keybindings or any way of launching
applications right now - you'll have to figure out an alternative way of
doing it.
Enlightenment only handles a small subset of ICCCM and thus will have bugs -
some applications will not behave correctly and may apear in odd spots or
not resize or place themselves properly etc. Expect this - it's code being
worked on. Just be happy it does as much as it already does.
Enlightenment RELIES on lots of libraires that have been written. Ecore,
Ebits, Evas, Edb, Imlib2 just to mention a few. Especially Ebits, Ecore and
Evas change in CVS often - you will need the absolute latest of these if you
wish Enlightenment 0.17 code to run properly or compile. If you update
Enlightenment from CVS update these too to get any changes they have in
their trees.
If you plan on working on the code... STOP! don't rush in and work on it -
even if you have CVS commit access - EXPECT me (Raster) to revert any changes
you make if you do this - regardless of the changes and how much work you
put into them. First read the code well and LEARN it. If you have questions
about some of the more obscure hidden program flow - ASK - but don't go
tampering with it - Enlightenment 0.17's code is much more complex and
intricate than E 0.16 - but at the same time it's much cleaner and more
object oriented. Learn it well first. Some parts of E 0.17 are "hacked" with
hard-coded stuff, just so, for now, it works. They will be virtualized and
imporved over time. If you have plans - tell me about them first - discuss
them before you go impliment them. I know I already have a lot of the
components of E 0.17's code planned in my head - but I won't get to them for
a while - and if people go impliment or hack bad stuff in, it means I have to
spend lots of time fixing something that is bad in the first place, or we
end up doing duplicate work. There *IS* a plan - believe it or not - but to
be honest - it's more complex and large than I can just write down in a
README, so talk about your ideas first. I'm going to be ruthless in keeping
the code neat, clean and free of nasty hacks (except ones I put in as
temporary stop-gap measures to make the thing work - since I know where
those are and what I need to do to do it right). If you can't find me or I
don't reply to your e-mail - don't get impatient - just wait. I currently
have no network access at home, so I'm doing a chunk of code offline. I'll
get to your mail and queries as time allows.
If you have problems with the code or bugs to report, kindly forward them to
/dev/null (the code is in now way or form ready for bug reports - I don't
want crap filling my mailbox).
I hope that clears things up for now.
SVN revision: 3976
2000-12-11 12:08:38 -08:00
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_BIN_DIR, "${bindir}")
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
dnl Set PACKAGE_LIB_DIR in config.h.
|
|
|
|
|
if test "x${datadir}" = 'x${prefix}/lib'; then
|
|
|
|
|
if test "x${prefix}" = "xNONE"; then
|
|
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_LIB_DIR, "${ac_default_prefix}/lib")
|
|
|
|
|
else
|
|
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_LIB_DIR, "${prefix}/lib")
|
|
|
|
|
fi
|
|
|
|
|
else
|
|
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_LIB_DIR, "${libdir}")
|
2000-12-08 17:29:47 -08:00
|
|
|
fi
|
|
|
|
|
|
2000-12-08 14:54:42 -08:00
|
|
|
dnl Set PACKAGE_SOURCE_DIR in config.h.
|
|
|
|
|
packagesrcdir=`cd $srcdir && pwd`
|
|
|
|
|
AC_DEFINE_UNQUOTED(PACKAGE_SOURCE_DIR, "${packagesrcdir}")
|
|
|
|
|
|
|
|
|
|
dnl Use -Wall if we have gcc.
|
|
|
|
|
changequote(,)dnl
|
|
|
|
|
if test "x$GCC" = "xyes"; then
|
|
|
|
|
case " $CFLAGS " in
|
|
|
|
|
*[\ \ ]-Wall[\ \ ]*) ;;
|
|
|
|
|
*) CFLAGS="$CFLAGS -Wall" ;;
|
|
|
|
|
esac
|
|
|
|
|
fi
|
|
|
|
|
changequote([,])dnl
|
|
|
|
|
|
2001-09-24 14:21:25 -07:00
|
|
|
dnl Check for Imlib2.
|
|
|
|
|
AC_ARG_WITH(imlib2,
|
|
|
|
|
[ --with-imlib2=DIR use imlib2 in <DIR>],
|
|
|
|
|
[CFLAGS="$CFLAGS -I$withval/include"
|
|
|
|
|
LIBS="-L$withval/lib $LIBS"])
|
|
|
|
|
|
|
|
|
|
AC_PATH_GENERIC(imlib2,, [
|
|
|
|
|
AC_SUBST(imlib2_libs)
|
|
|
|
|
AC_SUBST(imlib2_cflags)],
|
|
|
|
|
AC_MSG_ERROR(Cannot find imlib2: Is imlib2-config in path?))
|
|
|
|
|
imlib2_libs=`imlib2-config --libs`
|
|
|
|
|
imlib2_cflags=`imlib2-config --cflags`
|
|
|
|
|
|
2001-08-02 16:43:02 -07:00
|
|
|
dnl Check for Evas.
|
|
|
|
|
AC_ARG_WITH(evas,
|
|
|
|
|
[ --with-evas=DIR use evas in <DIR>],
|
|
|
|
|
[CFLAGS="$CFLAGS -I$withval/include"
|
|
|
|
|
LIBS="-L$withval/lib $LIBS"])
|
|
|
|
|
|
|
|
|
|
AC_PATH_GENERIC(evas,, [
|
|
|
|
|
AC_SUBST(evas_libs)
|
|
|
|
|
AC_SUBST(evas_cflags)],
|
2001-08-02 16:44:12 -07:00
|
|
|
AC_MSG_ERROR(Cannot find evas: Is evas-config in path?))
|
2000-12-08 14:54:42 -08:00
|
|
|
evas_libs=`evas-config --libs`
|
2001-08-02 16:43:02 -07:00
|
|
|
evas_cflags=`evas-config --cflags`
|
|
|
|
|
|
|
|
|
|
dnl Check for Edb.
|
|
|
|
|
AC_ARG_WITH(edb,
|
|
|
|
|
[ --with-edb=DIR use edb in <DIR>],
|
|
|
|
|
[CFLAGS="$CFLAGS -I$withval/include"
|
|
|
|
|
LIBS="-L$withval/lib $LIBS"])
|
|
|
|
|
|
|
|
|
|
AC_PATH_GENERIC(edb,, [
|
|
|
|
|
AC_SUBST(edb_libs)
|
|
|
|
|
AC_SUBST(edb_cflags)],
|
|
|
|
|
AC_MSG_ERROR(Cannot find edb: Is edb-config in path?))
|
2000-12-08 14:54:42 -08:00
|
|
|
edb_libs=`edb-config --libs`
|
2001-08-02 16:43:02 -07:00
|
|
|
edb_cflags=`edb-config --cflags`
|
|
|
|
|
|
|
|
|
|
dnl Check for Ebits.
|
|
|
|
|
AC_ARG_WITH(ebits,
|
|
|
|
|
[ --with-ebits=DIR use ebits in <DIR>],
|
|
|
|
|
[CFLAGS="$CFLAGS -I$withval/include"
|
|
|
|
|
LIBS="-L$withval/lib $LIBS"])
|
|
|
|
|
|
|
|
|
|
AC_PATH_GENERIC(ebits,, [
|
|
|
|
|
AC_SUBST(ebits_libs)
|
|
|
|
|
AC_SUBST(ebits_cflags)],
|
|
|
|
|
AC_MSG_ERROR(Cannot find ebits: Is ebits-config in path?))
|
2000-12-08 14:54:42 -08:00
|
|
|
ebits_libs=`ebits-config --libs`
|
2001-08-02 16:43:02 -07:00
|
|
|
ebits_cflags=`ebits-config --cflags`
|
|
|
|
|
|
|
|
|
|
dnl Check for Ecore.
|
|
|
|
|
AC_ARG_WITH(ecore,
|
|
|
|
|
[ --with-ecore=DIR use ecore in <DIR>],
|
|
|
|
|
[CFLAGS="$CFLAGS -I$withval/include"
|
|
|
|
|
LIBS="-L$withval/lib $LIBS"])
|
|
|
|
|
|
|
|
|
|
AC_PATH_GENERIC(ecore,, [
|
|
|
|
|
AC_SUBST(ecore_libs)
|
|
|
|
|
AC_SUBST(ecore_cflags)],
|
|
|
|
|
AC_MSG_ERROR(Cannot find ecore: Is ecore-config in path?))
|
2000-12-08 14:54:42 -08:00
|
|
|
ecore_libs=`ecore-config --libs`
|
2001-08-02 16:43:02 -07:00
|
|
|
ecore_cflags=`ecore-config --cflags`
|
|
|
|
|
|
|
|
|
|
dnl Check for Efsd.
|
|
|
|
|
AC_ARG_WITH(efsd,
|
|
|
|
|
[ --with-efsd=DIR use efsd in <DIR>],
|
|
|
|
|
[CFLAGS="$CFLAGS -I$withval/include"
|
|
|
|
|
LIBS="-L$withval/lib $LIBS"])
|
2001-02-09 00:13:16 -08:00
|
|
|
|
2001-08-02 16:43:02 -07:00
|
|
|
AC_PATH_GENERIC(efsd,, [
|
|
|
|
|
AC_SUBST(efsd_libs)
|
|
|
|
|
AC_SUBST(efsd_cflags)],
|
|
|
|
|
AC_MSG_ERROR(Cannot find efsd: Is efsd-config in path?))
|
|
|
|
|
efsd_libs=`efsd-config --libs`
|
|
|
|
|
efsd_cflags=`efsd-config --cflags`
|
2000-12-08 14:54:42 -08:00
|
|
|
|
2002-01-25 18:01:42 -08:00
|
|
|
dnl Check for Edb.
|
|
|
|
|
AC_ARG_WITH(ebg,
|
|
|
|
|
[ --with-ebg=DIR use ebg in <DIR>],
|
|
|
|
|
[CFLAGS="$CFLAGS -I$withval/include"
|
|
|
|
|
LIBS="-L$withval/lib $LIBS"])
|
|
|
|
|
|
|
|
|
|
AC_PATH_GENERIC(ebg,, [
|
|
|
|
|
AC_SUBST(ebg_libs)
|
|
|
|
|
AC_SUBST(ebg_cflags)],
|
|
|
|
|
AC_MSG_ERROR(Cannot find ebg: Is ebg-config in path?))
|
|
|
|
|
ebg_libs=`ebg-config --libs`
|
|
|
|
|
ebg_cflags=`ebg-config --cflags`
|
|
|
|
|
|
2001-09-24 14:21:25 -07:00
|
|
|
CFLAGS=$imlib2_cflags
|
|
|
|
|
LIBS=$imlib2_libs
|
|
|
|
|
dnl Check for db loader.
|
|
|
|
|
AC_TRY_RUN([
|
|
|
|
|
#include <stdio.h>
|
|
|
|
|
#include <unistd.h>
|
|
|
|
|
#include <stdlib.h>
|
|
|
|
|
#include <X11/Xlib.h>
|
|
|
|
|
#include <Imlib2.h>
|
|
|
|
|
|
|
|
|
|
int main(int argc, char **argv) {
|
|
|
|
|
Imlib_Image im;
|
|
|
|
|
int width;
|
|
|
|
|
|
|
|
|
|
im = imlib_load_image("$packagesrcdir/data/test/test.db:/test/image");
|
|
|
|
|
if (!im) exit(-1);
|
|
|
|
|
imlib_context_set_image(im);
|
|
|
|
|
width = imlib_image_get_width();
|
|
|
|
|
if (width != 7) exit(-1);
|
|
|
|
|
exit(0);
|
|
|
|
|
return 0;
|
|
|
|
|
argv=NULL;
|
|
|
|
|
argc=0;
|
|
|
|
|
}
|
|
|
|
|
],
|
|
|
|
|
[echo "checking for imlib2 db loader... yes"],
|
|
|
|
|
[
|
|
|
|
|
echo "checking for imlib2 db loader... no"
|
|
|
|
|
AC_MSG_ERROR(Cannot detect db loader: Have you installed imlib2_loaders?)
|
|
|
|
|
],
|
|
|
|
|
AC_MSG_ERROR(Sorry. Enlightenment cannot be cross-compiled.))
|
|
|
|
|
|
2001-10-12 17:08:39 -07:00
|
|
|
|
|
|
|
|
dnl Checking for Perl:
|
|
|
|
|
AC_PATH_PROG(PERL,perl,0)
|
|
|
|
|
AC_SUBST(PERL)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
dnl Look for jade for sgml translations.
|
|
|
|
|
AC_ARG_WITH(dbsheets,
|
|
|
|
|
[ --with-dbsheets=DIR use DIR to specify your DocBook stylesheets installation path.],
|
|
|
|
|
DB_STYLESHEETS="$withval", DB_STYLESHEETS="/usr/lib/sgml/stylesheet/dsssl/docbook/nwalsh")
|
|
|
|
|
AC_SUBST(DB_STYLESHEETS)
|
|
|
|
|
AC_PATH_PROG(JADE, jade)
|
|
|
|
|
AM_CONDITIONAL(HAVE_JADE, test "x$JADE" != "x" && test -d "$DB_STYLESHEETS")
|
2002-03-10 11:22:30 -08:00
|
|
|
AC_CHECK_LIB(c, dlopen, LIBDL="",[AC_CHECK_LIB(dl, dlopen, LIBDL="-ldl")])
|
|
|
|
|
AC_SUBST(LIBDL)
|
2001-10-12 17:08:39 -07:00
|
|
|
|
2002-01-19 22:02:14 -08:00
|
|
|
AC_OUTPUT([
|
2001-10-12 17:08:39 -07:00
|
|
|
Makefile
|
|
|
|
|
src/Makefile
|
|
|
|
|
lib/Makefile
|
|
|
|
|
client/Makefile
|
2001-10-19 02:13:18 -07:00
|
|
|
tools/Makefile
|
2001-10-12 17:08:39 -07:00
|
|
|
doc/Makefile
|
|
|
|
|
doc/kernel-doc
|
|
|
|
|
doc/html-customizations.dsl
|
2002-01-16 09:31:38 -08:00
|
|
|
data/scripts/build_iconbar_db.sh
|
2002-01-19 22:02:14 -08:00
|
|
|
], [
|
2002-01-16 09:31:38 -08:00
|
|
|
chmod +x doc/kernel-doc
|
2002-01-19 22:02:14 -08:00
|
|
|
])
|
