Skip to content
This repository has been archived by the owner on May 17, 2021. It is now read-only.

--framework with *.a and *.dylib in _install/<toolchain>/lib complains #26

Open
headupinclouds opened this issue Jun 30, 2015 · 1 comment

Comments

@headupinclouds
Copy link
Contributor

I changed configurations and ended up with a *.a and *.dylib in my _install//lib/ folder. The build.py --framework option complained about multiple libs. This was with commit: a9443b4 . This isn't exactly as bug... (How should it know which type of lib to use?) It is easy enough to delete one and then re-run, but possibly an additional option is required to specify the desired framework type in cases where both libs are present. How do you want to handle this (or just leave as is)? I can probably modify as needed once I get past a couple deadlines.

@ruslo
Copy link
Owner

ruslo commented Jul 2, 2015

How should it know which type of lib to use?

Yes. There are several questions I guess:

  • if *.a and *.dylib installed what type of framework you want to build? Static or dynamic?
  • if multiple libraries found do you want to use one or combine all of them into one big library?
  • if multiple libraries found what framework name should we use?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants