Hi Christian,
go ahead, I just fixed it in trunk for the IDE to work.
Regards,
--
Taher Alkhateeb
> On Feb 4, 2016, at 3:12 PM, Christian Geisert
> wrote:
>
> Taher,
>
> you beat me to it ;-)
> Will you commit this to the release15.12 branch too or shall I do it?
>
> Thanks,
> Christian
>
Hi Jacques,
what about a parameter using -D for the build script. we can also do something
programmatic in the ./tools directory.
Regards,
--
Taher Alkhateeb
> On Nov 21, 2015, at 12:53 PM, Jacques Le Roux
> wrote:
>
> I'd veto something which would blindly applies to all specialpurpose
>
Hi Jacopo,
I would make a distinction between two things: a) preserve what exists and b)
prepare for the future.
Doubtless what you are saying below makes perfect sense as a design decision to
allow for better future developments. I am concerned however with what
currently exists in specialpur
Hi Nicolas,
The 13.07 to me was a painful release to deal with because of stripping out the
specialpurpose components. Also disabling these components means lower quality,
no testing and no guarantee of being compatible with the current version of
trunk. So i would imagine this to be sort of eq