Unable to execute in Debug Mode

[Kapil]

And try running "make sub-src" instead of pure "make", this should only compile the libraries you need (provided that you already have the release mode files). Of course it's all in addition to what's already been said (make clean could also help if you still get errors on the windowsxp style, which you won't be able to use on Windows2000 anyway).

hi wysota...

a strange thing is happening.. when i am trying to run make sub-src, its taking too much of memory... and saying that no memory left on device.. i had more than 250 MB free for this purpose and strangely all of it is consumed while compiling.. this is strange.. never happened before when i used just "make".. what can be the reason for it.. the error which it displays before exiting is this..

[HTML]
g++ -mthreads -Wl,-enable-stdcall-fixup -Wl,-enable-auto-import -Wl,-enable-runt
ime-pseudo-reloc -shared -Wl,--out-implib,C:\Qt\4.1.1\lib\libQtSvgd4.a -o "..\..
\lib\QtSvgd4.dll" object_script.QtSvgd.Debug -L"C:\Qt\4.1.1\lib" -L"C:\Qt\4.1.1
\lib" tmp\obj\debug_shared\QtSvgd_resource.o -lQtXmld4 -lQtGuid4 -lQtCored4
Creating library file: C:\Qt\4.1.1\lib\libQtSvgd4.a
C:\MinGW\bin\..\lib\gcc\mingw32\3.4.2\..\..\..\..\ mingw32\bin\ld.exe: final link
failed: No space left on device
collect2: ld returned 1 exit status
mingw32-make[3]: *** [..\..\lib\QtSvgd4.dll] Error 1
mingw32-make[3]: Leaving directory `C:/Qt/4.1.1/src/svg'
mingw32-make[2]: *** [debug-all] Error 2
mingw32-make[2]: Leaving directory `C:/Qt/4.1.1/src/svg'
mingw32-make[1]: *** [sub-svg-make_default-ordered] Error 2
mingw32-make[1]: Leaving directory `C:/Qt/4.1.1/src'
mingw32-make: *** [sub-src] Error 2
[/HTML]

[ChristianEhrlicher]

As I said - you're using the wrong qmake.exe...
You build Qt4.1.1 with debug in C:\Qt\4.1.1 but you run qmake.exe from 4.1.0 in C:\Qt\4.1.0. This 'old' qmake is using the library-paths from 4.1.0 and not the paths from 4.1.1.
Rerun qmake (c:\Qt\4.1.1\bin\qmake).

[Kapil]

As I said - you're using the wrong qmake.exe...
You build Qt4.1.1 with debug in C:\Qt\4.1.1 but you run qmake.exe from 4.1.0 in C:\Qt\4.1.0. This 'old' qmake is using the library-paths from 4.1.0 and not the paths from 4.1.1.
Rerun qmake (c:\Qt\4.1.1\bin\qmake).

okay... what option should i specify with qmake.. shold it be -makefile

[ChristianEhrlicher]

okay... what option should i specify with qmake.. shold it be -makefile

Please think before you post...
You should execute c:\Qt\4.1.1\bin\qmake and not c:\Qt\4.1.0\bin\qmake . If you used some options before, you should use them now too.

[Kapil]

Please think before you post...
You should execute c:\Qt\4.1.1\bin\qmake and not c:\Qt\4.1.0\bin\qmake . If you used some options before, you should use them now too.

Hi..

Its working now...

Thanks a lot for pointing out my mistake... next time i would definetly work out all my options before posting so that it does not create inconvenience for you all... Sorry for that..

take care..

with regards,
Kapil

[wysota]

a strange thing is happening.. when i am trying to run make sub-src, its taking too much of memory... and saying that no memory left on device.. i had more than 250 MB free for this purpose and strangely all of it is consumed while compiling.. this is strange.. never happened before when i used just "make".. what can be the reason for it.. the error which it displays before exiting is this..

You ran out of disk space. Debug libraries are much (and I mean much) larger than release ones so you need much more disk space to build them. No matter if you run make or make sub-src, the process of building the libraries will be the same, because make calls sub-src target anyway. The difference is that other components (like tools, etc.) won't be built when using make sub-src. It's simply faster this way.

[Kapil]

I am running out of major space..

I didnt know it and had not kept much of space... i am deleting or moving many of the files now.. it has nearly taken 2.00 GB space.. dont know how much more will it take... does it take so much ????

Also,
But why is it so that the programs which were running with 4.1.0 in the release mode are not getting compiled now (4.1.1 -debug)...

In my applications, i had directly included the #include files.. ie #include <Q3Canvas> and #include <Q3CanvasView>... earlier they were running fine but now it is saying that these files are not found whereas they are where they should be...

do i have to give the full path... or the path of the header file ????

[wysota]

I didnt know it and had not kept much of space... i am deleting or moving many of the files now.. it has nearly taken 2.00 GB space.. dont know how much more will it take... does it take so much ????

It depends whether you compile both debug and release or only debug. It shouldn't take more than a gigabyte or so. Maybe it's your Windows swap file that's eating your resources?

Also,
But why is it so that the programs which were running with 4.1.0 in the release mode are not getting compiled now (4.1.1 -debug)...

Because you don't have debug structures and libraries in your installation.

In my applications, i had directly included the #include files.. ie #include <Q3Canvas> and #include <Q3CanvasView>... earlier they were running fine but now it is saying that these files are not found whereas they are where they should be...

You might have a broken or incomplete installation.

do i have to give the full path... or the path of the header file ????

If your installation is correct and your project file is correct (QT+=qt3support), you should be able to call them without paths.

[Kapil]

Hi...

I got this error when i compiled everything... when i tried to execute the .exe which was created in the debug mode...

it said..
[HTML]
The dynamic link library Qt3Support4.dll could not be found in the specified path...
// and then it showed me the entire Environment variables path...
[/HTML]

now from where do i get the Qt3Support4.dll.. The compilation was fine.. and there came no errors also which were coming earlier.... I have also included the directory path in the Enviroment variables and it is showing it also...

[wysota]

You are building your application in release mode. Do you have release mode libraries compiled too?

[Kapil]

Hi..

I am not building the application in the release mode...

So far what i was doing was to add "CONFIG += release" in my .pro file as u had suggested once to make my application run...

but today after compiling in debug mode, it gave this error...

[jacek]

Do you have "Qt3Support4.dll" file on your system somewhere?

[Kapil]

Do you have "Qt3Support4.dll" file on your system somewhere?

Hi..

yes i do have it.. its there in the C:\Qt\4.1.1\bin...

[jacek]

yes i do have it.. its there in the C:\Qt\4.1.1\bin...

Is it also in C:\Qt\4.1.1\lib?

[Kapil]

Hi..

Nope.. its not there at the C:\Qt\4.1.1\lib... but i have the Qt3Supportd4.dll present in the lib folder of the QtDIR...
In fact i have all of these file sin support to the Qt3Supportd4.dll


libQt3Support4.a
libQt3Supportd4.a
Qt3Support.prl
Qt3Supportd.prl
Qt3Supportd4.dll


Now what should i do ????????

Kapil

[Kapil]

Hi...

Its working now..

Basically i had not set the path C:\Qt\4.1.1\lib in the enviornment variables... i didnt know that i have to do that also.. i just thought that i have to set only the "bin" path which is "c:\Qt\4.1.1\bin".. now that i have done that its working...

is it correct this way ??? like in the docs it was no where mentioned to mention the "lib" path as well in the enviornment variables???????
so if its correct then this updation can be made in the docs.. or if its just a forced way to make the application run, then what is the proper way of getting things done...

Thanks a lot for all the help everyone has provided...

with due regards,
Kapil