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

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

Revision: 7400
          http://sourceforge.net/p/teem/code/7400
Author:   kindlmann
Date:     2025-09-10 23:37:05 +0000 (Wed, 10 Sep 2025)
Log Message:
-----------
rename

Added Paths:
-----------
    teem/trunk/UseTeemCMakeDemo/00-INFO.txt

Removed Paths:
-------------
    teem/trunk/UseTeemCMakeDemo/00-Readme.txt

Copied: teem/trunk/UseTeemCMakeDemo/00-INFO.txt (from rev 7399, teem/trunk/UseTeemCMakeDemo/00-Readme.txt)
===================================================================
--- teem/trunk/UseTeemCMakeDemo/00-INFO.txt	                        (rev 0)
+++ teem/trunk/UseTeemCMakeDemo/00-INFO.txt	2025-09-10 23:37:05 UTC (rev 7400)
@@ -0,0 +1,39 @@
+This is a simple demo of how another C program can use CMake to link
+with a CMake-built Teem (it also reflects how I (GLK) am belatedly
+understanding how CMake works).
+
+Steps:
+
+1) Set TEEM_DIR to the path to where CMake installed Teem.  There should be
+`bin`, `include`, `lib`, subdirectories, and the `lib/cmake` will record how
+CMake built Teem.  Then:
+
+  ls $TEEM_DIR
+
+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:
+
+  cmake -S . -B build \
+     -DCMAKE_PREFIX_PATH=$TEEM_DIR \
+     -DCMAKE_INSTALL_PREFIX=install
+
+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.
+
+3) To build in a way that is agnostic w.r.t. build system:
+
+  cmake --build build
+
+which means: run the "build" step (first "--build") in the local `build`
+subdirectory (second "build").  Or if you like running make:
+
+  (cd build; make)
+
+4) To install:
+
+  cmake --install build

Deleted: teem/trunk/UseTeemCMakeDemo/00-Readme.txt
===================================================================
--- teem/trunk/UseTeemCMakeDemo/00-Readme.txt	2025-09-10 19:32:15 UTC (rev 7399)
+++ teem/trunk/UseTeemCMakeDemo/00-Readme.txt	2025-09-10 23:37:05 UTC (rev 7400)
@@ -1,39 +0,0 @@
-This is a simple demo of how another C program can use CMake to link
-with a CMake-built Teem (it also reflects how I (GLK) am belatedly
-understanding how CMake works).
-
-Steps:
-
-1) Set TEEM_DIR to the path to where CMake installed Teem.  There should be
-`bin`, `include`, `lib`, subdirectories, and the `lib/cmake` will record how
-CMake built Teem.  Then:
-
-  ls $TEEM_DIR
-
-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:
-
-  cmake -S . -B build \
-     -DCMAKE_PREFIX_PATH=$TEEM_DIR \
-     -DCMAKE_INSTALL_PREFIX=install
-
-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.
-
-3) To build in a way that is agnostic w.r.t. build system:
-
-  cmake --build build
-
-which means: run the "build" step (first "--build") in the local `build`
-subdirectory (second "build").  Or if you like running make:
-
-  (cd build; make)
-
-4) To install:
-
-  cmake --install build

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