José Fonseca wrote on 2010-01-12 19:51: > On Mon, 2010-01-11 at 15:28 -0800, Stephan Raue wrote: > >> Hi all, >> >> Am 10.12.2009 17:36, schrieb José Fonseca: >> >>> On Thu, 2009-12-10 at 08:31 -0800, Jose Fonseca wrote: >>> >>> >>>> Module: Mesa >>>> Branch: glsl-pp-rework-2 >>>> Commit: 491f384c3958067e6c4c994041f5d8d413b806bc >>>> URL: >>>> http://cgit.freedesktop.org/mesa/mesa/commit/?id=491f384c3958067e6c4c994041f5d8d413b806bc >>>> >>>> Author: José Fonseca<jfons...@vmware.com> >>>> Date: Thu Dec 10 16:29:04 2009 +0000 >>>> >>>> scons: Get GLSL code building correctly when cross compiling. >>>> >>>> This is quite messy. GLSL code has to be built twice: one for the >>>> host OS, another for the target OS. >>>> >>>> >>> >>> >> is there also an solution for building without scons? >> >> i am get the follow when i am crosscompile for x86_64 target with i386 host: >> >> gmake[3]: Entering directory >> `/home/stephan/projects/openelec/build.OpenELEC-intel_x64.x86_64.devel/Mesa-master-20100108/src/mesa/shader/slang/library' >> ../../../../../src/glsl/apps/compile fragment slang_common_builtin.gc >> slang_common_builtin_gc.h >> ../../../../../src/glsl/apps/compile: >> ../../../../../src/glsl/apps/compile: cannot execute binary file >> gmake[3]: *** [slang_common_builtin_gc.h] Error 126 >> gmake[3]: Leaving directory >> `/home/stephan/projects/openelec/build.OpenELEC-intel_x64.x86_64.devel/Mesa-master-20100108/src/mesa/shader/slang/library' >> gmake[2]: *** [glsl_builtin] Error 1 >> gmake[2]: Leaving directory >> `/home/stephan/projects/openelec/build.OpenELEC-intel_x64.x86_64.devel/Mesa-master-20100108/src/mesa' >> make[1]: *** [subdirs] Error 1 >> make[1]: Leaving directory >> `/home/stephan/projects/openelec/build.OpenELEC-intel_x64.x86_64.devel/Mesa-master-20100108/src' >> make: *** [default] Error 1 >> > > Nope, and I don't think it will be easy, since Mesa's makefile system > doesn't support building stuff on a separate dir. > > Yes, and that's a good reason to go back to how it was before -- regenerating the files and checking them in by a developer that made a change to input files.
I will do the necessary changes. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
