Bug 291983 - Build directory is not saved until exit
Summary: Build directory is not saved until exit
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: CMake (show other bugs)
Version: git master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: 4.2.3
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-19 19:32 UTC by David
Modified: 2013-03-08 02:41 UTC (History)
1 user (show)

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 David 2012-01-19 19:32:08 UTC
Version:           git master (using Devel) 
OS:                Linux

If I create a new project (by opening a CMakeLists.txt file) and then KDevelop crashes during my session (sadly, happening all too frequently :( ), when I re-open KDevelop it asks me to set my build directory again. My typical work around is to simply create the new project and the immediately close it, then open it again. This way when KDevelop crashes, everything is setup correctly. It seems to make sense that the project settings (build dir) could be saved immediately when the project is created so that wouldn't happen.

Reproducible: Always

Steps to Reproduce:
Create a new project and then crash kdevelop. When you reopen kdevelop, it will ask you again for the build directory you want to use.

Actual Results:  
KDevelop asks again for the build directory when reopneing after a crash while using a new project.

Expected Results:  
KDevelop should save the build directory immediately so after a crash when using a new project the build directory is saved.
Comment 1 Aleix Pol 2013-03-08 02:41:36 UTC
Git commit 6f0e4bb079c517b5aede32ad177d50115423c44e by Aleix Pol.
Committed on 08/03/2013 at 01:40.
Pushed by apol into branch 'master'.

Don't upload/download the developer config file if it's a local project

What this patch does, is to not have a developerTempFile and instead use
the actual developer config file (the .kdev4/*.kdev4) to read/write
configurations, in case it's a local project. This way we skip the download
part and kconfig will edit the file in place.
REVIEW: 109317

M  +13   -7    shell/project.cpp

http://commits.kde.org/kdevplatform/6f0e4bb079c517b5aede32ad177d50115423c44e