Bug 260738 - Custom BuildSystem shouldn't use $HOME when build directory doesn't exist
Summary: Custom BuildSystem shouldn't use $HOME when build directory doesn't exist
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdevelop
Classification: Applications
Component: BuildSystem: Custom BuildSystems (other bugs)
Version First Reported In: git master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: 4.2.0
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-19 21:47 UTC by Alexander
Modified: 2023-01-18 09:58 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2010-12-19 21:47:15 UTC 
Version:           SVN (using KDE 4.5.3) 
OS:                Linux

I'm using KDevelop 4.2 git branch from 2010-12-19 and master branch of kdev-custom-buildsystem.

I have an autotools-based project with a path to "configure" specified in the Executable field.
If I specify a non-existent directory (e.g. a subdirectory of my project directory) in "Build Directory" field, my configure and make commands end up being run in my home directory, polluting it.

I think the build directory should simply be auto-created if one of them is run.

Thanks

Reproducible: Always




openSUSE 11.3 x86-64, Qt 4.7.1, KDE from OBS.
Comment 1 Aleix Pol 2013-06-12 01:52:59 UTC 
Can you try again? I seem to recall changes in this regard.
Comment 2 Alexander 2014-03-12 19:44:19 UTC 
This seems to be partially fixed.

If the build directory doesn't exist, the configure command is executed in the source directory instead (or maybe just in the upper level of the build directory). This pollutes the source directory.

The build directory should be auto-created if it doesn't exist.

Thanks
Comment 3 Andrew Crouthamel 2018-11-11 04:33:27 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-21 04:24:28 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Alexander 2018-11-21 08:52:56 UTC 
I no longer use KDevelop so I cannot re-test this, sorry.
Comment 6 Justin Zobel 2023-01-18 02:41:18 UTC 
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Alexander 2023-01-18 09:58:18 UTC 
I no longer use the software, and this is for a very old version of the software, so I'm closing this bug.