Crystal Space External Project Template Creation

This form will generate a basic Crystal Space project for you, complete with configuration (Autoconf) and build system (Jam and MSVC).
You can achieve the same using $CRYSTAL/scripts/jamtemplate/createproject.sh from your CS copy.
The resulting archive is in tar.bz2 format; if you can't open it, use for example 7-zip.

Project Choose a project name. We need a short form of the name for use in directory and file names. The short name should be lowercase (though not strictly required) and must not contain any special characters or spaces. We also need a long name for use in help messages and the README file. For example, if you project is called "Space Fighters - Revenge for Ducky", then you may want to choose a short name "spacefighters", and a long name "Space Fighters - Revenge for Ducky". You may also provide an address for the project's home page. Please specify a complete URI. For example: http://www.spacefighter.org/
Contact The information about the author is mentioned in the README file and in the configuration script so that people see a support address when they invoke "./configure --help". When asked for the copyright information, type the full copyright notice as you wish it to appear in the generated files. For instance:
Copyright (C)2009 by Duffer McFluffer
License The meta-information which describes a plugin module can be embedded directly into the plugin itself on some platforms or laid down alongside the plugin in a separate *.csplugin file. On Unix, Crystal Space utilizes its own ELF-based reader to extract embedded meta-information from plugin modules. If the ELF-based reader is not available for some reason (such as missing elf.h), then Crystal Space falls back to using the libbfd library for reading embedded meta-information. The libbfd library carries a GPL license, therefore it can be used legally only with projects also carrying a GPL or GPL-compatible license. If your project is not compatible with GPL, then Crystal Space needs to be instructed not to fallback to using libbfd for extracting meta-information if the built-in ELF reader is unavailable. Avoding libbfd, in this case, will prevent its GPL license from infecting your non-GPL project. Your response to this question controls whether or not it is safe to fall back to using libbfd in the event that the ELF-based reader is unusable. (Note, though, that the end-user can manually override the embedding default via the configure script's --enable-meta-info-embedding option.)
If you are unsure of the answer, then respond "no". yes no
Dependencies The Crystal Entity Layer (CEL) is a set of classes and modules which layer game-oriented facilities atop Crystal Space. The Autoconf configuration script and Jam build system can be set up to work with CEL if your project will utilize this SDK. yes no trunk 1.4 1.2.1