Craig Scott

@crascit

Consultant, C++ developer, CMake co-maintainer and book author. Consulting services available through my company, Crascit Pty Ltd.

Vrijeme pridruživanja: ožujak 2016.

Tweetovi

Blokirali ste korisnika/cu @crascit

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @crascit

  1. Prikvačeni tweet
    6. ruj 2019.

    Very pleased to make the public announcement that I'm now offering consulting services through my new company, Crascit Pty Ltd. Interested in having me work with you on your CMake, C++ or build/release issues? Then get in touch!

    Poništi
  2. proslijedio/la je Tweet
    31. sij

    The earlybird rate for 2020 ends on Monday night at 23.59. Book your place today to save £££. Pricing details can be found via the following link:

    Poništi
  3. 28. sij

    CMake Best Practice: How To Be A Good Citizen Intended for those who have been using CMake for a while. Learn how to get CMake to work better for you and how to make your projects integrate more smoothly with others.

    Prikaži ovu nit
    Poništi
  4. 28. sij

    Introduction To CMake (full day workshop): Ideal for those wanting to get started with CMake and haven't really used it before. Get a solid grounding in the essentials and learn recommended practices from the beginning.

    Prikaži ovu nit
    Poništi
  5. 28. sij

    Thinking of heading to this March in the UK? Interested in learning more about ? Come along and attend either my full day intro to CMake workshop or my talk on CMake best practices. Links to follow...

    Prikaži ovu nit
    Poništi
  6. 28. sij

    "Many methods exposing raw pointers have been changed to use smart pointers (usually Poco::SharedPtr or Poco::AutoPtr) instead. This may break some existing code." Ouch, that's going to hurt...

    Poništi
  7. proslijedio/la je Tweet
    25. sij

    In today's issue of "Computers were a mistake", gcc thinks that __uint128_t compiled with -std=c++11 and -std=gnu++11 are different types and gives ODR violation warnings

    Poništi
  8. 12. pro 2019.

    Confirmation the 3.16.0 release was BIG. Number of merge requests attached to each milestone: 3.16.0 = 423 3.15.0 = 378 3.14.0 = 373 3.13.0 = 263 3.12.0 = 295 3.11.0 = 294 3.10.0 = 333 3.9.0 = 358 3.8.0 = 273 3.7.0 = 101 Typically ~4 months between each feature release

    Poništi
  9. 10. pro 2019.

    And if you're going to play around with the new unity build or precompiled header features, you should grab the CMake 3.16.1 release which also just came out today. It contains a few fixes specifically for those.

    Prikaži ovu nit
    Poništi
  10. 10. pro 2019.

    Thanks to for implementing the new support for unity builds and precompiled headers (and others who worked on earlier versions of it)!

    Prikaži ovu nit
    Poništi
  11. 10. pro 2019.

    The build performance chapter covers CMake's new support for unity builds and precompiled headers. It also has sections for ccache, debugging-related improvements using split dwarf and using alternative linkers (e.g. gold linker).

    Prikaži ovu nit
    Poništi
  12. 10. pro 2019.

    Announcing the new edition of my book "Professional CMake: A Practical Guide". This update covers CMake 3.16 (which turned out to be a monster!) and includes a whole new chapter on build performance + a new section on the new fine-grained test resources.

    Prikaži ovu nit
    Poništi
  13. proslijedio/la je Tweet
    2. pro 2019.
    Odgovor korisnicima

    I think we have a winner! If you can find a first-edition version of K&R's "The C Programming Language," section 2.2 specifies that the preprocessor only uses the first eight characters of macro names for matching. It seems likely that these headers are old enough to be impacted.

    Poništi
  14. 26. stu 2019.

    3.16.0 has been released. Updates to my book "Professional CMake: A Practical Guide" are in progress, but you'll have to wait a few more weeks for the new edition - this has been quite a big release with some important new features!

    Poništi
  15. 7. stu 2019.

    Timely reminder that I should look into how this interacts with producing debuginfo RPMs (specifically through CMake/CPack)

    Poništi
  16. 6. stu 2019.

    For those who prefer to do so, note that you can continue to use the discourse forum purely through email, just like you would a mailing list.

    Prikaži ovu nit
    Poništi
  17. 6. stu 2019.

    PSA: CMake has switched from mailing lists to discourse: Motivation for the switch and other details can be found in the announcement on the mailing list: Mailing lists will remain active for a few more months.

    Prikaži ovu nit
    Poništi
  18. 3. stu 2019.

    One of the drawbacks to working on book updates is that you can't listen to at the same time. Too hard to do word-smithing while listening to other interesting word smiths. 😕

    Poništi
  19. 28. lis 2019.

    Think I might change my job title to Software Archeologist, based on what I’ve had to dig through lately. 🤨

    Poništi
  20. 26. lis 2019.

    Achievement unlocked: two off-by-one errors for the same piece of code. No test coverage, otherwise address sanitiser would have picked it up. On a related note, std::numeric_limits::digits10 probably doesn't mean what you think it does. ;)

    Poništi
  21. proslijedio/la je Tweet
    25. lis 2019.
    Odgovor korisnicima

    100% yes. You need both O3 and O0 with ASAN at least. You get different results and different levels of diagnostics.

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·