rotund birch
I want to move these to a config, but when I do it they either apply to everything or nothing. It's in a workspace, and only for the target x86_64-polished-kernel.json . Right now, i have:
RUSTFLAGS="-C relocation-model=static -C link-args=-no-pie -C link-arg=-Tkernel/linker.ld" cargo build -p kernel -Zbuild-std=core,alloc --target x86_64-polished-kernel.json
usually i can do it but ive never applied it to a workspace member specifically
wraith rain
You don't. You apply it to a target.
[target.'cfg(...)']
rustflags = [...]
where
i tried that but didn't put cfg
wraith rain
in .cargo/config.toml
rotund birch
[target.'cfg(x86_64-polished-kernel.json)']
?
rotund birch
in .cargo/config.toml
in the root of the workspace or the actual member?
wraith rain
```toml
[target.'cfg(x86_64-polished-kernel.json)']
```
?
no, the cfg() should contain cfg flags
rotund birch
huh
i don't think i have a cfg flag i could use just for the kernel member?
~/workspace/.cargo/config.toml though right
wraith rain
i don't think i have a cfg flag i could use just for the kernel member?
ones that will uniquely specify your target. such as cfg(target_vendor = "polished") or whatever you have set vendor to in the json
rotund birch
"vendor": "unknown",
wraith rain
well, set it to something unique
rotund birch
Okay
wraith rain
cargo's configuration file has nothing to do with the workspace
rotund birch
[target.'cfg(target_vendor = "polished")']
rustflags = [
"-C", "link-arg=-Tkernel/linker.ld",
]
?
wraith rain
it is configuration for the cargo tool itself, not any particular project. the .cargo directory that contains it can be located in ., .., ../.., etc.
or, even if it is not a parent, ~/
rotund birch
bruh
im used to one per rust project
i just need it to apply the linker.ld for one workspace member 😭
wraith rain
that is certainly one way to configure cargo
rotund birch
```toml
[target.'cfg(target_vendor = "polished")']
rustflags = [
"-C", "link...
should this work
wraith rain
assuming that is set in the spec json passed to rustc, yes
a linker flag for a particular bin or cdylib artifact is generally set from the build script
rotund birch
i think it is?
rotund birch
a linker flag for a particular bin or cdylib artifact is generally set from the ...
so should it be kept in the makefile...
wraith rain
fn main() {
println!("cargo::rustc-link-arg=-Tkernel/linker.ld")
}
if you did not try this before resorting to RUSTFLAGS, I recommend trying it, though it is possible that the linker script flag in particular does not work
rotund birch
hm
rotund birch
```rust
fn main() {
println!("cargo::rustc-link-arg=-Tkernel/linker.ld")
}
`...
printing things changes cargo?
rotund birch
why is it println and not some other method that would make more sense
rotund birch
```rust
fn main() {
println!("cargo::rustc-link-arg=-Tkernel/linker.ld")
}
`...
this works
weird
i feel like its against rust to do magic shit with printlns when building but ig not in this one case
wraith rain
i feel like its against rust to do magic shit with printlns when building but ig...
a build script is a program that takes input in the form of environment variables and produces output in the form of printed build directives
rotund birch
so this adds a build directive?
wraith rain
rotund birch
Build scripts communicate with Cargo by printing to stdout. Cargo will interpret each line that starts with cargo:: as an instruction that will influence compilation of the package. All other lines are ignored.
Ah
interesting
well thanks
rotund birch
I want to move these to a config, but when I do it they either apply to everythi...
should any of this other stuff be in the build.rs