KDevelop integration?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

KDevelop integration?
by ac on Sunday 11/Sep/2005, @13:10

How are the issues (hard to parse existing Python build scripts since they are too powerful to catch all possibilities) raised in the past on the mailinglists about integration of the new building system into KDevelop to be solved? Strictly limiting API/syntact to the amount understood/supported by KDevelop? With everything not complying being thrown out from the SVN? Who is going to monitor this?

Related Links

·   Articles on Developer
·   Also by ac
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: KDevelop integration?
by Michael Pyne on Sunday 11/Sep/2005, @13:38

From what I understand bksys will also be able to support a XML description of the target and its build dependencies, etc. The idea is to make it possible to do most of what you'd need to do using XML alone (which is machine-parsable, and can therefore be understood by KDevelop). Not sure how successful it will be, but there are KDevelop guys already working on it.

[ Reply To This | View ]

Re: KDevelop integration?
by manyoso on Sunday 11/Sep/2005, @18:13

Well, one idea was to embed the python interpreter in KDevelop and then query scons directly via it's API. With the information returned from the API we could write out a SConstruct file that KDevelop could understand.

Unfortunately, this does not seem possible. SCons API is nearly impossible to understand and it doesn't seem that the relevant information (a list of sources, etc, etc) are maintained in any member variables we can get access to.

So, probably what mpyne said above ;)

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"He may be a Hotmail user, but the patch works, so who am I to argue?" -- Charles Samuels
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.