Projects/laydi
Projects
/
laydi
Archived
7
0
Fork 0
Code Issues Pull Requests Activity
This repository has been archived on 2024-07-04. You can view files and clone it, but cannot push or open issues or pull requests.
laydi/doc/Makefile

21 lines
429 B
Makefile
Raw Normal View History

Added documentation directory with a Makefile to generate source code documentation. This adds python-epydoc as a build dependency.
2006-10-17 17:06:24 +02:00
Lots of changes in structure to make it possible to package the program while still allowing workflows to be placed in several locations in the file system. The installation procedure is now ./configure && make install configure will run m4 on fluents/paths.py.m4, Makefile.m4 and doc/Makefile.m4 so that the installation system and the program will know where some important directories are located. The paths.py.m4 and consequently also pahts.py files are just listings of directories configured during install. I did this to separate these from all other files so that as little as possible is touched by m4. It is still necessary to do an install now to get the program to run in a clean checkout. Workflows can now be placed anywhere in the system. This is done by setting the workflowdir variable in the configuration file. All workflow directories, separated by semicolons, are added to the python path. The use of setup.py is now deprecated.
2008-12-05 01:12:49 +01:00
DOC_DIR=/home/einarr/src/fluents-8/debian/fluents/usr/share/doc/laydi
Added documentation directory with a Makefile to generate source code documentation. This adds python-epydoc as a build dependency.
2006-10-17 17:06:24 +02:00
all: html
html:
@echo ----------------
@echo Generating epydoc html code documentation.
@echo See epydoc-html.log for epydoc log.
@echo ----------------
Fixed makefile to not use lots of space on inherited function documentation.
2007-08-02 12:04:06 +02:00
epydoc --html --inheritance listed -o html/ ../fluents 2> epydoc-html.log
Added documentation directory with a Makefile to generate source code documentation. This adds python-epydoc as a build dependency.
2006-10-17 17:06:24 +02:00
Lots of changes in structure to make it possible to package the program while still allowing workflows to be placed in several locations in the file system. The installation procedure is now ./configure && make install configure will run m4 on fluents/paths.py.m4, Makefile.m4 and doc/Makefile.m4 so that the installation system and the program will know where some important directories are located. The paths.py.m4 and consequently also pahts.py files are just listings of directories configured during install. I did this to separate these from all other files so that as little as possible is touched by m4. It is still necessary to do an install now to get the program to run in a clean checkout. Workflows can now be placed anywhere in the system. This is done by setting the workflowdir variable in the configuration file. All workflow directories, separated by semicolons, are added to the python path. The use of setup.py is now deprecated.
2008-12-05 01:12:49 +01:00
install:
find html/ -type f -exec install -m 644 -D '{}' ${DOC_DIR}/'{}' \;
Expanded some documentation. Added clean target to doc Makefile.
2006-10-17 19:18:46 +02:00
clean:
-rm -rf html
-rm epydoc-html.log
Added documentation directory with a Makefile to generate source code documentation. This adds python-epydoc as a build dependency.
2006-10-17 17:06:24 +02:00
Lots of changes in structure to make it possible to package the program while still allowing workflows to be placed in several locations in the file system. The installation procedure is now ./configure && make install configure will run m4 on fluents/paths.py.m4, Makefile.m4 and doc/Makefile.m4 so that the installation system and the program will know where some important directories are located. The paths.py.m4 and consequently also pahts.py files are just listings of directories configured during install. I did this to separate these from all other files so that as little as possible is touched by m4. It is still necessary to do an install now to get the program to run in a clean checkout. Workflows can now be placed anywhere in the system. This is done by setting the workflowdir variable in the configuration file. All workflow directories, separated by semicolons, are added to the python path. The use of setup.py is now deprecated.
2008-12-05 01:12:49 +01:00