Hi All,
Like many, I've been having trouble understanding the RPATH control settings.
In particular, I can't seem to get external libraries (e.g. boost) to link in
*any* way that allows it to find dependent libraries without DYLD_LIBRARY_PATH.
Eventually I'd like to refer to them with relative pa
Hi Carlton,
On Sun, Oct 29, 2017 at 12:02 PM, Carlton Banks wrote:
>
> Is there a way to print the path like ${source_dir} and so on within the
> CMAKElist, so I can keep track of the paths defined?
I found understanding exactly what you are asking for a little unclear, but
possibly you are loo
On Wed, Oct 25, 2017 at 10:36 AM, Carlton Banks wrote:
> Is there some literature that desbribes how cmakelist has to be defined a
> big system, that involve multiple smaller modules within the big module.
Unfortunately, written documentation of structuring larger projects with
CMake seems to b
On Wed, Aug 23, 2017 at 8:07 AM, Clément Gregoire wrote:
> I entirely agree with for the rest. CMake badly documenting good practices
> or even giving tutorials is an issue. Probably the biggest issue I found. I
> myself still fight after years of using and experimenting with it. This
> lead to a
. Perhaps
I'm merely imagining something wildly different from the intention.
Nick
On Mon, Jul 24, 2017 at 7:46 PM, Nicholas Devenish
> wrote:
>
>> Seen in the boost discussions on the CMake announcements:
>>
>>
>>> > The rest can be implemented straight
Seen in the boost discussions on the CMake announcements:
> > The rest can be implemented straightforwardly as cache options so that
> > you can run cmake with options like
> >
> > -Dvalgrind=OFF -Dtransactional-memory=ON -Dsegmented-stacks=ON [-D…]
> ...
Secondly, in cmake 3 we try not to con
For what it's worth, I'm not seeing this on Sierra 10.12.5, CMake
3.9.0 on a simple test case of:
cmake_minimum_required(VERSION 3.5 FATAL_ERROR)
file(COPY afile DESTINATION .)
I ran through Instruments to check the otherwise silent copy, it
copies the first time but thereafter only stat
Hi,
It looks like this is the issue covered in
https://cmake.org/Wiki/CMake_FAQ#How_can_I_add_a_dependency_to_a_source_file_which_is_generated_in_a_subdirectory.3F
and bug https://gitlab.kitware.com/cmake/cmake/issues/14633 ? I
suppose if you are writing your own systems from scratch it's easy not
I've been finding the 'modern' approaches of imported targets as used
by e.g. Boost and some other modules much better - being able to
specify all dependencies in a single target_link_libraries instead of
hauling around a whole load of required variables for each dependency.
However, only very few
