[Avida-cvs] [Avida2-svn] r130 - branches/developers/kaben-organism-scope/source/python

[kaben at myxo.css.msu.edu]

Author: kaben
Date: 2005-04-08 21:45:40 -0400 (Fri, 08 Apr 2005)
New Revision: 130

Modified:
   branches/developers/kaben-organism-scope/source/python/CMakeLists.txt
Log:

* Fixes in process of renaming AvidaEd to Avida-ED.



Modified: branches/developers/kaben-organism-scope/source/python/CMakeLists.txt
===================================================================
--- branches/developers/kaben-organism-scope/source/python/CMakeLists.txt	2005-04-09 01:45:20 UTC (rev 129)
+++ branches/developers/kaben-organism-scope/source/python/CMakeLists.txt	2005-04-09 01:45:40 UTC (rev 130)
@@ -21,21 +21,21 @@
 
   IF(UNIX)
     IF(APPLE)
-      CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/AvidaEd-osx.py ${CMAKE_CURRENT_BINARY_DIR}/AvidaEd.py COPYONLY)
+      CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/AvidaEd-osx.py ${CMAKE_CURRENT_BINARY_DIR}/Avida-ED.py COPYONLY)
       CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/setup_osx.py.in ${CMAKE_CURRENT_BINARY_DIR}/setup.py)
 
       # CMake custom targets often produce strange and idiosyncratic
       # output in Makefiles, and this has become a real pain. I would
       # like a different build system again.
       # @kgn
-      ADD_CUSTOM_TARGET(BUILD_AvidaEd ALL DEPENDS ${EXECUTABLE_OUTPUT_PATH}/AvidaEd.app)
+      ADD_CUSTOM_TARGET(BUILD_AvidaEd ALL DEPENDS ${EXECUTABLE_OUTPUT_PATH}/Avida-ED.app)
       #ADD_CUSTOM_TARGET(
       #  ${CMAKE_CURRENT_BINARY_DIR}/build
       #  ALL
       #  DEPENDS ${EXECUTABLE_OUTPUT_PATH}/AvidaEd.app/Contents/MacOS/AvidaEd
       #)
       ADD_CUSTOM_COMMAND(
-        OUTPUT ${EXECUTABLE_OUTPUT_PATH}/AvidaEd.app
+        OUTPUT ${EXECUTABLE_OUTPUT_PATH}/Avida-ED.app
         COMMAND ${PYTHON_EXE}
         DEPENDS ${LIBRARY_OUTPUT_PATH}/libPyAvidaRepairHacks.dylib
         ARGS setup.py py2app