Brad King wrote: > On 07/04/2013 04:29 AM, Stephen Kelly wrote: >> Goals: >> * Install to /opt/kf5 on the target >> * Install to $HOME/dev/kf5 on the host > > Steve, why do we need to have the host location not end in the > target's install prefix?
For me, it's because I install things to the same $HOME/dev prefix on my dev machine, and my bash aliases and functions assume that. If I cd to $HOME/kf5 I know I'll find the include/ and lib/ dirs right there. I'd want to cd to $HOME/kf5-rpi and have the include/ and lib/ dirs right there too for my raspberry pi builds instead of having $HOME/kf5-rpi/opt/kf5/lib. That's the first reason I think of at least. The opt/kf5/ part might also be a more inconvenient location, different depending on the platform/device I'm building for etc. Not having that gives me uniformity. Thanks, Steve. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
