From: stephan b. <st...@s1...> - 2004-12-23 00:06:16
|
Yo, Christian! Okay, i've got toc installed and configuring, but won't have all of the required tests done before late Thursday or maybe Friday. Here are things which you need to know: a) ./configure is the toc-powered configure script. When using autotools you will overwrite configure. This is exactly what we want, as it means "by default use toc, otherwise fall back to autotools". Be sure not to commit your configure script if you auto-gen it! b) All configure tests go into configure.pclasses2. That is called by configure. configure.toc is a middleman stub - ignore it. c) toc now creates the Makefiles, with Makefile.toc holding the "real" make code. toc just generates stubs which look like: #!/usr/bin/make -f # Automatically generated by configure. # Do not edit this file: put your code in Makefile.toc. include Makefile.toc DIST_FILES += Makefile.toc DIST_FILES := $(filter-out Makefile,$(DIST_FILES)) # ^^^^ toc automatically adds Makefile to DIST_FILES. DISTCLEAN_FILES += Makefile The Makefile.toc implementations are your standard Makefiles. Autotools will overwrite toc's Makefiles, which is exactly what we want. Both trees can co-exist while i piddle around with toc and figure out if it's really what we want to use. :) So, what this all essentially means is: You may continue working on the tree as if toc didn't exist, and i'll let you know once it's fully buildable. The transition from AT to toc will then be transparent for the builder. See ya! -- ----- st...@s1... http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts |