junrushao commented on code in PR #170:
URL: https://github.com/apache/tvm-ffi/pull/170#discussion_r2442574965


##########
examples/quickstart/CMakeLists.txt:
##########
@@ -0,0 +1,52 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+cmake_minimum_required(VERSION 3.20)
+project(tvm_ffi_example)
+
+option(EXAMPLE_NAME "Which example to build (cpp/cuda)" "cpp")
+message(STATUS "Building example: ${EXAMPLE_NAME}")
+
+find_package(tvm_ffi CONFIG)
+if (NOT tvm_ffi_FOUND)
+  message(FATAL_ERROR "Unable to find tvm_ffi. Set `tvm_ffi_DIR` with 
`tvm-ffi-config --cmakedir`")
+endif ()
+
+if (EXAMPLE_NAME STREQUAL "cpp")

Review Comment:
   given that we now have `./run_all_cpu.sh` and `./run_all_cuda.sh`, which 
builds all the targets, i believe it's necessary here.
   
   most importantly, i believe putting different examples under different if 
branches gives better clarity, because it shortens the LOC needed to read for 
end users to understand specific logics.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to