From kdevelop-bugs  Tue Oct 23 19:17:13 2007
From: Michael Downey <michael.downey () pixelgrammetry ! com>
Date: Tue, 23 Oct 2007 19:17:13 +0000
To: kdevelop-bugs
Subject: [Bug 151251] New: QMake manager reports "The specified folder does
Message-Id: <20071023211712.151251.michael.downey () pixelgrammetry ! com>
X-MARC-Message: https://marc.info/?l=kdevelop-bugs&m=119316714720040

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=151251         
           Summary: QMake manager reports "The specified folder does not
                    exit or was not readable" when a variable is used in
                    DESTDIR
           Product: kdevelop
           Version: 3.5.0
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: michael.downey pixelgrammetry com


Version:           3.5.0 (using KDE 3.5.7, Gentoo)
Compiler:          Target: i686-pc-linux-gnu
OS:                Linux (i686) release 2.6.22-gentoo-r8

Using a user defined variable to set the DESTDIR variable causes the QMake manager to pop up a dialog that says: "The specified folder does not exist or was not readable" when the subproject settings is selected.

Steps to reproduce:
1) Create new QMake Qt4 project
2) Add a custom variable BASEDIR = ..
3) Set the DESTDIR = $${BASEDIR}/bin/
4) Set TARGET = test
5) Create the bin directory off of the base directory.
6) Bring up the settings again for that application and a dialog should pop up with the error.

Expected:
Manager sees that $${BASEDIR}/bin/ is ../bin/ and no error is generated.

Also note that DESTDIR = $${BASEDIR} works.  It seems to require an extra directory specification on top of it.

Main reason for using DESTDIR instead of TARGET is to allow for easier portability between Linux and Windows.

I'm not using the very latest KDevelop but I didn't see any bugs on this problem.  I'm sorry if this is already fixed in SVN.

Also this doesn't effect the building of the application.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs