kdevelop and cvs

[Stefano Borini]

i have some question not strictly related to kdevelop,
but since i don't know really well the kde sdk i want to manage
the cvs repository at best.

first: what are the files that really need to be added to cvs
repository? i mean. should the admin directory be added? should
Makefile.am ? and so on... i need to produce a cvs version that is compilable
from everyone which have autotools. Not every developer involved in my
project uses kdevelop, so i need an uniform management to prevent misuse.
As far as i understand, Makefile.am is automatically created by kdevelop from
the kdevprj file, so it should not be added to cvs. What happen if some developer
which doesn't use kdevelop need to create a new directory or file? it should
modify the .kdevprj by hand, i guess... how now can recreate Makefile.am files?

second: I need to check for other libraries on the target system. Exactly, i
need to check for libqwt (c++), libblas and liblapack (fortran).
reading on the faq, i noted that changes should be added to configure.in.in.
Good. My question is: as the best approach, should i check for the specific
file (ex: qwt_plot.h) or try to compile and link some simple code?
Where can i find a simple application built with kdevelop that uses other
checks? as suggested, i tried to create a kde-opengl project, but i dont'
have that entry.

pointers to documentation and simple example applications greatful appreciated.

i use kdevelop 2.1.5 for kde3.1, automake 1.5 and autoconf 2.53





-- 

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«