0
0

Dear all.
I need to start a development for sound processes.

[b:dfno87oo]I want to use Qt 4.5.2
OS – Windows Vista 32bits
and FMOD libraries.[/b:dfno87oo]

I read that

[i:dfno87oo]Linking (which library to link to)
If you want to use fmodex.dll: (all plugins compiled into the dll, larger main dll size)
Visual Studio users – fmodex_vc.lib.
Metrowerks Codewarrior users – fmodex_vc.lib.
Intel compiler users – fmodex_vc.lib.
Borland users – fmodex_bc.lib.
LCC-Win32 users – fmodex_lcc.lib.
Dev-C++, MinGW and CygWin users – libfmodex.a.[/i:dfno87oo]

I tried all variants of the libraries, but I have same situation – immediate crash of my program. I just made one example:

[code:dfno87oo] FMOD_RESULT result;
FMOD_SYSTEM *system;

result = FMOD_System_Create(&system);       // Create the main system object.
if (result != FMOD_OK)
{
    printf("FMOD error! (%d) %s\n", result, FMOD_ErrorString(result));
    exit(-1);
}[/code:dfno87oo]

if I comment [b:dfno87oo]result = FMOD_System_Create(&system);[/b:dfno87oo] I can start the application.

for any case the project file:

TARGET = Fmod1
TEMPLATE = app
LIBS += -L"lib" -lfmodex
INCLUDEPATH = inc
SOURCES += main.cpp \
mainwindow.cpp
HEADERS += mainwindow.h \
common.h
FORMS += mainwindow.ui

output of compiler:

mingw32-make: Entering directory C:/Users/MAIN/Desktop/Qt/Fmod1'
C:/Qt/2009.03/mingw/bin/mingw32-make -f Makefile.Debug
mingw32-make[1]: Entering directory
C:/Users/MAIN/Desktop/Qt/Fmod1′
c:\Qt\2009.03\qt\bin\uic.exe mainwindow.ui -o ui_mainwindow.h
g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -DQT_NEEDS_QMAIN -I"c:\Qt\2009.03\qt\include\QtCore" -I"c:\Qt\2009.03\qt\include\QtGui" -I"c:\Qt\2009.03\qt\include" -I"inc" -I"c:\Qt\2009.03\qt\include\ActiveQt" -I"debug" -I"." -I"c:\Qt\2009.03\qt\mkspecs\win32-g++" -o debug\main.o main.cpp
g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -DQT_NEEDS_QMAIN -I"c:\Qt\2009.03\qt\include\QtCore" -I"c:\Qt\2009.03\qt\include\QtGui" -I"c:\Qt\2009.03\qt\include" -I"inc" -I"c:\Qt\2009.03\qt\include\ActiveQt" -I"debug" -I"." -I"c:\Qt\2009.03\qt\mkspecs\win32-g++" -o debug\mainwindow.o mainwindow.cpp
C:/Qt/2009.03/qt/bin\moc.exe -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -DQT_NEEDS_QMAIN -I"c:\Qt\2009.03\qt\include\QtCore" -I"c:\Qt\2009.03\qt\include\QtGui" -I"c:\Qt\2009.03\qt\include" -I"inc" -I"c:\Qt\2009.03\qt\include\ActiveQt" -I"debug" -I"." -I"c:\Qt\2009.03\qt\mkspecs\win32-g++" -D__GNUC__ -DWIN32 mainwindow.h -o debug\moc_mainwindow.cpp
g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -DQT_NEEDS_QMAIN -I"c:\Qt\2009.03\qt\include\QtCore" -I"c:\Qt\2009.03\qt\include\QtGui" -I"c:\Qt\2009.03\qt\include" -I"inc" -I"c:\Qt\2009.03\qt\include\ActiveQt" -I"debug" -I"." -I"c:\Qt\2009.03\qt\mkspecs\win32-g++" -o debug\moc_mainwindow.o debug\moc_mainwindow.cpp
g++ -enable-stdcall-fixup -Wl,-enable-auto-import -Wl,-enable-runtime-pseudo-reloc -mthreads -Wl -Wl,-subsystem,windows -o debug\Fmod1.exe debug/main.o debug/mainwindow.o debug/moc_mainwindow.o -L"c:\Qt\2009.03\qt\lib" -lmingw32 -lqtmaind -Llib -lfmodex -lQtGuid4 -lQtCored4
mingw32-make[1]: Leaving directory C:/Users/MAIN/Desktop/Qt/Fmod1'
mingw32-make: Leaving directory
C:/Users/MAIN/Desktop/Qt/Fmod1′

[b:dfno87oo]Could you help me?[/b:dfno87oo] :roll:

  • You must to post comments
0
0

😥

  • You must to post comments
0
0

It is usually better to debug into the application to confirm for sure where it is crashing, and debug into it as deep as you can.

You did not say what type of crash though, and it is good to give a complete complete compilable example too.

  • You must to post comments
0
0

[quote="OvermindDL1":iavr6vzf]It is usually better to debug into the application to confirm for sure where it is crashing, and debug into it as deep as you can.

You did not say what type of crash though, and it is good to give a complete complete compilable example too.[/quote:iavr6vzf]

Type of crash? Wrong library and crash before first code line :(

  • You must to post comments
0
0

[quote="gelemos":2f8bs48p][quote="OvermindDL1":2f8bs48p]It is usually better to debug into the application to confirm for sure where it is crashing, and debug into it as deep as you can.

You did not say what type of crash though, and it is good to give a complete complete compilable example too.[/quote:2f8bs48p]

Type of crash? Wrong library and crash before first code line :([/quote:2f8bs48p]

I’m seeing this same error, and it doesn’t require Qt at all to happen.

I am running on Windows XP, using the latest Cygwin gcc to compile and link the playsound C example.

What happens is that the program ends abruptly, without a core dump or even an error message and ends up back at the cygwin prompt when executing the FMOD_System_Create(&system) call.

I’ve tried placing a

printf("got here\n"); fflush(stdout);

before that line and the "got here doesn’t come out unless I place an exit call after the fflush.

So something weird is going on here.

Any ideas?

  • You must to post comments
0
0

I did some more experimentation, and found that because I had soft-linked the fmodex.dll file into my test directory, that it was silently exiting on the symbol resolution phase.

So I tried just copying the .dll into that directory, and now the test case works better (but I’m still having some issues with getch under cygwin).

  • You must to post comments
Showing 5 results
Your Answer

Please first to submit.