[bt-devel] Count me in.

[Martin Gruner]

Gabriel,

that's really weird.

Please don't waste your energy with this. As long as it builds correctly 
("make install"), we're fine. It is just good to know ("make distcheck") that 
it also uninstalls fine... And up to now we didn't have .ui files so we could 
always check. 
But if you have to make major changes, that would perhaps not be worth the 
time. Would be good to know what others did with this...

mg


Am Mittwoch, 15. März 2006 18:22 schrieb Gabriel M. Beddingfield:
> On Tue, March 14, 2006 6:01 pm, Martin Gruner said:
> > It seems that .cpp files are autogenerated from the .ui files in
> > $(srcdir),
> > while the .h files are generated in the _build directory. That's why moc
> > cannot find the file on my system. And moc tries to generate a .moc file
> > in
> > _build.
> >
> > What do you say, should not all .cpp, .h and .moc files be generated in
> > the
> > $(srcdir), and _build only contain Makefiles and .o files? Or am I
> > missing something? I don't know how the system is intended to work...
>
> It looks like it keeps the sources pristeen ('chmod -R a-w *') and that
> *all* automatically generated files (including MOC'ed and UIC'ed files) go
> into the _build directory.  When building, there is -I. for the _build/foo
> directory that you are in.  The problem is when you are in _build/foo and
> you nead a generated header in _build/bar.
>
> I've got something that works now, but I'm investigating if it's the
> *right* way.  First, I undid my previous fix.  Then, I'm adding
> -I$(top_builddir)/bibletime to the CPPFLAGS, and changing #include
> references to 'searchresultsform.h' and the like to
> 'frontend/searchdialog/searchresultsform.h'.  I'm doing a little
> investigating to see if this is the right way.
>
> While this works, I have a hard time believing we're the only ones who
> encountered this problem in using 'make distcheck' with .ui files.  I'll
> see if I can find what other people have done (just short of switching to
> unsermake).
>
> One odditiy:  make distcheck appears to generate all UIC'ed .h and .cpp
> files before creating the dist package.  However, those .h and .cpp files
> don't make it into the package.  Wierd.  Do we want them in the package?
> (I.e. no need for UIC when compiling the tarball.)
>
> BTW, on the subject of unsermake, I also think we should migrate to
> unsermake... but probably after 1.6 and SVN.
>
> Peace,
> Gabriel