summaryrefslogtreecommitdiffstats
path: root/Lib/distutils/command/build.py
Commit message (Collapse)AuthorAgeFilesLines
* Fix forMichael W. Hudson2001-12-101-1/+2
| | | | | | | | [ #477371 ] build_scripts can use wrong #! line scripts now get "built" into a directory build/scripts-$(PYTHON_VERSION)/
* Untabified.Greg Ward2000-10-141-1/+1
|
* Standardized whitespace around function calls.Greg Ward2000-09-301-6/+6
|
* Changed to use the 'sub-commands' machinery:Greg Ward2000-09-301-21/+29
| | | | | | - added 'sub_commands' class attr - added 'has_*()' predicates referenced by the sub-command list - rewrote 'run()' so it's a trivial loop over relevant sub-commands
* Added 'boolean_options' list to support config file parsing.Greg Ward2000-09-251-0/+2
|
* Tweaked the build temp dir names again.Greg Ward2000-09-161-8/+4
|
* Include the Python version in the platform-specific build directories:Greg Ward2000-09-161-2/+4
| | | | | | with the recent change in 'get_platform()', we now have directory names like "build/lib-1.5-linux-i586". Idea and original patch by Rene Liebscher.
* Changed so all the help-generating functions are defined, at module-level,Greg Ward2000-06-241-1/+6
| | | | | | | in the module of the command classes that have command-specific help options. This lets us keep the principle of lazily importing the ccompiler module, and also gets away from defining non-methods at class level.
* Stylistic/formatting changes to Rene Liebscher's '--help-xxx' patch.Greg Ward2000-06-241-1/+2
|
* Patch from Rene Liebscher: this adds "--help-foo" options to list theGreg Ward2000-06-071-0/+5
| | | | | | | | | | values that "--foo" can take for various commands: eg. what formats for "sdist" and "bdist", what compilers for "build_ext" and "build_clib". I have *not* reviewed this patch; I'm checking it in as-is because it also fixes a paper-bag-over-head bug in bdist.py, and because I won't have time to review it properly for several days: so someone else can test it for me, instead!
* Some far-reaching naming changes:Greg Ward2000-05-271-4/+4
| | | | | | | * Command method 'find_peer()' -> 'get_finalized_command()' * Command method 'run_peer()' -> 'run_command()' Also deleted the 'get_command_option()' method from Command, and fixed the one place where it was used (in "bdist_dumb").
* Use Distribution's 'has_scripts()' method instead of directly accessingGreg Ward2000-05-251-1/+1
| | | | its 'scripts' attribute.
* Bastian Kleineidam: the "build_scripts" command and changesGreg Ward2000-05-251-0/+8
| | | | | | | | | | | | | | | | | | | | | | | necessary to support it. Details: - build command additionally calls build_scripts - build_scripts builds your scripts in 'build/scripts' and adjusts the first line if it begins with "#!" and ends with "python", optionally ending with commandline options (like -O, -t ...). Adjusting means we write the current path to the Python interpreter in the first line. - install_scripts copies the scripts to the install_scripts dir - install_data copies your data_files in install_data. You can supply individual directories for your data_files: data_files = ['doc/info.txt', # copy this file in install_scripts dir ('testdata', ['a.dat', 'b.dat']), # copy these files in # install_scripts/testdata ('/etc', ['packagerc']), # copy this in /etc. When --root is # given, copy this in rootdir/etc ] So you can use the --root option with absolute data paths.
* Normalized all the end-of-class lines.Greg Ward2000-05-251-1/+1
|
* Fix from Lyle Johnson: add the '--compiler' option.Gregory P. Smith2000-05-121-1/+4
|
* Delete some debugging print statements.Greg Ward2000-04-101-2/+0
|
* Added '--force' option -- very clear what it means for building (ignoreGreg Ward2000-04-101-0/+5
| | | | | timestamps), so every build_* command has 'self.force', which follows the 'build' command if not set by the user.
* Use the new 'has_pure_modules()', 'has_ext_modules()', 'has_c_libraries()'Greg Ward2000-03-291-3/+3
| | | | methods of Distribution instead of grovelling directly in self.distribution.
* Renamed 'build_lib' command to 'build_clib':Greg Ward2000-03-021-1/+1
| | | | | | * replaced build_lib.py with build_clib.py * renamed the class in build_clib.py * changed all references to 'build_lib' command in other command classes
* Changed '__rcsid__' to '__revision__'.Greg Ward2000-03-021-1/+1
|
* Build reorg:Greg Ward2000-03-011-12/+43
| | | | | | * 'build_lib' -> 'build_purelib' * new 'build_lib' and 'build_temp' options * use 'get_platform()' to initialize 'build_platlib' and 'build_temp'
* Renamed 'set_default_options()' to 'initialize_options()', andGreg Ward2000-02-181-2/+2
| | | | 'set_final_options()' to 'finalize_options()'.
* Renamed all 'options' class attributes to 'user_options'.Greg Ward2000-02-181-9/+10
|
* Renamed all command classes so they're exactly the same as the name of theGreg Ward2000-02-181-1/+1
| | | | | command itself: no more of this "FooBar class for foo_bar command" silliness.
* Added 'debug' option (just there for 'build_ext' and 'build_lib' commandsGreg Ward2000-02-091-0/+3
| | | | to fallback to if the user doesn't set it for those commands.
* Run the 'build_lib' command before building extensions, if necessary.Greg Ward2000-02-051-0/+6
|
* Added 'description' class attribute to every command class (to help theGreg Ward2000-01-301-0/+2
| | | | | | | '--help-commands' option). Shuffled imports around in a few command modules to avoid expensive up-front import of sysconfig (and resulting delays in generating list of all commands).
* Renamed many options to be consistent across commands.Greg Ward1999-09-291-15/+16
| | | | | | Tweaked some help strings to be consistent with documentation. Don't call 'set_final_options()' in 'run()' anymore -- that's now guaranteed to be taken care of for us by the Distribution instance.
* Only run build_py if we have pure Python modules, and build_ext if weGreg Ward1999-09-211-5/+9
| | | | have extension modules.
* Now run 'build_ext'.Greg Ward1999-09-131-2/+2
| | | | Default platform-specific build directory changed to 'build/platlib'.
* Rearranged things so that compilation of .py files is the responsibilityGreg Ward1999-05-021-7/+0
| | | | | | | | | of the 'install_py' command rather than 'build_py'. Obviously, this meant that the 'build_py' and 'install_py' modules had to change; less obviously, so did 'install' and 'build', since these higher-level commands must make options available to control the lower-level commands, and some compilation-related options had to migrate with the code.
* First checkin of real Distutils command modules.Greg Ward1999-03-221-0/+56