https://github.com/halide/Halide
Revision 6f2cae6de519a0d1c78b79525c3c88441e79b78b authored by Alex Reinking on 28 June 2023, 16:38:47 UTC, committed by GitHub on 28 June 2023, 16:38:47 UTC
* Hoist Threads::Threads to the top level

* Remove global OpenGL dependency

This is added by the helpers as-needed. Removing it here lets one build
just libHalide without searching for OpenGL.

* Narrow scope of OpenMP to tutorial

Only the tutorial targets actually use OpenMP. Don't search for OpenMP
if WITH_TUTORIALS is off.

* Move JPEG and PNG deps to tools

Only the Halide::ImageIO library uses these directly, so limiting the
scope protects against unintented use.

* Work around CMake bug

The CMake $<TARGET_NAME_IF_EXISTS:...> genex uses dynamic scoping w.r.t.
the target environment, rather than the usual static scoping. This means
we need to move the PNG and JPEG dependencies higher up.

* Add link to CMake issue in comments.
1 parent 470f43c
Raw File
Tip revision: 6f2cae6de519a0d1c78b79525c3c88441e79b78b authored by Alex Reinking on 28 June 2023, 16:38:47 UTC
Dependency wrangling part 0/N: standard CMake modules (#7658)
Tip revision: 6f2cae6
CODE_OF_CONDUCT.md
The Halide community has always worked to be a welcoming and respectful
community, and we want to ensure that doesn’t change as we grow and evolve. To
that end, we have a few ground rules that we ask people to adhere to:

- **Be friendly and patient.**

- **Be welcoming.** We strive to be a community that welcomes and supports
  people of all backgrounds and identities. This includes, but is not limited to
  members of any race, ethnicity, culture, national origin, colour, immigration
  status, social and economic class, educational level, sex, sexual orientation,
  gender identity and expression, age, size, family status, political belief,
  religion, and mental and physical ability.

- **Be considerate.** Your work will be used by other people, and you in turn
  will depend on the work of others. Any decision you take will affect users and
  colleagues, and you should take those consequences into account when making
  decisions. Remember that we're a world-wide community, so you might not be
  communicating in someone else's primary language.

- **Be respectful.** Not all of us will agree all the time, but disagreement is
  no excuse for poor behavior and poor manners. We might all experience some
  frustration now and then, but we cannot allow that frustration to turn into a
  personal attack. It’s important to remember that a community where people feel
  uncomfortable or threatened is not a productive one. Members of the Halide
  community should be respectful when dealing with other members as well as with
  people outside the Halide community.

- **Be careful in the words that you choose.** We are a community of
  professionals, and we conduct ourselves professionally. Be kind to others. Do
  not insult or put down other participants. Harassment and other exclusionary
  behavior aren't acceptable. This includes, but is not limited to:

  - Violent threats or language directed against another person.
  - Discriminatory jokes and language.
  - Posting sexually explicit or violent material.
  - Posting (or threatening to post) other people's personally identifying
    information ("doxing").
  - Personal insults, especially those using racist or sexist terms.
  - Unwelcome sexual attention.
  - Advocating for, or encouraging, any of the above behavior.
  - Repeated harassment of others. In general, if someone asks you to stop, then
    stop.

- **When we disagree, try to understand why.** Disagreements, both social and
  technical, happen all the time and Halide is no exception. It is important
  that we resolve disagreements and differing views constructively. Being unable
  to understand why someone holds a viewpoint doesn't mean that they’re wrong.
  Don’t forget that it is human to err and blaming each other doesn't get us
  anywhere. Instead, focus on helping to resolve issues and learning from
  mistakes.

- **Give credit where it's due.** If you use code or ideas from other people,
  projects, or publications, say so. Add a comment in the source code at the
  point where the idea is used. If adapting code, this requirement is above and
  beyond any requirements placed on you by the license of the original code. We
  all like recognition for our work. To that end...

**Acknowledgements.** This code of conduct is a mix of
[LLVM's](https://llvm.org/docs/CodeOfConduct.html) and
[Django's](https://www.djangoproject.com/conduct/), which both ultimately derive
from the code of conduct from the
[Speak Up!](http://web.archive.org/web/20141109123859/http://speakup.io/coc.html)
project.
back to top