Qt-interest Archive, March 2002
AW: Linker error in VS 6.0 - new problem...
Message 1 in thread
/FORCE seems to be the right choice, then you can delete incremental out of
the Linker options and the sources will be compiled. But I have found
another very ridicoulos problem. When I save the whole data, suddenly the
Compiler (or is it the Linker?) cannot write to ../Debug/xxx.exe.
Seems to be that I have more problems as I expected... Renaming the existing
xxx.exe helps, the compiler runs through... Any ideas what this could
be...??
Björn
> I found out that if you put the implementation of the class's methods
> directly in the header file (when not using the inline
> directive) MS VC++
> creates a separate implementation in each compiled .obj or
> .lib file. This
> does however not apply if you put it directly into the class
> declaration and
> of cource not if you put it into a separate .cpp file.
> Another way seems to
> be to specify /FORCE:mulitple in the linker options as you suggested.
>
> Tom
>
> --
> List archive and information: http://qt-interest.trolltech.com
>
Message 2 in thread
This may be the case when your application didn't shut down correctly after
the previous run and the process is still existent. Then the .exe is
write-locked. You can check this easily by looking up the name of your app
in the task manager. If it's still there after you closed the app window
then this is the problem. I sometimes run into that when I code
multithreaded apps and some class blocks in the destructor when closing.
Tom
-----Ursprüngliche Nachricht-----
Von: "Berg, Björn" [mailto:BERG@genesys-e.de]
Gesendet: Mittwoch, 13. März 2002 10:28
An: 'Thomas.Bauer@fh-joanneum.at'; QT Mailing List (E-Mail)
Betreff: AW: Linker error in VS 6.0 - new problem...
/FORCE seems to be the right choice, then you can delete incremental out of
the Linker options and the sources will be compiled. But I have found
another very ridicoulos problem. When I save the whole data, suddenly the
Compiler (or is it the Linker?) cannot write to ../Debug/xxx.exe.
Seems to be that I have more problems as I expected... Renaming the existing
xxx.exe helps, the compiler runs through... Any ideas what this could
be...??
Björn
> I found out that if you put the implementation of the class's methods
> directly in the header file (when not using the inline
> directive) MS VC++
> creates a separate implementation in each compiled .obj or
> .lib file. This
> does however not apply if you put it directly into the class
> declaration and
> of cource not if you put it into a separate .cpp file.
> Another way seems to
> be to specify /FORCE:mulitple in the linker options as you suggested.
>
> Tom
>
> --
> List archive and information: http://qt-interest.trolltech.com
>
