If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Anybody know how toget a checkout into Kdevelop? or for that matter, if Kdevelop wasn't used to make the project what was?

I've already go a binary vers of XaraLX which is OK as far as it goes, but (?perhaps deliberately?) none of the exporting/printig functions work....

Again no surprises there. I do have an old windows vers. of XarA (having originally had Artworks on the RiscPC) and I CAN VNC onto a box running that if need be but a 'full version' on linux would be nice.

Looks like find_if ain't there... only instance is in the code that failed..

Seen this sort of thing before when trying to get a valid build for KDE - but in this case
evidently no activity (svn log) for a looonnng time.

It may be that the development has moved off elsewhere and what I am looking
at is just an abandoned residue. If so, 'tis better if I know that now without
having to waste any further time on it.

Obviously, unless I restore the original development environment
(I'm guessing that that was Kdevelop). I'm not going to get too far.
At the moment, I'm trying to
persuade Kdevelop to 'adopt' this project, but so far less than
successfully..

Re: svn 1785

Originally Posted by Soquili

Sedric the page I referenced shows that GCC/G++ are required to compile XaraLX. KDevelop needs to be configured to compile GCC/G++ source.
See the references in the google search http://www.google.com/search?hl=en&q=gcc&as_q=kdevelop
Very few Linux developers ever visited these forums. The members of Talkgraphics are mostly users of graphics software rather than developers.

I did get as far as the gcc/g++ deduction. (A look at the checkout full of .cpp source files vaguely hints at that...). The make did run for quite a few steps before it
barfed on the file shown. Since the steps in the make before this one succeeded,
one can reasonably infer that gcc/g++ are present and working.

What I wanted to know is how, given a checkout from some
project [probably originally generated by] Kdevelop one goes about re-introducing
this project into Kdevelop so as to continue working on it..

It has been suggested that I try the dev maillist - so I may do that, next time I've
got a hour to spare.