-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Dmitry!

Could you elaborate a bit on how you managed to get bug #315170? It
seems to me the problem only occurs if you are modifying a .pro file in
the top directory. I tried the following :

A/ A default QMake project

1. create a new QMake project called "fooproj". The result is this:

  ./fooproj.kdevelop
  ./fooproj.pro
  ./src/src.pro
  ./src/fooproj.cpp

  --- fooproj.pro ---
  TEMPLATE=subdirs
  SUBDIRS=src
  ---

  --- src/src.pro ---
  SOURCES=fooproj.cpp
  TARGET=../bin/fooproj
  ---

  "src" is set as the active directory and stored in fooproj.kdevelop as
  <activedirectory>src</<activedirectory>

2. add a new class using "Project" -> "New Class" and call it "wizbang"

  The QMake file src/src.pro is correctly updated, no extra slash at the
  beginning of file names.

  --- src/src.pro ---
  HEADERS += wizbang.h
  SOURCES += fooproj.cpp \
             wizbang.cpp
  TARGET=../bin/fooproj
  ---

B/ A hand-crafted QMake project

1. modify previous project

  I took the previous project and moved the files from "src" up one
  level, replaced fooproj.pro by src.pro, suitably modified:

  --- fooproj.pro ---
  HEADERS += wizbang.h
  SOURCES += fooproj.cpp \
             wizbang.cpp
  TARGET=bin/fooproj
  ---

2. add a new class using "Project" -> "New Class" and call it "foobar"

  Here we get the problem you described, fooproj.pro now contains:

  HEADERS += wizbang.h \
             /foobar.h
  SOURCES += fooproj.cpp \
             wizbang.cpp \
             /foobar.cpp
  TARGET=bin/fooproj

Jeremy

- --
http://www.jerryweb.org/             : JerryWeb.org
http://sailcut.sourceforge.net/      : Sailcut CAD
http://opensource.polytechnique.org/ : Polytechnique.org Free Software
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDHoxd4mJJZqJp2ScRAnZUAJ4mDBeE/3j5Tp5Wwm3qCBFoaNgSIgCePejV
+Df5T3zCeg6p9fyUDdeVLfo=
=2/al
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to