Bug 71298 - Space in the project path
Summary: Space in the project path
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: All build tools (show other bugs)
Version: 3.0.0b2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
: 141083 164848 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-12-27 14:07 UTC by Frédéric COIFFIER
Modified: 2008-07-05 20:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frédéric COIFFIER 2003-12-27 14:07:56 UTC
Version:           3.0.0b2 (using KDE KDE 3.1.94)
Installed from:    Compiled From Sources
Compiler:          gcc (GCC) 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r2, propolice) 
OS:          Linux

When the project path contains one (or several space), KDevelop can't compile or launch the program because, the shell commands which are used, don't used quote.
So a :
cd /home/user/project path/
will failed !
Comment 1 Harald Fernengel 2003-12-27 16:34:45 UTC
thanks for the report, I think I fixed all unquoted paths from the autmake part. Unfortunately, it still doesn't build since the configure script doesn't like path names with spaces, but that's something that has to be fixed in the auto-tools and not in KDevelop.

Summary: Just don't use spaces in filenames, it looks too MS-like anyways :) Underscores work well.
Comment 2 Eduardo Robles Elvira 2004-05-06 20:44:10 UTC
Frédéric, please can you open the bug ? I' using kdevelop 3.0.3, and this doesn't seems to be solved at all. It's exactly the same problem.. 

Summary: this is important, although someone which want to develop I'm sure he would notice which is the problem normally, but the new starters don't. And sorry, but MS didn't invent spaces :-).
Comment 3 Fred van Zwieten 2005-03-17 17:33:19 UTC
Could someone please reopen this bug. I'm running Suse 9.2 with KDE 3.4 and kdevelop 3.2.0 and found this bug still there. I used a folder "KDE Training" in my home dir for my projects. bad idea! " Build Project (F8) stops compaining it can't CD to the project dir.
Comment 4 Amilcar do Carmo Lucas 2005-03-18 11:31:28 UTC
Like Harold said this is most probably an GNU-Autotools problem and not a KDevelop problem.

What are your autoconf, automake, autoheader, libtool versions ?
Comment 5 Amilcar do Carmo Lucas 2005-11-29 15:10:23 UTC
No activity for 9 months
Comment 6 Frédéric COIFFIER 2005-11-29 15:18:48 UTC
As spaces are not allowed in paths, maybe these spaces could be forbidden in the KDevelop dialog box (or to display a Warning message box).
Comment 7 Andreas Pakulat 2007-02-02 19:12:26 UTC
*** Bug 141083 has been marked as a duplicate of this bug. ***
Comment 8 Xangis 2007-05-18 23:29:15 UTC
This bug is still an issue in KDevelop 3.4.0 on Ubuntu 7.04 using gcc 4.1.2, automake 1.9.6, and autoconf 2.13.

The following error message is given on a build:
configure: error: ls -t appears to fail. Make sure there is not a broken
alias in your environment
configure: error: newly created file is older than distributed files!
Check your system clock 

When a path without spaces is used this error disappears.

Using a program path without spaces is not necessarily always easy or desirable, for instance, when working on porting an application checked into CVS or Subversion by Windows-centric programmers who don't realize spaces are annoying.
Comment 9 Andreas Pakulat 2007-05-18 23:48:38 UTC
KDevelop doesn't allow to create projects with spaces in the path. We can't fix configure, that is a generated script and the error is in autotools (which generate this). Autotools are not a part of KDevelop. If you want to use an autotools project and have spaces in their path please file a bugreport at the autotools project.

Also Windows programs don't use autotools normally, so you could just use a different buildsystem on your non-windows platform.
Comment 10 Amilcar do Carmo Lucas 2008-06-24 19:38:36 UTC
*** Bug 164848 has been marked as a duplicate of this bug. ***
Comment 11 Andreas Pakulat 2008-07-05 20:57:20 UTC
I'm closing this as fixed, KDevelop4 doesn't have any restrictions on paths. The autotools-problem needs to be handled upstream anyway.