Hi Michael~
> That does seem to be the rub, at least on a Windows build. Something about
> ExternalProject_Add ain't quite kosher with what the Boost build system
> expects and it needs a little help.
> Using ExternalProject_Add, it succeeds, to a point. Then it falls over
> looking for b2 no
maybe a CMake snippet of what you are trying would help clarify, but are you
using an interface library for your header-only? I would assume yes - and then
have to tried add_dependency() for that library to trigger the file generation?
The dependency will only be resolved when the library is use
Hi Robert.
You might try leaving ASM out of project() and using enable_language()
after your call to project() (potentially in conditional branches). It can
only (reliably) be used from the toplevel CMakeList, but that sounds like
it could be good enough for you.
https://cmake.org/cmake/help/late
I haven't; the bigger issue here is that the way we specify ASM
changes depending on platform. But prior to the project() call, you
can't really use CMake to its fullest since project() serves as
practically an "initialize CMake" function. So there's a catch 22
situation here.
My expectation was t
Hi!
I am a seasoned Cmake user but cannot solve a fairly simple problem, so I might
be mistaking the forest for the trees.
I have a project in which there is a custom_command/custom_target pair that
creates a header file as part of a (currently) header-only target. I want to
create an imported
