Re: [CMake] How do static libraries get linked in Ninja?

When I make an example project I see the following link line /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/example.dir/test.cpp.o -o example liblib1.a liblib2.a && : Can you

Re: [CMake] How do static libraries get linked in Ninja?

The latter. On Thu, Jan 5, 2017 at 3:39 PM, Robert Maynard wrote: > Do you mean you don't see where the static library is created or where > the static library is listed on the link line for the dynamic library? > > On Thu, Jan 5, 2017 at 11:30 AM, Robert Dailey

Re: [CMake] How do static libraries get linked in Ninja?

Do you mean you don't see where the static library is created or where the static library is listed on the link line for the dynamic library? On Thu, Jan 5, 2017 at 11:30 AM, Robert Dailey wrote: > I have two targets in CMake: a static library and a shared library. >

[CMake] How do static libraries get linked in Ninja?

I have two targets in CMake: a static library and a shared library. The shared library specifies the static library as a target link library. When I generate for Ninja, and I run: $ ninja -v During the link command for the shared library, I do not see the static library specified to g++. I do