Skip to content

Commit

Permalink
Updates to lab 12 finalized.
Browse files Browse the repository at this point in the history
  • Loading branch information
Mark Floryan committed Apr 25, 2019
1 parent 2ae396a commit 317ca07
Show file tree
Hide file tree
Showing 4 changed files with 19 additions and 19 deletions.
3 changes: 1 addition & 2 deletions labs/lab12/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,7 @@ <h3 id="pre-lab">Pre-lab</h3>
</ol>
<h3 id="in-lab">In-lab</h3>
<ol style="list-style-type: decimal">
<li>While we are required to have you show up to lab today, we won't be taking up much of your time.</li>
<li>However, note that you still have to attend lab in Olsson 001 (or Rice 340), however briefly, and submit your file for this lab from there.</li>
<li>For this in-lab, we won't be taking up much of your time.</li>
<li>How much wrath do you have to vent about the course? How much did it ruin your life? How much did you learn? Let us know -- fill out the course surveys! You can access them through Collab (or SIS? We aren't actually given any information about how students access the course evaluations). On a more serious note, we are very interested in your feedback about the course, and would greatly appreciate your filling out of the course evaluation.</li>
<li>The one text file you must submit for this lab is called suggestion.txt, and it should contain one <em>constructive</em> suggestion as to how to improve this course. Here, constructive means that it could actually be accomplished (so you can't just say &quot;ditch C++&quot; without some sort of suggestion as to what to place in its stead).</li>
<li>Any other comments to pass on? There is always the Collab anonymous feedback for more comments as well.</li>
Expand Down
15 changes: 7 additions & 8 deletions labs/lab12/index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -32,14 +32,13 @@ Procedure

### In-lab ###

1. While we are required to have you show up to lab today, we won't be taking up much of your time.
2. However, note that you still have to attend lab in Olsson 001 (or Rice 340), however briefly, and submit your file for this lab from there.
3. How much wrath do you have to vent about the course? How much did it ruin your life? How much did you learn? Let us know -- fill out the course surveys! You can access them through Collab (or SIS? We aren't actually given any information about how students access the course evaluations). On a more serious note, we are very interested in your feedback about the course, and would greatly appreciate your filling out of the course evaluation.
4. The one text file you must submit for this lab is called suggestion.txt, and it should contain one *constructive* suggestion as to how to improve this course. Here, constructive means that it could actually be accomplished (so you can't just say "ditch C++" without some sort of suggestion as to what to place in its stead).
5. Any other comments to pass on? There is always the Collab anonymous feedback for more comments as well.
6. There will be a review session for the final; details to be announced later.
7. Make sure you know when the final exam is!!!
8. File to submit: suggestion.txt
1. For this in-lab, we won't be taking up much of your time.
2. How much wrath do you have to vent about the course? How much did it ruin your life? How much did you learn? Let us know -- fill out the course surveys! You can access them through Collab (or SIS? We aren't actually given any information about how students access the course evaluations). On a more serious note, we are very interested in your feedback about the course, and would greatly appreciate your filling out of the course evaluation.
3. The one text file you must submit for this lab is called suggestion.txt, and it should contain one *constructive* suggestion as to how to improve this course. Here, constructive means that it could actually be accomplished (so you can't just say "ditch C++" without some sort of suggestion as to what to place in its stead).
4. Any other comments to pass on? There is always the Collab anonymous feedback for more comments as well.
5. There will be a review session for the final; details to be announced later.
6. Make sure you know when the final exam is!!!
7. File to submit: suggestion.txt


### Post-lab ###
Expand Down
11 changes: 6 additions & 5 deletions tutorials/12-objc/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -46,11 +46,12 @@ <h3 id="differences-with-the-wikibooks-tutorials">Differences with the Wikibooks
<p><strong>Difference 2: the super-class</strong></p>
<p>We have included (well, imported) a different file, and thus can no longer subclass from <code>Object</code>. Thus, we must change the super class name from <code>Object</code> to <code>NSObject</code>. This is line 3 of the Point.h class in the <a href="http://en.wikibooks.org/wiki/Objective-C_Programming/syntax">Objective C Syntax</a> tutorial on Wikibooks.</p>
<p><strong>Difference 3: compilation command</strong></p>
<p>As our programs are now more complicated than just a &quot;hello world&quot;, the compilation line is longer as well. The compilation command for Linux machines (such as the VirtualBox image) is:</p>
<pre><code>clang -I /usr/include/GNUstep/ *.m -lobjc -lgnustep-base</code></pre>
<p>On some Linux systems (specificially, on 64-bit Ubuntu 16.04 systems), we had to use the following compilation line; if the one above does not work, then try this one:</p>
<pre><code>clang -I /usr/include/GNUstep/ -I /usr/lib/gcc/x86_64-linux-gnu/5/include/ *.m -lobjc -lgnustep-base</code></pre>
<p>On Mac OS X, the compilation command is much simpler, and is what was shown above:</p>
<p>As our programs are now more complicated than just a &quot;hello world&quot;, the compilation line is longer as well. The compilation command for Linux machines (such as VirtualBox image) is:</p>
<pre><code>clang -I /usr/include/GNUstep/ -I /usr/lib/gcc/x86_64-linux-gnu/7/include/ *.m -lobjc -lgnustep-base</code></pre>
<p>The command above was tested on the provided Virtual Box image and works. If you are on another Linux system, you can try one of the following similar commands to see if they work:</p>
<pre><code>clang -I /usr/include/GNUstep/ *.m -lobjc -lgnustep-base
clang -I /usr/include/GNUstep/ -I /usr/lib/gcc/x86_64-linux-gnu/5/include/ *.m -lobjc -lgnustep-base</code></pre>
<p>On Mac OS X, the compilation command is much simpler, and is what was previously shown. Here it is again for your convenience:</p>
<pre><code>clang *.m -lobjc</code></pre>
<p><strong>Difference 4: other libraries to use</strong></p>
<p>If you are compiling the Point class, described in the <a href="http://en.wikibooks.org/wiki/Objective-C_Programming/syntax">Objective C Syntax</a> tutorial on Wikibooks, the compiler will need to know what the <code>sqrt()</code> function is. Thus, you will have to link it to the math library: put <code>-lm</code> at the end of the compilation command, otherwise it will tell you that it cannot find the <code>sqrt()</code> implementation. This likely won't be necessary for the program you have to do below, but it will be necessary for the Point class program.</p>
Expand Down
9 changes: 5 additions & 4 deletions tutorials/12-objc/index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -76,19 +76,20 @@ We have included (well, imported) a different file, and thus can no longer subcl

**Difference 3: compilation command**

As our programs are now more complicated than just a "hello world", the compilation line is longer as well. The compilation command for Linux machines (such as the VirtualBox image) is:
As our programs are now more complicated than just a "hello world", the compilation line is longer as well. The compilation command for Linux machines (such as VirtualBox image) is:

```
clang -I /usr/include/GNUstep/ *.m -lobjc -lgnustep-base
clang -I /usr/include/GNUstep/ -I /usr/lib/gcc/x86_64-linux-gnu/7/include/ *.m -lobjc -lgnustep-base
```

On some Linux systems (specificially, on 64-bit Ubuntu 16.04 systems), we had to use the following compilation line; if the one above does not work, then try this one:
The command above was tested on the provided Virtual Box image and works. If you are on another Linux system, you can try one of the following similar commands to see if they work:

```
clang -I /usr/include/GNUstep/ *.m -lobjc -lgnustep-base
clang -I /usr/include/GNUstep/ -I /usr/lib/gcc/x86_64-linux-gnu/5/include/ *.m -lobjc -lgnustep-base
```

On Mac OS X, the compilation command is much simpler, and is what was shown above:
On Mac OS X, the compilation command is much simpler, and is what was previously shown. Here it is again for your convenience:

```
clang *.m -lobjc
Expand Down

0 comments on commit 317ca07

Please sign in to comment.