updated to get closer to building using cygwin, which is difficult because

[feisty_meow.git] / nucleus / tools / clam_tools / write_build_config.cpp

diff --git a/nucleus/tools/clam_tools/write_build_config.cpp b/nucleus/tools/clam_tools/write_build_config.cpp
index 6a9a30b5157a553d7f4c6e49889f4914066644a1..d3b9a812cad979196255538871c937366b474f36 100644 (file)
--- a/nucleus/tools/clam_tools/write_build_config.cpp
+++ b/nucleus/tools/clam_tools/write_build_config.cpp
@@ -208,10 +208,10 @@ if (read < 1) LOG("why is existing header contentless?");
     byte_filer build_header(filename, "wb");
     if (!build_header.good())
       non_continuable_error(static_class_name(), func, astring("failed to create "
-          "build header file in ") + build_header.filename());
+          "build header file in ") + build_header.name());
     build_header.write(new_contents);
     LOG(astring(static_class_name()) + ": wrote config to "
-        + build_header.filename());
+        + build_header.name());
   } else {
     // nothing has changed.
 //    LOG(astring(static_class_name()) + ": config already up to date in "
@@ -263,7 +263,7 @@ int write_build_config::execute()
   byte_filer ini(fname, "r");
   if (!ini.good())
     non_continuable_error(static_class_name(), func, astring("failed to open "
-        "build configuration file for reading at ") + ini.filename());
+        "build configuration file for reading at ") + ini.name());
 //hmmm: parameterize the build ini thing above!
 
   // now we build strings that represents the output files we want to create.