Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 0001-01-01-lesson01.md #55

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update 0001-01-01-lesson01.md #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion tutorials/_posts/0001-01-01-lesson01.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -580,7 +580,7 @@ We sometimes call this a "command-line driver."
Empirical's config tools have built-in support to facilitate constructing a proper command-line interface that can process arguments, print help, etc.
But in our case we basically just want to slap a call to `evolve()` in `main()`.

Open up `source/native/evo-algo.cpp` and modify it to read something like
Open up `source/native.cpp` and modify it to read something like
```cpp
// This file is part of My First Evolutionary Algorithm
// Copyright (C) Matthew Andres Moreno, 2020.
Expand Down Expand Up @@ -621,6 +621,10 @@ C++ compilers have notoriously unhelpful, long error messages.
You can view the top of a really long error message with `make | less` (press `q` when you're done looking).
Google and Stack Overflow are useful companions for debugging compiler-ese.

If you are getting an error that mentions `-lstdc++fs`, open up `Makefile`, find where `-lstdc++fs` is used, and delete `-lstdc++fs`.
It's only needed on some machines and causes problems on others unfortunately!
Try making the project again.

If your executable compiles but crashes or doesn't work properly while running, you'll want to try compiling in debug mode and then running again.
Compiling in debug mode will activate otherwise dormant Empirical debugging facilities.
This should hopefully yield a (more) helpful runtime error message.
Expand Down