Skip to content

Conversation

viraptor
Copy link

@viraptor viraptor commented Apr 4, 2024

This option set the target build location. This caused the build to output the binary to the final install directory, breaking some build system assumptions.

Result seems to work just fine without it.

This option set the target build location. This caused the build to output the binary to the final install directory, breaking some build system assumptions.

Result seems to work just fine without it.
@Aeva
Copy link
Owner

Aeva commented Apr 27, 2024

Hm. So I think that step exists so that Tangerine can run after building it. Without that step, nothing appears in linux/build/Release/bin/, which is where I'm used to running it from while iterating? As Tangerine is written right now, it needs to be able to find the shaders directory relative to the executable, and probably also the models folder for the init model. I'm unsure what the best way to handle this is, but I'm open to suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants