Comments (4)
Hi, thank you for your post.
The three seconds are to allow time to cancel the build if necessary. The script files are only to facilitate the building procedure, but you can always just use CMake directly and have more control over the building process. I will try to add an option to the script to control the sleeping time, though.
from fuzzylite.
Alright, sure :P
I'm currently working on a node.js module that uses the this library and part of that requires building the code. I'm just running build.sh
since thats whats documented as the build procedure. I would prefer to build with default-arguments to reduce the risk of diverging from this repository's build-system. With that in mind, I think it might be beneficial to either document the cmake arguments thoroughly and/or make sure sane defaults are used.
It might be that they both are documented and that sane defaults currently are configured, but in that case I don't know where to find that information (which then in itself might be worth documenting).
Perhaps this discussion is a bit off topic though, if you think so I will create a new issue for it.
from fuzzylite.
Please, check the CMake command in build.sh
. Information about the arguments can be found here: http://www.fuzzylite.com/cpp/#Building_from_source . You can also look at the CMakeLists.txt for specific information.
from fuzzylite.
Ah, yes, so I just missed it, good :)
Then I will close this issue, thanks for the help.
from fuzzylite.
Related Issues (20)
- AUR - fuzzylite compilation failed HOT 6
- Run tests on Windows
- Compiling errors under Ubuntu 22.04 HOT 6
- Missunderstanding of the obstacle avoidance example HOT 2
- Outdated Doxygen URL in README.md HOT 2
- Outdated guideline hyperlink in CONTRIBUTING.md HOT 8
- Build issue with glibc 2.34 HOT 4
- support for catch2 v3
- Can not open the source file "fl/Headers.h" HOT 2
- example error undefined reference to 'fl::Engine::Engine(std::string const&)' and relocation error HOT 1
- test hardcodes path
- doxygen files in git
- fuzzylite stores build path in output binary HOT 5
- executable file without shebang
- unit test fails on i386 HOT 4
- Energia code for fuzzy speed controller on C language
- Releasing this under vcpkg HOT 3
- Segmentation fault when `fl::*` objects embedded in C++ class HOT 2
- Tests fail to compile with glibc >= 2.34 HOT 9
- TODO: Version 7.0 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fuzzylite.