Building .ui files in tar.gz dist

[W. Tasin]

Tarjei Knapstad wrote:

>On Thu, 14 Mar 2002, W. Tasin wrote:
>
><snip>
>
>Well, I upgraded my admin dir with the files from KDevelop2.1Beta2 and 
>that helped a tiny bit. The .cpp files belonging to the .ui files are now 
>included in the dist, but not the headers. No .moc.cpp files are included 
>either. After a distclean, here's the output from one of the subdirs 
>containing Qt stuff (and some other subdirs) when running 'make dist':
>

Only to prevent misunderstandings:
1) "Distclean"
2) "autoconf/automake" ( i.e. make -f Makefile.dist ... here happens the 
am_edit call)
3) "configure"
4) "make dist"

Please do this always if you are creating a dist-tarball.

>
>/usr/local/lib/qt/bin/uic -o SetRootDirectoryDlg.h 
>./SetRootDirectoryDlg.ui
>
<snip>

>awk '    { files[$0] = 1; } \
>END { for (i in files) print i; }'`; \
>test -z "$unique$tags" \
>|| (cd . && etags  $tags  $unique  -o $here/TAGS)
>
>
>So, headers, .cpp and moc files get generated, allthough the moc output is 
>now postfixed .moc instead of .moc.cpp as they do when I do a regular make 
>in my project. Moc is however not run on the other headers I have which 
>need moc processing.
>/usr/local/lib/qt/bin/moc Messenger.h -o Messenger.moc.cpp 
>
Does Messenger.h have a Q_OBJECT call? IIRC am_edit scans the include 
file for this.
[And if you have to insert this begin again with make -f Makefile.dist]

>
>should have been run in the segment I posted above, and the moc.cpp file 
>included.
>
>I'm not sure what other checks I could perform to get to the bottom of 
>this. Suggestions are welcome...
>
><snip>
>
>Cheers,
>
If this all didn't help I would need the Makefile to compare it with 
mine (or better the project).

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>




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