f

CMakeSettings.json

@@ -0,0 +1,15 @@
+{
+  "configurations": [
+    {
+      "name": "x64-Debug",
+      "generator": "Ninja",
+      "configurationType": "Debug",
+      "inheritEnvironments": [ "msvc_x64_x64" ],
+      "buildRoot": "${projectDir}\\out\\build\\${name}",
+      "installRoot": "${projectDir}\\out\\install\\${name}",
+      "cmakeCommandArgs": "",
+      "buildCommandArgs": "",
+      "ctestCommandArgs": ""
+    }
+  ]
+}

NouVeL/CMakeLists.txt

@@ -4,6 +4,6 @@
 cmake_minimum_required (VERSION 3.8)
 
 # Add source to this project's executable.
-add_executable (NouVeL "NouVeL.cpp" "NouVeL.h")
+add_executable (NouVeL "NouVeL.cpp"  "NVL.cpp" "NVL.h")
 
 # TODO: Add tests and install targets if needed.

NouVeL/NouVeL.cpp

@@ -1,7 +1,14 @@
-#include "NouVeL.h"
+#include "NVL.h"
 
 int main()
 {
-	std::cout << "Hello CMake." << std::endl;
+	const std::string PJ_DIR = "E:\\Archive\\Projects\\NouVeL\\";
+	
+	NVL::Tree tree;
+	if (NVL::parse_NVL(tree, PJ_DIR + "myfile.txt"))
+		return 1;
+
+	tree.Print_Tree(0);
+
 	return 0;
 }

NouVeL/NouVeL.h

@@ -1,4 +0,0 @@
-#pragma once
-
-// Switch to FMT
-#include <iostream>

documentation/implementation.md

@@ -1,4 +1,4 @@
 # Implementation
 It is certainly not a good idea to parse and interpret NVL files on the go. To reduce this overhead, I'm still thinking what I should do.
 
-Candidate: compile NVL files into another format (perhaps binary?) that is fast to use on the go
+Candidate: compile NVL files into another format (perhaps binary?) that is fast to use on the go