Horde3D

Next-Generation Graphics Engine
It is currently 22.11.2024, 06:46

View unanswered posts | View active topics


Board index » Horde3D Usage » Support

All times are UTC + 1 hour




Post new topic Reply to topic  Page 1 of 1
  [ 5 posts ] 
  Print view Previous topic | Next topic 
Author Message
BigDragon
PostPosted: 27.09.2010, 17:55 
Offline

Joined: 27.09.2010, 16:54
Posts: 2
I'm trying to compile Horde3d on 64-bit Fedora 13. I've run into a problem with both the zipped sourceforge release and latest SVN copy. I don't understand what the output is trying to tell me or how to fix this problem.

Code:
[ 42%] Built target Horde3D
[ 43%] Built target Horde3DUtils
[ 54%] Built target ColladaConv
[ 91%] Built target glfw
Linking CXX executable ../../Binaries/Linux/Chicago
/usr/bin/ld: ../../Dependencies/Source/glfw/libglfw.a(x11_window.o): undefined reference to symbol 'XGrabKeyboard'
/usr/bin/ld: note: 'XGrabKeyboard' is defined in DSO /usr/lib64/libX11.so.6 so try adding it to the linker command line
/usr/lib64/libX11.so.6: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[2]: *** [Horde3D/Binaries/Linux/Chicago] Error 1
make[1]: *** [Horde3D/Samples/Chicago/CMakeFiles/Chicago.dir/all] Error 2
make: *** [all] Error 2


How can I fix this compilation problem? I have Horde3d working fine on a Windows box, but I'd also like to use it on a Linux box too. Thanks for any help!
Top
 Profile  
Reply with quote  
BigDragon
PostPosted: 27.09.2010, 20:14 
Offline

Joined: 27.09.2010, 16:54
Posts: 2
I poked around some more and found that adding -lX11 to the Chicago and Knight link.txt files fixed the problem. I didn't think to try that earlier.

Now I've got an OpenGL 2 error. Still working on this one.
Code:
Horde3D Log

Horde3D 1.0.0 Beta4

0.000   
Initializing GL2 backend using OpenGL driver '2.0 Mesa 7.8.1' by 'Advanced Micro Devices, Inc.' on 'Mesa DRI R600 (RV620 95C0) 20090101  TCL DRI2'
0.000   
Extension EXT_texture_compression_s3tc not supported
0.000   
Failed to init renderer backend, debug info following
0.000   
Supported extensions: 'GL_ARB_depth_texture GL_ARB_depth_clamp GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_imaging GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_shader_objects GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_MESAX_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_logic_op GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_convolution GL_EXT_copy_texture GL_EXT_draw_range_elements GL_EXT_framebuffer_object GL_EXT_fog_coord GL_EXT_gpu_program_parameters GL_EXT_histogram GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texture GL_EXT_texture3D GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_APPLE_packed_pixels GL_ATI_blend_equation_separate GL_ATI_texture_env_combine3 GL_ATI_texture_mirror_once GL_ATI_separate_stencil GL_IBM_multimode_draw_arrays GL_
Top
 Profile  
Reply with quote  
Volker
PostPosted: 27.09.2010, 22:20 
Offline
Tool Developer

Joined: 13.11.2007, 11:07
Posts: 1150
Location: Germany
BigDragon wrote:
I poked around some more and found that adding -lX11 to the Chicago and Knight link.txt files fixed the problem. I didn't think to try that earlier.


I guess that's a problem in the CMakeLists.txt of GLFW, since GLFW is responsible for the keyboard input. I currently don't have a running linux system, so if anyone could figure out, what has to be added to the CMakeLists.txt to let GLFW link against X11 it would be helpful.

Concerning your extension problem, I'm not sure why we demand that s3tc is available. I guess it should be possible to make it optional as well, but anyway the Mesa driver seems to have problems with s3tc.
Top
 Profile  
Reply with quote  
AlexL
PostPosted: 28.09.2010, 09:39 
Offline

Joined: 24.03.2010, 10:17
Posts: 55
We had the problem as well and changed this this globally.
when compiling on Linux we SET(LINUX_ADD_LIBS "X11") in the top CMakeLists.txt
and changed all Samples CMakeLists.txt to (e.g. for Chicago sample)
target_link_libraries(Chicago Horde3D Horde3DUtils glfw ${LINUX_ADD_LIBS} )

And as we're linking statically against GLFW we have to include X11 "by hand" I think, as no other shared lib pulls in X11.
Top
 Profile  
Reply with quote  
Volker
PostPosted: 01.10.2010, 13:54 
Offline
Tool Developer

Joined: 13.11.2007, 11:07
Posts: 1150
Location: Germany
Can someone test if the following patch works?

Maybe we should change the way the different platforms are configured through CMake to a more centralistic approach like proposed by AlexL, but for now I think we keep things more consistent with specifying the additional library dependencies within the app CMakeLists.txt files.


Attachments:
File comment: X11 linking when using CMake
x11.patch [2.36 KiB]
Downloaded 734 times
Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 1
  [ 5 posts ] 

Board index » Horde3D Usage » Support

All times are UTC + 1 hour


Who is online

Users browsing this forum: No registered users and 13 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group