You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: