fix(cairo_native): use current dir in cairo compile

[noaov1]

No description provided.

[reviewable-StarkWare]

This change is 

[github-actions]

Artifacts upload workflows:

• Started at 2024-12-19T10:05:17Z
• Started at 2024-12-19T10:06:17Z
• Started at 2024-12-19T10:08:35Z
• Started at 2024-12-19T10:23:58Z
• Started at 2024-12-19T11:49:54Z

[dorimedini-starkware]

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @avi-starkware and @noaov1)

---

crates/blockifier/build.rs line 9 at r1 (raw file):

    let cairo_native_dir =
        current_dir().expect("Failed to get current directory").join(PathBuf::from("cairo_native"));

this is resolved at runtime, and the resulting dir depends on the calling context; this is desired behavior?

Code quote:

current_dir().expect("Failed to get current directory")

[noaov1]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @avi-starkware)

---

crates/blockifier/build.rs line 9 at r1 (raw file):

Previously, dorimedini-starkware wrote…

this is resolved at runtime, and the resulting dir depends on the calling context; this is desired behavior?

@avi-starkware ?
I just reverted the changes in #2289.
Do you have other ideas?

[avi-starkware]

crates/blockifier/build.rs line 9 at r1 (raw file):

Previously, noaov1 (Noa Oved) wrote…

@avi-starkware ?
I just reverted the changes in #2289.
Do you have other ideas?

Why do you want to do this?

The problem with using current_dir is that it depends on the dir from which the crate is built. In particular, running

cargo build --package "blockifier"

and running

cd ~
cargo build --manifest-path ~/workspace/sequencer/crates/blockifier/Cargo.toml

would give you different results.

Which is weird and unexpected behavior that could easily cause bugs in the future.

Why are you doing this PR?