Re: [cmake-developers] CMake aliasing system

2016-03-19 Thread Tamás Kenéz
Ruslo, I think we all could argue both against and for implementing cmake-ini files inside the cmake command. I mean I'm also aware of all the pros and cons. It's just that we weigh differently. I like loosely connected simpler building blocks and my own cmake-wrapping extension script works fine,

Re: [cmake-developers] CMake aliasing system

2016-03-19 Thread Ruslan Baratov via cmake-developers
I've openned new issue for further discussion: * https://github.com/ruslo/CMake/issues/3 On 18-Mar-16 06:24, Tamás Kenéz wrote: Ruslo, I think we all could argue both against and for implementing cmake-ini files inside the cmake command. I mean I'm also aware of all the pros and cons. It's just

Re: [cmake-developers] CMake aliasing system

2016-03-14 Thread Ruslan Baratov via cmake-developers
On 15-Mar-16 02:42, Tamás Kenéz wrote: I also doubt this belongs to upstream. But you could write a single, generic script which forwards its arguments to cmake and also accepts and processes the additional parameters along the way. I don't think we'd lose anything: cmakeini -c ipad -H. -

Re: [cmake-developers] CMake aliasing system

2016-03-14 Thread Tamás Kenéz
I also doubt this belongs to upstream. But you could write a single, generic script which forwards its arguments to cmake and also accepts and processes the additional parameters along the way. I don't think we'd lose anything: cmakeini -c ipad -H. -DTHIS_WILL_BE_FORWARDED=AS_IT_IS This is th

Re: [cmake-developers] CMake aliasing system

2016-03-14 Thread Ruslan Baratov via cmake-developers
On 14-Mar-16 21:59, Brad King wrote: On 03/12/2016 08:04 AM, Ruslan Baratov via cmake-developers wrote: I guess it is a well known fact that cmake command is almost never executed alone and for non-trivial examples usually hold some extra arguments (home directory, build directory, verbosity lev

Re: [cmake-developers] CMake aliasing system

2016-03-14 Thread Brad King
On 03/12/2016 08:04 AM, Ruslan Baratov via cmake-developers wrote: > I guess it is a well known fact that cmake command is almost never > executed alone and for non-trivial examples usually hold some extra > arguments (home directory, build directory, verbosity level, toolchains, > options, ...)

[cmake-developers] CMake aliasing system

2016-03-12 Thread Ruslan Baratov via cmake-developers
Hi, I guess it is a well known fact that cmake command is almost never executed alone and for non-trivial examples usually hold some extra arguments (home directory, build directory, verbosity level, toolchains, options, ...). Also I guess that such commands doesn't change from day-to-day dev