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

config.nims hack prevents using nim c somewrapper from outside nimterop repo #21

Open
4 tasks
timotheecour opened this issue Feb 1, 2019 · 0 comments
Open
4 tasks

Comments

@timotheecour
Copy link
Contributor

timotheecour commented Feb 1, 2019

soloud wrapper relies on cpp files, and it works when running from inside wrappers repo because of config.nims hack which redefines the linker; however it'll fail if main profile file is outside this repo since that config file won't be applied anymore and you'll get:

Undefined symbols for architecture x86_64:
  "std::terminate()", referenced from:
      ___clang_call_terminate in soloud.cpp.o
      ___clang_call_terminate in soloud_bus.cpp.o
...

workaround

  • use nim cpp
  • copy over/pass on cmdline the linker flags from config.nims

proposal

  • build soloud into a shared library (or static lib, or both)
  • optionally, maybe use the soloud-recommended build (which requires using genie, another dependency...)
  • remove linker hack in wrappers/config.nims
  • remove linker hack in nimterop/config.nims
@timotheecour timotheecour changed the title config.nims hack prevents using nim c somewrapper from outside nimterop repo [soloud] config.nims hack prevents using nim c somewrapper from outside nimterop repo Feb 1, 2019
@timotheecour timotheecour changed the title [soloud] config.nims hack prevents using nim c somewrapper from outside nimterop repo config.nims hack prevents using nim c somewrapper from outside nimterop repo Feb 1, 2019
timotheecour added a commit to timotheecour/wrappers that referenced this issue Feb 1, 2019
timotheecour added a commit that referenced this issue Feb 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant