# $Id: Makefile.in,v 1.1.1.1 2007/10/19 05:16:17 hww3 Exp $
@make_variables@
VPATH=@srcdir@:@srcdir@/../..:../..

# things we should define.

# the .o files that we need to generate for the module
# rules will automatically generate these from .c, .cmod, .m and .mmod files.
OBJS=altlinux/hyphen.o altlinux/hnjalloc.o altlinux/csutil.o hyphenate.o

# the module directory we put things into. it should be a directory path
# of .pmod directories, and this must end with a trailing slash.
MODDIR=Public.pmod/Tools.pmod/Language.pmod

# the module name the resulting dynamic and/or pike module will be 
# installed as. note that it's just a module or class name without extension.
MODNAME=Hyphenate

# the pike portion of the module. may be either a file or a directory
# containing multiple .pike and .pmod files.
MODULE_PMOD_IN=module.pmod.in

# used by the module repository to scan for autodocs. should be the 
# list of non pike files containing autodoc markup (ie cmod or c files). 
AUTODOC_SRC_IN=

# the module name note that there is no error checking, so all of these
# related variables should agree.
MODULE_NAME=Public.Tools.Language.Hyphenate

# the module name, with periods replaced with underscores. used to 
# generate the module distribution.
MODULE_DIR_NAME=Public_Tools_Language_Hyphenate

# need i say more?
MODULE_LICENSE=GPL

# we shouldn't need to do anything to the rest of the file.

CFLAGS=@CMOD_CFLAGS@
LDFLAGS=@CMOD_LIBS@

MODULE_LDFLAGS=@LDFLAGS@

CONFIG_HEADERS=@CONFIG_HEADERS@

@dynamic_module_makefile@
@dependencies@

release:
	cvs rtag -D now RELEASE_1_${MIN} pike_modules/${MODULE_DIR_NAME}
	cvs export -d ${MODULE_DIR_NAME}-1.${MIN} -r RELEASE_1_${MIN} pike_modules/${MODULE_DIR_NAME}
	cd ${MODULE_DIR_NAME}-1.${MIN} && \
	pike -x module --autoheader && pike -x module --autoconf && \
	rm -rf autom4*
	cp *.c ${MODULE_DIR_NAME}-1.${MIN}
	gtar czvf ${MODULE_DIR_NAME}-1.${MIN}.tar.gz  ${MODULE_DIR_NAME}-1.${MIN}
	pike upload_module_version.pike ${MODULE_NAME} 1.${MIN} "${MODULE_LICENSE}"