[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop
Subject:    Re: .in files
From:       "W. Tasin" <tasin () e-technik ! fh-muenchen ! de>
Date:       2000-04-13 15:10:32
[Download RAW message or body]

Joachim Ansorg wrote:
> 
> Hi!
> 
> I think it's known that .in files like AUTHORS.in or README.in can be used with the \
> auto tools to generate up to date documents (version number ...). 
> The problem is how to add these file automatically in KDevelop.
> 
> I I add them manually to configure.in the entries are overwritten the next time.
> 
> If I add them to the Makefiles line in the .kdevprj file the following paragraph is \
> added to the files: 
> ####### kdevelop will overwrite this part!!! (begin)##########
> 
> ####### kdevelop will overwrite this part!!! (end)############
> 
> this is not good.
> 
> Is there another how to add these files?

WOW... compliments you are really an advanced user of KDevelop...
if you already tried to search ways like these... :-)

Unfortunately I also didn't find a trick w/o patching KDevelop
to get an automatic result like...
AC_OUTPUT(README AUTHORS ......)

Some days ago I did a patch to allow custom Makefile.am's (was intended
for shared lib support), maybe this helps a little bit...
I know it isn't a clean solution, but here it is:

Your README.in needs only the comment line:
----
# kdevelop-pragma: custom
----

This prevents KDevelop to patch the README.in with
####### kdevelop will overwrite this part!!! (begin)########## ... etc.


> 
> -- Joachim
> BibleTime - the bible study program for KDE
> http://www.bibletime.de/
> info@bibletime.de

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>


[prev in list] [next in list] [prev in thread] [next in thread]