Re: [cdt-core-dev] question about project naming

["Alain Magloire" <alain@xxxxxxx>]

> 
> >>>>> "Thomas" == Thomas Fletcher <thomasf@xxxxxxx> writes:
> 
> >> Why is this restriction here?
> 
> Thomas> It is a badly located build restriction, but it stems from the
> Thomas> fact that make doesn't handle spaces very well.
> 
> I thought it might be something like that.
> 
> I think this is only really a problem if your Makefile actually
> contains a path with a space in it.  In many situations this won't
> occur.
> 

Right, it is not a problem with make.

> Also, space isn't the only objectionable character :-(.  At least tab
> and `:' are as well (`:' is especially weird in a couple respects).
> You may also find problems with `$' and `='.  (make is, umm, lexically
> challenged.)
> 
> Rather than complaining to the user up front, though, I think it would
> make sense to let them name the project whatever they like.  We don't
> know a priori that they'll even be using make, or that their Makefile
> will include the pwd in it.  The user can always rename the project if
> he runs into trouble.
> 

The restriction should not be here, but rather let specific wizard make any
restrictions it wants.  For example the QNX C Application wizard,
should probably restrict this because its build policy can not
handle spaces.   But the default CDT wizard does not have such a restriction.

This should be remove, Pr on it [Bug 25784]

Thanks.