should just be add_executable( whatever_target secur32 )
On Fri, Jul 27, 2018 at 8:05 PM Theodore Hall wrote:
> Greetings,
>
> I'm building a project that depends on a Windows library -- Secur32.Lib --
> that is included in the regular library search path but is not one of the
> specific librar
Greetings,
I'm building a project that depends on a Windows library -- Secur32.Lib --
that is included in the regular library search path but is not one of the
specific libraries that the compiler normally links to. In *NIX
command-line terms, the "-L" is OK, I only need to specify the
"-lSecur32
Hey Andreas,
thanks for your comments. Yes I too have exhausted the resources you have
mentioned here. The concepts make sense and I see the intended point but for a
beginner its hard to grasp on how to implement and given the type of project
application of cmake's is diverse (easy to complex
Hi,
OK, unless the answer to the question in the subject line should be "NO",
then please disregard this email. I think I was having a caching issue with
my super build setup. I'm pretty sure that transitive includes are being
correctly propagated now.
Sorry for the noise,
Zaak
On Fri, Jul 27, 2
I'm trying to use a superbuild to tightly control third party libraries for
an application. They will all be statically linked in the end (besides deps
like MPI that are effective system libraries). I have the following code in
the TPL's CMakeLists.txt that I am trying to link into the main applica
Dear space & and the rest of the cmake world :)
i just googled for "modern cmake" and came up with at least two
interesting talks from cppcon and boostcon:
https://www.youtube.com/watch?v=bsXLMQ6WgIk&feature=youtu.be&t=37m15s
https://www.youtube.com/watch?v=eC9-iRN2b04
Their slides can be f
