Comments (3)
(transitive_)(relative_)(angled_)includes
now handle -iquote
and -I
. We have absolute and workspace-relative includes working, but cross-workspace includes are missing. This is particularly relevant for Projects building on top of LLVM.
We need to be able to reference LLVM and Clang headers from outside the @llvm-project
workspace. Since the current implementation uses rules_cc
for these targets we need some sort of compatibility layer. Either rules_ll
must understand cc_library
targets better, or we add ll_*
targets to the existing cc_*
overlay.
We did not encounter a need for -idirafter
, -isystem
and -isystem-after
, so this is postponed.
from rules_ll.
After adding module support we get some unwanted warnings in precompilation steps regarding unused -iquote...
. I'm also considering whether we want to change the APIs to have finer-grained control regarding transitivity. Something like
attr
public_attr
transitive_attr
where public_attr
is only made available to direct dependencies and transitive_attr
is available to all downstream dependencies in the build graph. We need to be careful not to bloat the user interface for ll_library
though 😅
from rules_ll.
We now removed all transitive_*
attributes in favor of exposed_*
attributes which don't carry dependencies transitively. I think this is good for now. We can create another issue if this needs another rework.
from rules_ll.
Related Issues (20)
- GPU targets run correctly but tests fail HOT 1
- Module override for circl breaks downstream users
- Investigate the use of aspects for clang-tidy
- Borrowing an Nvidia GPU HOT 2
- Embedded device support (Steamdeck)
- WSL: Number of devices is 0 HOT 2
- The `ll init` command is a bit whacky HOT 2
- Cannot run tests in CI HOT 4
- 😵 GPU examples make my eyes bleed
- Shellcheck pre-commit hook might be broken HOT 1
- Document usage with local CUDA HOT 2
- Migrate CUDA imports to new variants in nixpkgs HOT 4
- Migrate to zlib-ng HOT 2
- We can't ignore example lockfile but also can't commit it
- Improve user experience for the `rbegen` tool HOT 1
- Document new remote execution toolchains HOT 1
- Release blockers
- Consider building our own remote execution service HOT 3
- Remote execution images too hard to customize
- Rework internal file inputs as preparation for module std 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 rules_ll.