Qt2.x template bug in KDevelop1.1final

W. Tasin tasin at e-technik.fh-muenchen.de
Mon Mar 6 12:44:43 UTC 2000


Falk Brettschneider wrote:
> 
> "W. Tasin" wrote:
> >
> > Falk Brettschneider wrote:
> > >
> > > Hi,
> > >
> > > I found another bug in the Qt2.x SDI template (RedHat6.1).
> > > The app wizard went fine. But after that a build (of a test project
> > > called 'qqqqqqqq') for the first time interrupts with:
> > >
> > > cd .. && automake --gnu qqqqqqqq/Makefile
> > > cd .. && perl am_edit qqqqqqqq/Makefile.in
> > > cd .. \
> > >   && CONFIG_FILES=qqqqqqqq/Makefile CONFIG_HEADERS= /bin/sh
> > > ./config.status
> > > creating qqqqqqqq/Makefile
> > > gmake: *** No rule to make target `qqqqqqqq_DEPENDENCIES', needed by
> > > `qqqqqqqq'.  Stop.
> > > *** Fehler ***
> > >
> > > --
> > >
> > > Ciao,
> > > --Falk
> >
> > Could you give mir a little bit more hints??
> > Was ist w/o sources?
> Do you mean the ./configure output? Don't know what you mean with w/o
> sources...
> - _no_ headers and _no_ sources

THAT'S it...

> 

> .....
> job-working-directory: could not get current directory
> job-working-directory: could not get current directory
> -------------------------------

This happens always if you delete the project path and kdevelop has done
a 
setCurrentPath() to this directory...
(without concerning the templates)

> 
> Clicking on "Build" produces the error message I wrote about the email
> before.
> 
> BTW: The same error is happening when I choose /home/falk instead of
> /home/falk/Projekte.cvs/CORVIS as the project path.
> 
> ???

That's right... this is because you didn't create any sources or
headers...
how should we handle this??
> 
> --
> 
> Ciao,
> --Falk

Ciao

Walter

--
oohhh sveglia.... il mondo e' ammalato, ma x colpa di chi.........
(Zucchero)
:-------W. Tasin, FB 04,
FHM-------------------PGP-KeyID:0x7961A645----------:
<Key-Fingerprint: 1610 835F 0080 32F4 6140  6CF7 A7D0 44CD 7961A645>
<http://wwwkeys.pgp.net:11371/pks/lookup?op=index&search=0x7961A645&fingerprint=on>




More information about the KDevelop-devel mailing list