Bug 60092 - The Default project configuration
Summary: The Default project configuration
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: appwizard (show other bugs)
Version: 1.0.0
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-19 23:07 UTC by Sphere
Modified: 2009-01-22 23:37 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sphere 2003-06-19 23:07:03 UTC
Version:           CVS (using KDE Devel)
Installed from:    Compiled sources

In the Default (debugging) project configuration, when creating
a new project, please append the project directory to KDEDIRS
in the environment and use --prefix=<project directory> for
running config.
Comment 1 John Birch 2003-06-21 22:05:50 UTC
I don't think kdevelop should be doing this - this is something that the user 
should be setting up. 
 
I know that I want my project to be installed in my live system (even in a 
debug mode), because I know what I am doing with my system. 
 
Other shops have a completely separate test system that they'll install to. 
 
This is really about what happens when we try and _install_ a project. It's 
here that the user should see an appropriate warning (that could be turned off 
btw) as has been suggested in another wishlist item I believe. 
Comment 2 Dominik Haumann 2003-10-18 15:53:06 UTC
IMO we don't need this.
I know the problem that newbes have problems with installing because they don't know how to specify the installation destination, BUT there is good documentation for kdevelop 3 that explains everything (look in KDevelop on the right sitebar the Documentation "QT-Designer 3 and KDevelop 3"). If a user goes though such a tutorial he knows what to do to set the destination path.

So I close this BR as WONTFIX - we can reopen the bug if more users wants this behaviour.

btw: it is possible to open a specified file directly after project generation. We could open a README.devel that contains information about how to set installation destination and other important things. What do you think about that???