Hi
> On 24 Feb 2017, at 11:50, Federico Bassini wrote:
>
> Hi!
>
> we are 3 italian's student of Osvaldo, he assign us to the IDE project, we
> work on the class testVS2013Ide so we don't change the
> VisualStudioIntegratorGeneration... we have the tasks that Jan gave
Hi!
we are 3 italian's student of Osvaldo, he assign us to the IDE project, we
work on the class testVS2013Ide so we don't change the
VisualStudioIntegratorGeneration... we have the tasks that Jan gave us...
we are ready to work! now we resolve this... so we need to create a new
directory where
Hi,
On Tue, Feb 21, 2017 at 03:54:42AM +0100, Thorsten Behrens wrote:
> I don't really use that, but - always feels wrong to write stuff into
> the source tree, any reason not to use workdir or instdir?
I agree in general. Note that I likely started this unhealthy trend as for
kdevelop, it
On 2/21/2017 5:54 AM, Thorsten Behrens wrote:
Kaganski Mike wrote:
currently vs201[35]-ide-integration places its generated output into
windows subdirectory in core.
[...]
I don't really use that, but - always feels wrong to write stuff into
the source tree, any reason not to use workdir or
Kaganski Mike wrote:
> currently vs201[35]-ide-integration places its generated output into
> windows subdirectory in core.
>
> [...]
>
I don't really use that, but - always feels wrong to write stuff into
the source tree, any reason not to use workdir or instdir?
Cheers,
-- Thorsten
Hi,
currently vs201[35]-ide-integration places its generated output into windows
subdirectory in core. I an not convinced that it is sensible in the
cross-platform project like LO. And anyway VS != Windows.
My proposal is to use something like this for e.g. vs2013-ide-integration
results: