- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello!
I have compiled TBB 4.1 from source in Windows 7 using the MingW compiler. I got both the debug and release libs: tbb_debug.dll and tbb.dll.
I have also this trivial code to test the installation:
[cpp]#include "tbb/task_scheduler_init.h"
#include <iostream>
int main(void) {
tbb::task_scheduler_init init;
std::cout << "Ok" << std::endl;
return 0;
}[/cpp]
Compiling the code from the Windows terminal with g++.exe -I%TBB_INCLUDE% -L%TBB_DEBUG_LIB% -l tbb_debug.dll
and executing it goes perfectly.
However, if I try to do the same from QtCreator the compilation is stopped with this error message:
[plain]E:/LIBRERIAS/tbb-4.1_src/build/windows_intel64_gcc_mingw4.5.4_debug/tbb_debug.dll: file not recognized:
File format not recognizedcollect2: ld returned 1 exit status[/plain]
Here's the project pro file:
[plain]TEMPLATE=app
CONFIG+=console
CONFIG-=qt
SOURCES+=main.cpp
#QMAKE_CXXFLAGS+=-fopenmp
#QMAKE_LFLAGS+=-fopenmp
INCLUDEPATH+="E:/SITEGI/LIBRERIAS/tbb-4.1_src/include"
LIBS+=-L"E:/SITEGI/LIBRERIAS/tbb-4.1_src/build/windows_intel64_gcc_mingw4.5.4_debug"-ltbb_debug[/plain]
Why isn't the linking working with QtCreator?.
Cheers!.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Could you look at 'tbb_debug.dll' properties ( 'Version' property page ) in the Windows Explorer? Where did it come from?I'm not used to work in Windows... Do you mean right-clicking on the dll, "properties" and then into "previous versions"???. 0.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Congratulations!Thanks to you!.
I think this is how a make file you used was createdIt's the one that came with the tgz.
and it looks like as undocumented feature, or a bug (?I think it's an undocumented feature. Looking at the 'vproj' file I found several lines like this: [plain]< Configuration Name="Debug|x64" OutputDirectory="$(SolutionDir)intel64\$(ConfigurationName)" IntermediateDirectory="$(SolutionDir)intel64\$(ConfigurationName)" ConfigurationType="2" CharacterSet="0" >[/plain] It seems that when you don't define the arch, it defaults to that name. Am I right? o.o
Yes, of course.Where can I do that?. I dont' find any button/link to mark the question as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Adri C. S. wrote:In case you do not provide "arch" argument there is a runtime detection. It looks that by default gcc build the sample for intel64 arch. x64 is the value that is used in visual studio configurations de facto. We do not want to invent a wheel there. But makefiles use intel64 for 64 bit configurations. --Vladimir
Just a question, if the 64 but version name is x64, why when I typed "make compiler=gcc" it defaulted to intel64?. I'm curious, since both of them work well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In case you do not provide "arch" argument there is a runtime detection. It looks that by default gcc build the sample for intel64 arch. x64 is the value that is used in visual studio configurations de facto. We do not want to invent a wheel there. But makefiles use intel64 for 64 bit configurations.Didn't know that. Thanks!.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page