search

tonkv / qdevelop

Automatically exported from code.google.com/p/qdevelop
0 stars 0 forks source link

Add support to add custom build targets to project file #49

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Add support to the project settings dialog to add and edit custom build
targets.

Example of custom build target:

doxdoc.commands = doxygen
doxdoc.depends = Doxyfile FORCE
doxdoc.target = doc

QMake will create a target "doc" inside the generated Makefiles that allows
me to create Doxygen documentation using make:

> make doc

-Jens

Original issue reported on code.google.com by jens.re...@gmail.com on 5 Dec 2006 at 9:31

GoogleCodeExporter commented 9 years ago 
QDevelop breaks custom build targets at the moment, because it reorders the 
commands 
(or generally all variable values). I manually added a build target for 
cvs2cl.pl:

cvs2cl.commands = ./cvs2cl.pl --hide-files --no-times
cvs2cl.target = changelog

QDevelop reorders the commands by name:

cvs2cl.commands = --hide-files \
  --no-times \
  ./cvs2cl.pl

Solution: QDevelop should only reorder header, source, ui, resource and 
translation 
files.

-Jens

Original comment by jens.re...@gmail.com on 10 Feb 2007 at 12:16

GoogleCodeExporter commented 9 years ago 
Version 0.24 had some changes in this area. Can you test version 0.24 and 
re-confirm?
I would like to close this bug if possible.

Thanks!

Original comment by cucoma...@gmail.com on 22 Sep 2007 at 8:55

GoogleCodeExporter commented 9 years ago 
I will have a look at this in the upcomming week.

-Jens

Original comment by jens.re...@gmail.com on 23 Sep 2007 at 11:09

GoogleCodeExporter commented 9 years ago 
QDevelop still reorganize everything hence great problems with self-written 
projects.

Original comment by Lord.Div...@gmail.com on 30 Jan 2009 at 4:06

GoogleCodeExporter commented 9 years ago

Original comment by Lord.Div...@gmail.com on 14 Feb 2009 at 7:40