kdevelop.kdevelop
Bernd Pol
bernd.pol at online.de
Wed Oct 22 14:33:04 UTC 2003
Hi all,
On Wednesday 22 October 2003 08:25, Falk Brettschneider wrote:
> The feature of the project file to not to be user-specific (and
> therefore ready for cvs-management) got lost from KDevelop-2 to
> KDevelop-3. So at present this is some kind of a regression. And I
> think the user acceptance depends on such simple questions.
Falk makes a point here. Common project structure and user
dependent informations should be separated again. Form the user's point
of view it makes a clear difference if you have to import a freshly
required project or can just start over with a provided
common .kdevelop project file.
We must also find a way to keep multitarget/cross build information
readily available as well, even distributable on a common level as Iztok
pointed out.
So we have three levels of project information to consider: common
structure (.kdevelop), special build structures (some .kdevelop
extension???), and private structures (.kdevses, rc).
But this is something for a 3.1 version.
Bernd
More information about the KDevelop-devel
mailing list