Hi,
I'm trying to automate the installer generation of one of my projects.
Everything is working fine so far except one thing: One of my test-users
(still using XP) is 'moaning' about not having a start-menu-entry for
the program (but for the uninstaller). Unfortunately I don't have an
instance of
I mostly agree with Bill's reply, especially the advice about the all
or nothing approach. If you use ExternalProject, go all the way, build
all your dependencies first, and then your own project as an
ExternalProject.
After the build is done, it's easy enough to switch to the "inner"
project
On 1/6/2014 10:05 AM, Bill Hoffman wrote:
There is not a good way to make this work. Everything HAS to be
external project including your project. You have a couple of options:
1. leave it with your project as an external project along with the
other depends. Then instruct your developers t
On 1/5/2014 12:14 PM, Rob McDonald wrote:
I have since tried moving to a two-class system, where my main project
is not ExternalProject_Add'ed, but the big dependencies are. This of
course runs into the problem where the libraries are not built when the
FindXXX.cmake modules go looking for them
Hi
I'm getting the same behaviour with CMake 2.1.12.X on my own project. The
behaviour has been reported on the ninja mailing list. Doesn't seem to be clear
where the issue is…
Mike
On 28 Dec 2013, at 17:52, Utkarsh Ayachit wrote:
> I'm seeing a strange behavior since I updated to CMake 2.8
