diff options
| -rw-r--r-- | docs/source/buildfile.rst | 6 | ||||
| -rw-r--r-- | xnt/commands/target.py | 4 |
2 files changed, 5 insertions, 5 deletions
diff --git a/docs/source/buildfile.rst b/docs/source/buildfile.rst index cec8e30..8200fff 100644 --- a/docs/source/buildfile.rst +++ b/docs/source/buildfile.rst @@ -134,16 +134,16 @@ Build Properties As mentioned in :ref:`xntPropertiesParameters`, Xnt can accept parameters from the command line and pass them into the build file. Xnt doesn't necessarily -expect the dictionary (named `properties`) to exist; but if you ever intend to +expect the dictionary (named `PROPERTIES`) to exist; but if you ever intend to use it, it will have to be defined one way or another (either to an empty dictionary or actually hold values). For example, to define an empty -`properties` dictionary, one could write their build file as such:: +`PROPERTIES` dictionary, one could write their build file as such:: #!/usr/bin/env python from xnt import target - properties = {} + PROPERTIES = {} @target def foo(): diff --git a/xnt/commands/target.py b/xnt/commands/target.py index 0520c74..dbf46fe 100644 --- a/xnt/commands/target.py +++ b/xnt/commands/target.py @@ -58,13 +58,13 @@ class TargetCommand(Command): def __get_properties(): """Return the properties dictionary of the build module""" try: - return getattr(self.build, "properties") + return getattr(self.build, "PROPERTIES") except AttributeError: return None try: if props and len(props) > 0: setattr(self.build, - "properties", + "PROPERTIES", process_params(props, __get_properties())) target = getattr(self.build, target_name) error_code = target() |