On Sat, Jun 15, 2019 at 5:01 PM Paul Smith wrote:
> I have a situation where I create a number of static libraries, then I
> create a shared library from them, then I create an executable from the
> shared library.
>
> This seems straightforward, but I can't get it do work as I want. The
> behav
On Sat, Jun 15, 2019 at 9:03 PM Shoaib Meenai wrote:
> Is it possible to associate a target with multiple exports? For example,
> if I'm building a project where I want to create multiple export sets, but
> there's some overlap in targets between those sets. I tried passing
> multiple EXPORT opti
Is it possible to associate a target with multiple exports? For example, if I'm
building a project where I want to create multiple export sets, but there's
some overlap in targets between those sets. I tried passing multiple EXPORT
options to the install(TARGETS) signature but I just got an erro
I have a situation where I create a number of static libraries, then I
create a shared library from them, then I create an executable from the
shared library.
This seems straightforward, but I can't get it do work as I want. The
behavior of STATIC -> SHARED for target property inheritance seems
i
I want to accomplish a c++ executable that links to another c++ library
of my own without a libstdc++ dependency. I can create such a c++
executable without the library without difficulty. But as soon as I link
it to my library, the executable now has a libstdc++ dependency. A
requirement is to
