The Wayback Machine - https://web.archive.org/web/20201105033525/https://github.com/DLR-SC/tigl/issues/576
Skip to content

/ tigl

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

Jump to bottom

Install internal python bindings directly to the correct location #576

Open
joergbrech opened this issue Mar 13, 2019 · 3 comments
Open

Install internal python bindings directly to the correct location #576

joergbrech opened this issue Mar 13, 2019 · 3 comments

Comments

@joergbrech
Copy link
Contributor

@joergbrech joergbrech commented Mar 13, 2019

We should provide either tools (setup.py?) or documentation on how to build and use the internal python API from source
@rainman110
Copy link
Member

@rainman110 rainman110 commented Mar 13, 2019

We are using conda to build the internal API: https://github.com/DLR-SC/tigl-conda
@joergbrech
Copy link
Contributor Author

@joergbrech joergbrech commented Mar 13, 2019

I know, but shouldn't document somewhere, e.g. in the wiki, how to setup the internal API for Python after it has been manually built using CMake?
@rainman110
Copy link
Member

@rainman110 rainman110 commented Mar 13, 2019

Yes, you are right. Good point. It's best to create a readme in the python_internal folder.
@rainman110 rainman110 changed the title Document how to build internal python API Install internal python bindings directly to the correct location Apr 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
@rainman110 @joergbrech
You can’t perform that action at this time.