[Teem-commit] SF.net SVN: teem:[7401] teem/trunk/UseTeemCMakeDemo

[<kin...@us...>]

Revision: 7401
          http://sourceforge.net/p/teem/code/7401
Author:   kindlmann
Date:     2025-09-10 23:51:42 +0000 (Wed, 10 Sep 2025)
Log Message:
-----------
tweaks

Modified Paths:
--------------
    teem/trunk/UseTeemCMakeDemo/00-INFO.txt
    teem/trunk/UseTeemCMakeDemo/CMakeLists-v2.txt

Modified: teem/trunk/UseTeemCMakeDemo/00-INFO.txt
===================================================================
--- teem/trunk/UseTeemCMakeDemo/00-INFO.txt	2025-09-10 23:37:05 UTC (rev 7400)
+++ teem/trunk/UseTeemCMakeDemo/00-INFO.txt	2025-09-10 23:51:42 UTC (rev 7401)
@@ -12,28 +12,32 @@
 
 should show `bin`, `include`, `lib`.
 
-2) The following will create a `build` subdirectory right here where testio.c
-is, doing the configure and generate steps of CMake:
+2) The following will create a `localbuild` subdirectory right here where
+testio.c is, doing the configure and generate steps of CMake:
 
-  cmake -S . -B build \
+  cmake -S . -B buildhere \
      -DCMAKE_PREFIX_PATH=$TEEM_DIR \
-     -DCMAKE_INSTALL_PREFIX=install
+     -DCMAKE_INSTALL_PREFIX=installhere
 
 The `.` argument to `cmake -S` is the path to the source directory, and the
-`build` argument to `cmake -B` is the path to the new testio build directory.
-After the `find_package` in ./CMakeLists.txt runs, CMake will set its own
-`Teem_DIR` variable to $TEEM_DIR. The `install` local (relative) path will be
-the subdirectory that CMake will install into later.
+`buildhere` argument to `cmake -B` is the path of the to-be-created directory
+to will contain all of CMake's work and files for building this
+"DemoOfUsingTeem" project (named by the `project(DemoOfUsingTeem LANGUAGES C)`
+line in CMakeLists.txt).  After the `find_package` in ./CMakeLists.txt runs,
+CMake will set its own `Teem_DIR` variable to $TEEM_DIR. The `installhere` path
+is where CMake will install things in when asked to install.
 
 3) To build in a way that is agnostic w.r.t. build system:
 
-  cmake --build build
+  cmake --build buildhere
 
-which means: run the "build" step (first "--build") in the local `build`
-subdirectory (second "build").  Or if you like running make:
+which means: run the "build" step (first "--build") in the `buildhere`
+directory.  Or if you like running make directly:
 
-  (cd build; make)
+  (cd buildhere; make)
 
 4) To install:
 
-  cmake --install build
+  cmake --install buildhere
+
+which runs CMake's "install" process on whatever has been built in "buildhere"

Modified: teem/trunk/UseTeemCMakeDemo/CMakeLists-v2.txt
===================================================================
--- teem/trunk/UseTeemCMakeDemo/CMakeLists-v2.txt	2025-09-10 23:37:05 UTC (rev 7400)
+++ teem/trunk/UseTeemCMakeDemo/CMakeLists-v2.txt	2025-09-10 23:51:42 UTC (rev 7401)
@@ -6,7 +6,7 @@
 cmake_minimum_required(VERSION 3.14)
 
 # Set (demo) project name, initialize compiler detection and compiler flags
-project(TestNrrdIO LANGUAGES C)
+project(DemoOfUsingTeem LANGUAGES C)
 
 # Find Teem (must be installed in CMAKE_PREFIX_PATH or default system paths)
 find_package(Teem REQUIRED)

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.