Date: prev next · Thread: first prev next last
2017 Archives by date, by thread · List index


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 we can put the project files?
we also remove the '../../' and to replace it we use the enviroment
variables... it's ok? :)

rgds
ffex

2017-02-21 12:01 GMT+01:00 Bjoern Michaelsen <
bjoern.michaelsen@canonical.com>:

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 indeed wasnt really possible to avoid writing to the source
tree.

As noted in other replies, having a top-level "make clean" kill the
solution
files is undesireable too. I wonder though, if for IDEs where this is
possible
a separate top-level dir instead of sprinkling things all over the tree is
desireable? E.g. $(SRCDIR)/ide-solutions or $(SRCDIR)/vs{2013,2015,...).

Best,

Bjoern
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.