indygreg / indygreg/PyOxidizer

How to set the output path for building?

Open
#495 3 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Rust
Stars
6.2k
Forks
256
PR merge metrics
No merged PRs in 30d

Description

I'm working on creating a basic pyoxidizer plugin for Pants (https://github.com/sureshjoshi/pants-pyoxidizer-plugin/) - and it's starting to work, however I cannot get the final binary to a useful directory, and then it's evicted from my Mac.

I'm investigating, but I believe Pants uses some tmp process-execution directories, which are immediately deleted. PyOxidizer appears to only build to relative locations. e.g.

`/private/var/folders/18/q1r7phps28nc9rx5j_0t3jmm0000gp/T/process-executiongGTfnJ/./build/x86_64-apple-darwin/debug/exe/helloworld-bin`

Is there any way to set the binary's output path to an absolute location?

I tried the `OUT_DIR` environment variable, but setting that before calling PyOxidizer doesn't appear to do anything.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing how PyOxidizer handles relative build destinations and whether the OUT_DIR environment variable is read. Compare that behavior with Pants's temporary process-execution directory, and verify the result by building the example and confirming the binary is written to an absolute location that survives cleanup.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.