Explore >> Select a destination
|
You are here 
|
crascit.com | ||
| | | | |
nelari.us
|
|
| | | | | Set up a build workflow to effortlessly embed data into your executable at build time. | |
| | | | |
samthursfield.wordpress.com
|
|
| | | | | As I said in my last post about CMake, targets are everything in CMake. Unfortunately, not everything is a target though! If you've tried do anything non-trivial in CMake using the add_custom_command() command, you may have got stuck in this horrible swamp of confusion. If you want to generate some kind of file at build... | |
| | | | |
blog.jak-linux.org
|
|
| | | | | Ever since it's creation back in the dark ages, APT shipped with it's own build system consisting of autoconf and a bunch of makefiles. In 2009, I felt like replacing that with something more standard, and because nobody really liked autotools, decided to go with CMake. Well,the bazaar branch was never really merged back in 2009. Fast forward 7 years to 2016. A few months ago, we noticed that our build system had trouble with correct dependencies in parallel building. So, in search for a way out, I picked up my CMake branch from 2009 last Thursday and spent the whole weekend working on it, and today I am happy to announce that I merged it into master: | |
| | | | |
www.softdevtube.com
|
|
| | | Computers are orders of magnitude faster than when most of us started programming and yet a lot of software runs much slower than it should. Nobody likes progress bars. Slow code provides for a horrible user experience, drains batteries faster, and increases our cloud bill. This session explores some of the reasons why software is | ||
