Re: [Cegcc-devel] xvid codec compile with cegcc
thanks a lot , danny... It works!! On 3/29/07, Danny Backx <[EMAIL PROTECTED]> wrote: Hi, I've taken the 1.1.2 release off the xvid site. On Wed, 2007-03-28 at 12:15 +0800, Hudson Hsueh wrote: > I want to cross-compile Xvid codec(http://www.xvid.org/)(from svn) > with cegcc(compiled from svn) for my WM 5.0 device, > I tried for several days and now I was stuck on some problem. > > Following is My configure command, > > ./configure CC=/opt/cegcc/bin/arm-wince-cegcc-gcc --host=arm I don't think that'll do what you want. Try this : % setenv CC arm-wince-cegcc-gcc % ./configure --host=i586-gnu-linux --target=arm-wince-cegcc You'll note that platform.inc then contains the right CC= line, I mean it'll say the compiler is arm-wince-cegcc-gcc. It doesn't mention the right ranlib though. Similarly the Makefile uses $(AS), so I tried again but also specified % setenv RANLIB arm-wince-cegcc-ranlib % setenv AS arm-wince-cegcc-as and then % ./configure --host=i586-gnu-linux --target=arm-wince-cegcc % make Running this compiles some of the sources, then fails with : L: libxvidcore.so Info: resolving _CRT_MT by linking to __imp__CRT_MT (auto-import) /opt/cegcc/lib/gcc/arm-wince-cegcc/4.1.0/../../../../arm-wince-cegcc/lib/libcegcc.dll.a( main.o):main.c:(.text+0x28): undefined reference to `WinMain' collect2: ld returned 1 exit status gmake: *** [libxvidcore.so] Error 1 This is the error you were getting too. The reason is that the xvid configure script tries to figure out what your build environment is, and adds some platform specific stuff in e.g. SPECIFIC_LDFLAGS. Look at line 267 and further in configure.in. I've added a couple of lines saying : cegcc*) AC_MSG_RESULT([ok]) STATIC_LIB="libxvidcore.\$(STATIC_EXTENSION)" SHARED_LIB="libxvidcore.\$(SHARED_EXTENSION).\$(API_MAJOR).\ $(API_MINOR)" SPECIFIC_LDFLAGS="-shared -lc -lm" SPECIFIC_CFLAGS="" ;; and then ran % autoreconf % ./configure --host=i586-gnu-linux --target=arm-wince-cegcc % make This ended with : L: libxvidcore.a L: libxvidcore.so.4.1 --- XviD has been successfully built. * Binaries are currently located in the '=build' directory * To install them on your system, you can run '# make install' as root. --- I assume I've answered the "howto" question, but have I also given you enough info to understand the problem and the solution ? Cheers, Danny -- Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
[Cegcc-devel] Qt on CE (was: newlib/wince)
Peter Kümmel wrote: > By the way, currently we use wcelibex for a port of Qt to wince > so we are in the same position as you, or worse because we only > support the ms tools: is it :) or :( ? I took a quick look at wcelibex, and it seems to be more or less of the same scope as libmingwex.a - which is linked in by default on mingw32ce, and is a static lib. I don't quite understand what you mean by being in the same position, but if I have to chose, it is a :):) I'm trying to cleanup my Qt4 port, which is currently 4.1 based. Unfortunately I've touched many files, which makes it non-trivial to merge into your Scusi (4.2 based). Here is my diffstat: 147 files changed, 9267 insertions(+), 1985 deletions(-) That's Core + Gui + Network + qt3support + svg + xml + some examples + some demos + a port of minesweeper from qt embedded (qt2). Too bad TT doesn't accept user contributions... It is really sad... I've been holding this port for what ??? almost two years latent on my drive, waiting to have a stable enough toolchain to release it. I'll upload it somewhere and then work from there. I should have released it much sooner, but there was always that something else waiting to be done. (Let me know if you want to take a look at the patch in the meantime.) Cheers, Pedro Alves - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
[Cegcc-devel] New gdb support in gdb cvs head.
Hi all, The new gdb support based on gdbserver is now installed into gdb cvs head at http://sourceware.org/gdb/ To build it, you will need a little patch, so configure accepts the arm-wince-mingw32ce target. I'm waiting for autoconf folks to accept the mingw32ce target name, so I can commit that patch, but in the meantime, if anyone wants to test it, let me know, and I'll guide you. Particularly interesting would be to hear from people with 64bit machines that can't build the gdb in our svn. Oh, and with this new version, mingw32ce should build on all the platforms the GNU tools support (that's linux, *BSD, Solaris, MacOS, Windows, Cygwin, x86, PPC, SPARC, you name it.) (cegcc still uses some hacks that are non portable in its build process.) Cheers, Pedro Alves - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
