On 5/15/06, André Pönitz <andre@xxxxxxx> wrote:
Larry Martell wrote:
> In the original dir, mainform.h is a link to .ui/mainform.h. When I
> copied everything to a new dir, mainform.h became a regular file, and
> was no longer linked to .ui/mainform.h. Both main.cpp and
> mainform.ui.h include mainform.h (not .ui/mainform.h). When the
> project is built .ui/mainform.h gets generated by uic, but the
> mainform.h in the top level dir is not. When I deleted mainform.h and
> recreated it as a link to .ui/mainform.h the crash went away. I've
> never had an issue like this before, and now I'm wondering how it's
> supposed to be. Should I be including mainform.h or .ui/mainform.h?
As a rule of thumb avoid linking or copying and use the 'original' file
Believe me, I wish I could. Unfortunately, the company I am currently
doing work for does not have any official source code or revision
control system (I use CVS for myself), nor do they have any separate
development and release structures. When I have to make a mod to
software that is being used I cannot break the existing version.
Therefore I am forced to make a copy and modify that. Only when the
new version has been tested and approved for "release" can I archive
the original and make the new version the "official" version :-(
> Should these be linked? Should there be a mainform.h in both the top
> level dir and in .ui?
It's not needed. Place them anywhere you like (or where it is put by
default) and add -I.ui to your compiler options.
To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with
"unsubscribe" in the subject or the body.
List archive and information: http://lists.trolltech.com/qt-interest/