Skip to content

Commit e3f1a85

Browse files
committed
Add new files to the toc.
1 parent b39ba84 commit e3f1a85

File tree

3 files changed

+10
-4
lines changed

3 files changed

+10
-4
lines changed

_toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sections:
66
- file: part_one/01_running
77
- file: part_one/02_hello_world
88
- file: part_one/03_simple_math
9-
- file: part_one/04_input-output.md
9+
- file: part_one/04_input-output
1010
- file: part_one/05_troubleshooting
1111
- file: part_one/exercises_one
1212
- file: part_two/intro
@@ -22,7 +22,7 @@ sections:
2222
- file: part_three/02_structs
2323
- file: part_three/03_header_files
2424
- file: part_three/04_build_systems
25-
- file: part_three/05_combining_with_python.md
25+
- file: part_three/05_combining_with_python
2626
- file: part_three/exercises_three
2727
- file: appendices/intro
2828
sections:

part_one/01_running.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
```{index} compiling
33
```
44

5-
Whereas Python is mostly fairly simple to get working with straight away, C & C++ have a few extra hurdles before you can get the computer to run your code. Your program must be compiled (and sometimes linked to other libraries) to produce a separate executable file, before that file can be run. In this section we present a number of ways of approaching this, listed in order of ease of use.
5+
Whereas Python is mostly fairly simple to get working with straight away, especially in interactive mode, C & C++ have a few extra hurdles before you can get the computer to run your code. Your program must be compiled (and sometimes linked to other external standard or third party libraries) to produce a separate executable file, before that file can be run to solve your problem. In this section we present a number of ways of approaching this, listed in order of ease of use.
66

77
## Web based solutions
88
```{index} compiling:web-based

part_three/04_build_systems.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,13 @@ In general there are two steps involved:
1313
1. Making sure the the path for the header files which contain the declarations for the library are available to the compiler
1414
2. Making sure the path for the library files which contain the compiled code for the library are available to the linker.
1515

16-
How to do this depends on the build system you are using.
16+
How to do this depends on the build system you are using. We will give a short explanation here, or you can look at the following tutorials for more
17+
18+
19+
- [Visual Studio](https://docs.microsoft.com/en-us/cpp/build/walkthrough-creating-and-using-a-dynamic-link-library-cpp?view=msvc-160)
20+
21+
- [Make](https://www.cs.colby.edu/maxwell/courses/tutorials/maketutor/)
22+
- [CMake](https://cmake.org/cmake/help/latest/guide/tutorial/index.html)
1723

1824
## Visual Studio (Windows only)
1925

0 commit comments

Comments
 (0)