From: Michael R. <mr...@us...> - 2003-08-26 18:29:22
|
Hi, > Dear sir(madam), No need to sir us, we are all equals here. > Recently, I have been engaging in transplanting minigui and xine > into Intel's Sitsang board. I have successfully transplanted minigui > into it by now. But I met some diffcult with xine, for there are few > documents to guide me to compile it. For example, how can I run > ./configure? In the process of transplanting minigui,I run it like > this: CC=arm-linux ./configure > > --prefix=/home/sitsang/sitsang_fs/usr > > --build=arm-linux --target=arm-linux --host=i386-linux, where > --prefix is the > > install path of the minigui's lib. I have tried to compile xine as > above, but itfailed. Would you please tell me which options can I use > to follow ./configue and what's the meaning of them? Do they have > similar meanings with those in minigui? Usually, since the configure-scripts are built with the same tool (autoconf), the options are all alike. You can get some explanation with "./configure --help". For cross-compilation, you already found the most interesting options: --build specifies the system of the machine you are building on --host specifies the system of the machine you want the binary to run on --target is only relevant, when compiling a compiler (it specifies the system you want the compiler to compile for) So if you want to build a binary to run on an arm platform, you have to say somthing like ./configure --host=arm-gnu-linux. > Another question: how can the Makefile of xine's know the install > path of minigui? I ask the question because xine relies the on the lib > of minigui. If it is installed in a standard library location like /usr/lib, the build system will have no problem finding it. Otherwise you have to add the library path manually by setting LDFLAGS: ./configure LDFLAGS="-L<path>" Michael -- "If you want to travel around the world and be invited to speak at a lot of different places, just write a Unix operating system." -Linus Torvalds |