Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom resources / models #47

Open
ptheywood opened this issue Mar 22, 2021 · 1 comment
Open

Custom resources / models #47

ptheywood opened this issue Mar 22, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@ptheywood
Copy link
Member

Non stock resources are accessed by path, realtive to the working directory.

Executables are not alwasy called from the same location, so this is limiting. Allowing a list of paths to search is a potential alternative?

I.e. in an individual model repository (based on the template), if a resource is placed into resources/cylinder_geom.obj, this binary must be called from the repository root, rather than build (or any level deeper, or higher).

Alternatively, a way of packing resources into the binary at the CMake level could be good.

This willl probably need changes in both repos given how the vis headers are spread around.

@ptheywood ptheywood added the enhancement New feature or request label Mar 22, 2021
@Robadob
Copy link
Member

Robadob commented Mar 22, 2021

Alternatively, a way of packing resources into the binary at the CMake level could be good.

Yeah this would be nice, should be possible to define a var, which is fed into the vis compilation's resource list. Albeit not 100% sure how at this point in time.

Probably not suitable for larger resources (e.g. if someone has a 200mb static model they want to include).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants