On 2016-08-31 23:32, Konstantin Tokarev wrote:
31.08.2016, 16:22, "Nick Appleton" :
Hi,
I’ve been recently doing a bit of work for an open source project
trying to extend it’s support for CMake. I’ve been trying to get CMake
to be able to replicate most of the functionality which can be
achi
Is this just not possible?
On 24 August 2016 at 11:35, Steve Lorimer wrote:
> As part of our build process we tag certain binary files with version
> information such as git branch, number of commits, build variant etc.
>
> Eg, for a binary called "app" we could install a file in the local sourc
31.08.2016, 16:22, "Nick Appleton" :
> Hi,
>
> I’ve been recently doing a bit of work for an open source project trying to
> extend it’s support for CMake. I’ve been trying to get CMake to be able to
> replicate most of the functionality which can be achieved with the existing
> autoconf-based
Hi,
I’ve been recently doing a bit of work for an open source project trying to
extend it’s support for CMake. I’ve been trying to get CMake to be able to
replicate most of the functionality which can be achieved with the existing
autoconf-based infrastructure (and have had pretty good success)
Hello,
Let's suppose I have a project Foo which generates a shared library
`libfoo.so`, and a project Bar which links to `foo` and builds an
executable `bar`.
Let's also suppose that as a maintainer, I wrote a library
`libfoo_overlay.so` which links to `libfoo.so` and redefines certain
symbols in
