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

How to build this project for static linking #75

Closed
odemiral opened this issue Aug 12, 2022 · 0 comments
Closed

How to build this project for static linking #75

odemiral opened this issue Aug 12, 2022 · 0 comments

Comments

@odemiral
Copy link

Hi,

I’ve been trying to link your library statically to my project without any luck, I was able to compile your library as a static library on mac (.a) and I understand that I need to manually add the include headers in order to use the static library, however your headers inside “include/" folder are all dependent on your headers from other modules such as CppCommon (like time/time.h) If I include just the include folder (like you suggested on this issue) then they won't compile since they’re all relying on your cppcommon library.

If I go down the path of including literally every header path to the project then, I suppose that might work but then again you have multiple files with same name (like version.h, memory.inl, etc) which will cause lots of headache.

I was wondering if there's a better way here that I'm not seeing? I'm not well versed in cmake but I made modifications to your CMakeList.txt to a point where I can build your library as a .framework for OSX and iOS (with Headers) but if you could shed some light on dealing with headers from other modules then I'd love to finish what I started and open a PR.

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

No branches or pull requests

1 participant