There are some possible solutions and reference here:
https://stackoverflow.com/questions/41471620/cmake-support-make-uninstall
Le sam. 16 févr. 2019 à 15:48, Felix Crazzolara
a écrit :
> Hi everyone
>
> For my smaller projects I'd like to have 'uninstall' functionality. To
> remove installed fi
On Wed, Feb 20, 2019 at 3:36 PM Timothy Wrona wrote:
> (Included cmake-developers list as well in case this may have just been
> something that should work that was overlooked with the FetchContent module)
>
> On Tue, Feb 19, 2019 at 11:32 PM Timothy Wrona
> wrote:
>
>> I am having an issue with
Hello,
I use CMake 3.13RC1. My project produces, installs and exports a shared library
target "fooshared". Some logical parts of "fooshared" are reused in an
executable, so I have placed those sources into an internal static library
target "barstatic". I have used target_link_libraries(fooshare
Hi,
I just got some build failures when changes to my build scripts led to
configuring with -DCMAKE_AR=ar (RANLIB=ranlib, etc).
The documentation isn't explicit on what these parameters expect so I assumed
that it should be fine to set them to a command name, as with
CMAKE__COMPILER.
Wrong! C
Okay that makes sense. I will give ExternalProject_Add a try. I think it
would be very useful if FetchContent were able to support targets with the
same name and that would be a great feature to add (although it is
understandable if it is a language limitation).
I much prefer the simplicity of Fet
Thanks for the sanity check. I'm not really sure what is going wrong then.
Not a big deal per se but would really like to figure out what the issue
is. Maybe something funky with my PATH variable. This is on Windows 10 x64.
--
Mike Jackson
On Tue, Feb 19, 2019 at 7:21 PM J. Caleb Wherry
wrote:
I just wanted to share a solution for mixing C++ and Fortran programs
on Windows using Visual Studio and Intel Fortran. The build was
failing at link time with undefined symbols comming from fortran code.
Actually, none of the fortran sources were compiled, even though it
was working fine on Linux
I have worked on multiple C++ libraries that are built with CMake and run
Doxygen to generate HTML documentation. In every one of these libraries,
the documentation get's built into an "html" folder in the CMake "build"
directory and never gets looked at by anyone.
*Because let's be honest, most p
I am developing platform support for an embedded target (Z8 Encore!), and it
mostly works – but I’d like to make it easier to set the compiler and linker
flags, as there’s a ton of them: and they are nothing like GNU flags, so they
only apply when building for that particular target.
Thus a qu
On 2019-02-20 17:52-0500 Timothy Wrona wrote:
I have worked on multiple C++ libraries that are built with CMake and run
Doxygen to generate HTML documentation. In every one of these libraries,
the documentation get's built into an "html" folder in the CMake "build"
directory and never gets looke
10 matches
Mail list logo