From c53ec2056dc2090ef0b8d2193b433aea4ee95cc3 Mon Sep 17 00:00:00 2001 From: Tilman Sauerbeck Date: Wed, 27 Apr 2005 14:27:01 +0000 Subject: [PATCH] Reworked the build system. --- INSTALL | 229 ------------------------------------------ Makefile.am | 9 -- README | 8 +- Rakefile | 36 +++++++ autogen.sh | 62 ------------ configure.ac | 33 ------ library.rb | 35 +++++++ m4/Makefile.am | 3 - m4/ac_path_generic.m4 | 136 ------------------------- m4/ac_ruby_ext.m4 | 51 ---------- src/Makefile.am | 15 --- 11 files changed, 77 insertions(+), 540 deletions(-) delete mode 100644 INSTALL delete mode 100644 Makefile.am create mode 100644 Rakefile delete mode 100755 autogen.sh delete mode 100644 configure.ac create mode 100644 library.rb delete mode 100644 m4/Makefile.am delete mode 100644 m4/ac_path_generic.m4 delete mode 100644 m4/ac_ruby_ext.m4 delete mode 100644 src/Makefile.am diff --git a/INSTALL b/INSTALL deleted file mode 100644 index 54caf7c..0000000 --- a/INSTALL +++ /dev/null @@ -1,229 +0,0 @@ -Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software -Foundation, Inc. - - This file is free documentation; the Free Software Foundation gives -unlimited permission to copy, distribute and modify it. - -Basic Installation -================== - - These are generic installation instructions. - - The `configure' shell script attempts to guess correct values for -various system-dependent variables used during compilation. It uses -those values to create a `Makefile' in each directory of the package. -It may also create one or more `.h' files containing system-dependent -definitions. Finally, it creates a shell script `config.status' that -you can run in the future to recreate the current configuration, and a -file `config.log' containing compiler output (useful mainly for -debugging `configure'). - - It can also use an optional file (typically called `config.cache' -and enabled with `--cache-file=config.cache' or simply `-C') that saves -the results of its tests to speed up reconfiguring. (Caching is -disabled by default to prevent problems with accidental use of stale -cache files.) - - If you need to do unusual things to compile the package, please try -to figure out how `configure' could check whether to do them, and mail -diffs or instructions to the address given in the `README' so they can -be considered for the next release. If you are using the cache, and at -some point `config.cache' contains results you don't want to keep, you -may remove or edit it. - - The file `configure.ac' (or `configure.in') is used to create -`configure' by a program called `autoconf'. You only need -`configure.ac' if you want to change it or regenerate `configure' using -a newer version of `autoconf'. - -The simplest way to compile this package is: - - 1. `cd' to the directory containing the package's source code and type - `./configure' to configure the package for your system. If you're - using `csh' on an old version of System V, you might need to type - `sh ./configure' instead to prevent `csh' from trying to execute - `configure' itself. - - Running `configure' takes awhile. While running, it prints some - messages telling which features it is checking for. - - 2. Type `make' to compile the package. - - 3. Optionally, type `make check' to run any self-tests that come with - the package. - - 4. Type `make install' to install the programs and any data files and - documentation. - - 5. You can remove the program binaries and object files from the - source code directory by typing `make clean'. To also remove the - files that `configure' created (so you can compile the package for - a different kind of computer), type `make distclean'. There is - also a `make maintainer-clean' target, but that is intended mainly - for the package's developers. If you use it, you may have to get - all sorts of other programs in order to regenerate files that came - with the distribution. - -Compilers and Options -===================== - - Some systems require unusual options for compilation or linking that -the `configure' script does not know about. Run `./configure --help' -for details on some of the pertinent environment variables. - - You can give `configure' initial values for configuration parameters -by setting variables in the command line or in the environment. Here -is an example: - - ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix - - *Note Defining Variables::, for more details. - -Compiling For Multiple Architectures -==================================== - - You can compile the package for more than one kind of computer at the -same time, by placing the object files for each architecture in their -own directory. To do this, you must use a version of `make' that -supports the `VPATH' variable, such as GNU `make'. `cd' to the -directory where you want the object files and executables to go and run -the `configure' script. `configure' automatically checks for the -source code in the directory that `configure' is in and in `..'. - - If you have to use a `make' that does not support the `VPATH' -variable, you have to compile the package for one architecture at a -time in the source code directory. After you have installed the -package for one architecture, use `make distclean' before reconfiguring -for another architecture. - -Installation Names -================== - - By default, `make install' will install the package's files in -`/usr/local/bin', `/usr/local/man', etc. You can specify an -installation prefix other than `/usr/local' by giving `configure' the -option `--prefix=PATH'. - - You can specify separate installation prefixes for -architecture-specific files and architecture-independent files. If you -give `configure' the option `--exec-prefix=PATH', the package will use -PATH as the prefix for installing programs and libraries. -Documentation and other data files will still use the regular prefix. - - In addition, if you use an unusual directory layout you can give -options like `--bindir=PATH' to specify different values for particular -kinds of files. Run `configure --help' for a list of the directories -you can set and what kinds of files go in them. - - If the package supports it, you can cause programs to be installed -with an extra prefix or suffix on their names by giving `configure' the -option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. - -Optional Features -================= - - Some packages pay attention to `--enable-FEATURE' options to -`configure', where FEATURE indicates an optional part of the package. -They may also pay attention to `--with-PACKAGE' options, where PACKAGE -is something like `gnu-as' or `x' (for the X Window System). The -`README' should mention any `--enable-' and `--with-' options that the -package recognizes. - - For packages that use the X Window System, `configure' can usually -find the X include and library files automatically, but if it doesn't, -you can use the `configure' options `--x-includes=DIR' and -`--x-libraries=DIR' to specify their locations. - -Specifying the System Type -========================== - - There may be some features `configure' cannot figure out -automatically, but needs to determine by the type of machine the package -will run on. Usually, assuming the package is built to be run on the -_same_ architectures, `configure' can figure that out, but if it prints -a message saying it cannot guess the machine type, give it the -`--build=TYPE' option. TYPE can either be a short name for the system -type, such as `sun4', or a canonical name which has the form: - - CPU-COMPANY-SYSTEM - -where SYSTEM can have one of these forms: - - OS KERNEL-OS - - See the file `config.sub' for the possible values of each field. If -`config.sub' isn't included in this package, then this package doesn't -need to know the machine type. - - If you are _building_ compiler tools for cross-compiling, you should -use the `--target=TYPE' option to select the type of system they will -produce code for. - - If you want to _use_ a cross compiler, that generates code for a -platform different from the build platform, you should specify the -"host" platform (i.e., that on which the generated programs will -eventually be run) with `--host=TYPE'. - -Sharing Defaults -================ - - If you want to set default values for `configure' scripts to share, -you can create a site shell script called `config.site' that gives -default values for variables like `CC', `cache_file', and `prefix'. -`configure' looks for `PREFIX/share/config.site' if it exists, then -`PREFIX/etc/config.site' if it exists. Or, you can set the -`CONFIG_SITE' environment variable to the location of the site script. -A warning: not all `configure' scripts look for a site script. - -Defining Variables -================== - - Variables not defined in a site shell script can be set in the -environment passed to `configure'. However, some packages may run -configure again during the build, and the customized values of these -variables may be lost. In order to avoid this problem, you should set -them in the `configure' command line, using `VAR=value'. For example: - - ./configure CC=/usr/local2/bin/gcc - -will cause the specified gcc to be used as the C compiler (unless it is -overridden in the site shell script). - -`configure' Invocation -====================== - - `configure' recognizes the following options to control how it -operates. - -`--help' -`-h' - Print a summary of the options to `configure', and exit. - -`--version' -`-V' - Print the version of Autoconf used to generate the `configure' - script, and exit. - -`--cache-file=FILE' - Enable the cache: use and save the results of the tests in FILE, - traditionally `config.cache'. FILE defaults to `/dev/null' to - disable caching. - -`--config-cache' -`-C' - Alias for `--cache-file=config.cache'. - -`--quiet' -`--silent' -`-q' - Do not print messages saying which checks are being made. To - suppress all normal output, redirect it to `/dev/null' (any error - messages will still be shown). - -`--srcdir=DIR' - Look for the package's source code in directory DIR. Usually - `configure' can determine that directory automatically. - -`configure' also accepts some other, not widely useful, options. Run -`configure --help' for more details. - diff --git a/Makefile.am b/Makefile.am deleted file mode 100644 index 8384215..0000000 --- a/Makefile.am +++ /dev/null @@ -1,9 +0,0 @@ -## $Id: Makefile.am 59 2004-08-10 14:10:31Z tilman $ - -SUBDIRS = m4 src -DOC_INPUT = src/rb_edje_main.c \ - src/rb_edje.c \ - src/rb_part.c - -doc: $(DOC_INPUT) - rdoc $(DOC_INPUT) diff --git a/README b/README index 2022c20..202ccaf 100644 --- a/README +++ b/README @@ -1,4 +1,4 @@ -$Id: README 59 2004-08-10 14:10:31Z tilman $ +$Id: README 327 2005-04-27 14:27:01Z tilman $ ruby-edje - Ruby bindings for Edje ================================== @@ -14,7 +14,11 @@ library, edje. Installation ------------ -Please see INSTALL. +Run "rake install" to install ruby-edje. +If you didn't install Edje to /usr/local, execute the following line +instead: + +EDJE_PREFIX=/prefix/edje/is/installed/in rake install Documentation diff --git a/Rakefile b/Rakefile new file mode 100644 index 0000000..801ed10 --- /dev/null +++ b/Rakefile @@ -0,0 +1,36 @@ +# $Id: Rakefile 327 2005-04-27 14:27:01Z tilman $ + +require "library" +require "rake/clean" +require "rake/testtask" +require "rake/rdoctask" +require "rake/packagetask" +require "rake/contrib/compositepublisher" +require "rake/contrib/sshpublisher" + +CLOBBER.include("src/*.{s,}o") + +ext_obj = Dir["src/*.c"].map { |f| f.sub(/\.[^.]+$/, ".o") } +ext_lib = Library.new("edje", ENV["EDJE_PREFIX"] || "/usr/local", "src") + +task :default => [ext_lib.so] + +file ext_lib.so => ext_lib.objects do |t| + sh "cc #{ext_lib.ldflags} -shared -Wl " + + " #{t.prerequisites.join(" ")} -o #{t.name}" +end + +ext_lib.objects.each do |object| + file object => object.sub(/\.[^.]+$/, ".c") do |t| + sh "cc #{ext_lib.cflags} #{t.prerequisites.first} " + + "-c -o #{t.name}" + end +end + +task :install => [ext_lib.so] do |t| + destdir = "#{ENV["DESTDIR"]}" + sitearchdir = Config::CONFIG['sitearchdir'] + + FileUtils::Verbose.install(ext_lib.so, destdir + sitearchdir, + :mode => 0755) +end diff --git a/autogen.sh b/autogen.sh deleted file mode 100755 index a535e8d..0000000 --- a/autogen.sh +++ /dev/null @@ -1,62 +0,0 @@ -#! /bin/sh -# Run this to generate all the initial makefiles, etc. - -# Stolen from the GNU Midnight Commander. Customized for giFTcurs. Stolen from -# giFTcurs. Customized for giFT. Stolen from giFT. -# Customized for $this_project. - -# Make it possible to specify path in the environment -: ${AUTOCONF=autoconf} -: ${AUTOHEADER=autoheader} -: ${AUTOMAKE=automake} -: ${ACLOCAL=aclocal} -: ${LIBTOOLIZE=libtoolize} - -srcdir=`dirname $0` -test -z "$srcdir" && srcdir=. - -( -cd $srcdir - -# The autoconf cache (version after 2.52) is not reliable yet. -rm -rf autom4te.cache - -rm -f aclocal.m4 -ACLOCAL_INCLUDES="-I m4" - -# Some old version of GNU build tools fail to set error codes. -# Check that they generate some of the files they should. - -echo "Running $ACLOCAL..." -$ACLOCAL $ACLOCAL_INCLUDES $ACLOCAL_FLAGS || exit 1 -test -f aclocal.m4 || \ - { echo "aclocal failed to generate aclocal.m4" 2>&1; exit 1; } - -echo "Running $AUTOHEADER..." -$AUTOHEADER || exit 1 -test -f config.h.in || \ - { echo "autoheader failed to generate config.h.in" 2>&1; exit 1; } - -echo "Running $AUTOCONF..." -$AUTOCONF || exit 1 -test -f configure || \ - { echo "autoconf failed to generate configure" 2>&1; exit 1; } - -# hack hack hack...i hate autotools. -echo "Running $LIBTOOLIZE --automake..." -$LIBTOOLIZE --automake || exit 1 -test -f ltmain.sh || \ - { echo "libtoolize failed to generate ltmain.sh" 2>&1; exit 1; } - -# Workaround for Automake 1.5 to ensure that depcomp is distributed. -echo "Running $AUTOMAKE..." -$AUTOMAKE -c -a src/Makefile || exit 1 -$AUTOMAKE -c -a || exit 1 -test -f Makefile.in || \ - { echo "automake failed to generate Makefile.in" 2>&1; exit 1; } - -) || exit 1 - -echo -echo "Type './configure' to configure ruby-edje." -echo diff --git a/configure.ac b/configure.ac deleted file mode 100644 index 0515398..0000000 --- a/configure.ac +++ /dev/null @@ -1,33 +0,0 @@ -dnl $Id: configure.ac 7 2004-06-19 19:32:33Z tilman $ - -AC_INIT(ruby-edje, 0.0.1) -AC_CONFIG_SRCDIR([src/rb_edje_main.c]) - -AM_INIT_AUTOMAKE([dist-bzip2]) -AM_CONFIG_HEADER(config.h) - -AC_PROG_CC -AC_PROG_CC_STDC -AC_PROG_INSTALL - -AM_DISABLE_STATIC -AC_PROG_LIBTOOL - -AC_HEADER_STDC -AC_HEADER_STDBOOL - -AC_RUBY_EXT - -AC_PATH_GENERIC(evas, , , - AC_MSG_ERROR(Cannot find evas: Is evas-config in path?)) - -AC_PATH_GENERIC(edje, , , - AC_MSG_ERROR(Cannot find edje: Is edje-config in path?)) - -AC_CONFIG_FILES([ -Makefile -m4/Makefile -src/Makefile -]) - -AC_OUTPUT diff --git a/library.rb b/library.rb new file mode 100644 index 0000000..d1e9817 --- /dev/null +++ b/library.rb @@ -0,0 +1,35 @@ +# $Id: library.rb 327 2005-04-27 14:27:01Z tilman $ + +require "rbconfig" + +class Library + def initialize(name, prefix, dir, lib = name) + @name = name + @prefix = prefix + @dir = dir + @lib = lib + end + + def ldflags + s = "#{ENV["LDFLAGS"]} -L #{@prefix}/lib -L " + + Config::CONFIG["libdir"] + " " + + Config::CONFIG["LIBRUBYARG_SHARED"] + + " -shared -Wl" + s << " -l#{@lib}" unless @lib.nil? + s + end + + def cflags + "#{ENV["CFLAGS"]} -I #{@prefix}/include " + + "-I #{Config::CONFIG['archdir']} " + + "-I #{Config::CONFIG['sitearchdir']} -fPIC" + end + + def so + "#{@dir}/#{@name}.so" + end + + def objects + Dir["#{@dir}/*.c"].map { |f| f.sub(/\.[^.]+$/, ".o") } + end +end diff --git a/m4/Makefile.am b/m4/Makefile.am deleted file mode 100644 index 41ecd10..0000000 --- a/m4/Makefile.am +++ /dev/null @@ -1,3 +0,0 @@ -## $Id: Makefile.am 7 2004-06-19 19:32:33Z tilman $ - -EXTRA_DIST = ac_path_generic.m4 ac_ruby_ext.m4 diff --git a/m4/ac_path_generic.m4 b/m4/ac_path_generic.m4 deleted file mode 100644 index 27b55b3..0000000 --- a/m4/ac_path_generic.m4 +++ /dev/null @@ -1,136 +0,0 @@ -dnl @synopsis AC_PATH_GENERIC(LIBRARY [, MINIMUM-VERSION [, ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND]]]) -dnl -dnl Runs a LIBRARY-config script and defines LIBRARY_CFLAGS and LIBRARY_LIBS -dnl -dnl The script must support `--cflags' and `--libs' args. -dnl If MINIMUM-VERSION is specified, the script must also support the -dnl `--version' arg. -dnl If the `--with-library-[exec-]prefix' arguments to ./configure are given, -dnl it must also support `--prefix' and `--exec-prefix'. -dnl (In other words, it must be like gtk-config.) -dnl -dnl For example: -dnl -dnl AC_PATH_GENERIC(Foo, 1.0.0) -dnl -dnl would run `foo-config --version' and check that it is at least 1.0.0 -dnl -dnl If so, the following would then be defined: -dnl -dnl FOO_CFLAGS to `foo-config --cflags` -dnl FOO_LIBS to `foo-config --libs` -dnl -dnl At present there is no support for additional "MODULES" (see AM_PATH_GTK) -dnl (shamelessly stolen from gtk.m4 and then hacked around a fair amount) -dnl -dnl @author Angus Lees - -AC_DEFUN([AC_PATH_GENERIC], -[dnl -dnl we're going to need uppercase, lowercase and user-friendly versions of the -dnl string `LIBRARY' -pushdef([UP], translit([$1], [a-z], [A-Z]))dnl -pushdef([DOWN], translit([$1], [A-Z], [a-z]))dnl - -dnl -dnl Get the cflags and libraries from the LIBRARY-config script -dnl -AC_ARG_WITH(DOWN-prefix,[ --with-]DOWN[-prefix=PFX Prefix where $1 is installed (optional)], - DOWN[]_config_prefix="$withval", DOWN[]_config_prefix="") -AC_ARG_WITH(DOWN-exec-prefix,[ --with-]DOWN[-exec-prefix=PFX Exec prefix where $1 is installed (optional)], - DOWN[]_config_exec_prefix="$withval", DOWN[]_config_exec_prefix="") - - if test x$DOWN[]_config_exec_prefix != x ; then - DOWN[]_config_args="$DOWN[]_config_args --exec-prefix=$DOWN[]_config_exec_prefix" - if test x${UP[]_CONFIG+set} != xset ; then - UP[]_CONFIG=$DOWN[]_config_exec_prefix/bin/DOWN-config - fi - fi - if test x$DOWN[]_config_prefix != x ; then - DOWN[]_config_args="$DOWN[]_config_args --prefix=$DOWN[]_config_prefix" - if test x${UP[]_CONFIG+set} != xset ; then - UP[]_CONFIG=$DOWN[]_config_prefix/bin/DOWN-config - fi - fi - - AC_PATH_PROG(UP[]_CONFIG, DOWN-config, no) - ifelse([$2], , - AC_MSG_CHECKING(for $1), - AC_MSG_CHECKING(for $1 - version >= $2) - ) - no_[]DOWN="" - if test "$UP[]_CONFIG" = "no" ; then - no_[]DOWN=yes - else - UP[]_CFLAGS="`$UP[]_CONFIG $DOWN[]_config_args --cflags`" - UP[]_LIBS="`$UP[]_CONFIG $DOWN[]_config_args --libs`" - ifelse([$2], , ,[ - DOWN[]_config_major_version=`$UP[]_CONFIG $DOWN[]_config_args \ - --version | sed 's/[[^0-9]]*\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\1/'` - DOWN[]_config_minor_version=`$UP[]_CONFIG $DOWN[]_config_args \ - --version | sed 's/[[^0-9]]*\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\2/'` - DOWN[]_config_micro_version=`$UP[]_CONFIG $DOWN[]_config_args \ - --version | sed 's/[[^0-9]]*\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\3/'` - DOWN[]_wanted_major_version="regexp($2, [\<\([0-9]*\)], [\1])" - DOWN[]_wanted_minor_version="regexp($2, [\<\([0-9]*\)\.\([0-9]*\)], [\2])" - DOWN[]_wanted_micro_version="regexp($2, [\<\([0-9]*\).\([0-9]*\).\([0-9]*\)], [\3])" - - # Compare wanted version to what config script returned. - # If I knew what library was being run, i'd probably also compile - # a test program at this point (which also extracted and tested - # the version in some library-specific way) - if test "$DOWN[]_config_major_version" -lt \ - "$DOWN[]_wanted_major_version" \ - -o \( "$DOWN[]_config_major_version" -eq \ - "$DOWN[]_wanted_major_version" \ - -a "$DOWN[]_config_minor_version" -lt \ - "$DOWN[]_wanted_minor_version" \) \ - -o \( "$DOWN[]_config_major_version" -eq \ - "$DOWN[]_wanted_major_version" \ - -a "$DOWN[]_config_minor_version" -eq \ - "$DOWN[]_wanted_minor_version" \ - -a "$DOWN[]_config_micro_version" -lt \ - "$DOWN[]_wanted_micro_version" \) ; then - # older version found - no_[]DOWN=yes - echo -n "*** An old version of $1 " - echo -n "($DOWN[]_config_major_version" - echo -n ".$DOWN[]_config_minor_version" - echo ".$DOWN[]_config_micro_version) was found." - echo -n "*** You need a version of $1 newer than " - echo -n "$DOWN[]_wanted_major_version" - echo -n ".$DOWN[]_wanted_minor_version" - echo ".$DOWN[]_wanted_micro_version." - echo "***" - echo "*** If you have already installed a sufficiently new version, this error" - echo "*** probably means that the wrong copy of the DOWN-config shell script is" - echo "*** being found. The easiest way to fix this is to remove the old version" - echo "*** of $1, but you can also set the UP[]_CONFIG environment to point to the" - echo "*** correct copy of DOWN-config. (In this case, you will have to" - echo "*** modify your LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf" - echo "*** so that the correct libraries are found at run-time)" - fi - ]) - fi - if test "x$no_[]DOWN" = x ; then - AC_MSG_RESULT(yes) - ifelse([$3], , :, [$3]) - else - AC_MSG_RESULT(no) - if test "$UP[]_CONFIG" = "no" ; then - echo "*** The DOWN-config script installed by $1 could not be found" - echo "*** If $1 was installed in PREFIX, make sure PREFIX/bin is in" - echo "*** your path, or set the UP[]_CONFIG environment variable to the" - echo "*** full path to DOWN-config." - fi - UP[]_CFLAGS="" - UP[]_LIBS="" - ifelse([$4], , :, [$4]) - fi - AC_SUBST(UP[]_CFLAGS) - AC_SUBST(UP[]_LIBS) - - popdef([UP]) - popdef([DOWN]) -]) - diff --git a/m4/ac_ruby_ext.m4 b/m4/ac_ruby_ext.m4 deleted file mode 100644 index da81116..0000000 --- a/m4/ac_ruby_ext.m4 +++ /dev/null @@ -1,51 +0,0 @@ -AC_DEFUN([AC_RUBY_EXT], [ - AC_CHECK_PROG(RUBY, ruby) - - AC_ARG_WITH(ruby, - [ --with-ruby=PATH Location of Ruby executable (default: autodetect)], - [rubybin="$withval"]) - - AC_CHECK_PROGS(rubybin, ruby) - - rubyver=`$rubybin --version 2> /dev/null` - if test -z "$rubyver"; then - AC_MSG_ERROR([ruby binary not found!]) - fi - - AC_MSG_CHECKING(for Ruby library path) - RUBYLIBDIR=`($rubybin -rmkmf -e 'print Config::CONFIG[["libdir"]]') 2> /dev/null` - if test -d "$RUBYLIBDIR"; then - AC_MSG_RESULT([$RUBYLIBDIR]) - else - AC_MSG_RESULT(not found) - AC_MSG_ERROR(Ruby library path not found) - fi - - AC_MSG_CHECKING(for Ruby extension path) - - RUBYDIR=`($rubybin -rmkmf -e 'print Config::CONFIG[["archdir"]]') 2> /dev/null` - if test -d "$RUBYDIR"; then - AC_MSG_RESULT([$RUBYDIR]) - else - AC_MSG_RESULT(not found) - AC_MSG_ERROR(Ruby extension path not found) - fi - - AC_MSG_CHECKING(for Ruby site library path) - RUBYSITEDIR=`($rubybin -rmkmf -e 'print Config::CONFIG[["sitearchdir"]]') 2> /dev/null` - if test -d "$RUBYSITEDIR"; then - AC_MSG_RESULT([$RUBYSITEDIR]) - else - AC_MSG_RESULT(not found) - AC_MSG_ERROR(Ruby site extension path not found) - fi - - AC_MSG_CHECKING(for Ruby shared library) - RUBYLIB=`($rubybin -rmkmf -e 'print Config::CONFIG[["LIBRUBYARG_SHARED"]]') 2> /dev/null` - AC_MSG_RESULT([$RUBYLIB]) - - AC_SUBST(RUBYLIB) - AC_SUBST(RUBYLIBDIR) - AC_SUBST(RUBYDIR) - AC_SUBST(RUBYSITEDIR) -]) diff --git a/src/Makefile.am b/src/Makefile.am deleted file mode 100644 index 06d777c..0000000 --- a/src/Makefile.am +++ /dev/null @@ -1,15 +0,0 @@ -## $Id: Makefile.am 139 2004-10-30 09:41:17Z tilman $ - -AM_CFLAGS = $(EVAS_CFLAGS) $(EDJE_CFLAGS) -INCLUDES = -I$(RUBYDIR) -I$(RUBYSITEDIR) - -ext_LTLIBRARIES = edje.la -extdir = $(RUBYSITEDIR) - -edje_la_SOURCES = rb_edje_main.c rb_edje_main.h \ - rb_edje.c rb_edje.h \ - rb_part.c rb_part.h \ - rb_messages.c rb_messages.h - -edje_la_LIBADD = -L$(RUBYLIBDIR) $(RUBYLIB) $(EVAS_LIBS) $(EDJE_LIBS) -edje_la_LDFLAGS = -module -avoid-version -- 2.30.2