gmane.comp.lib.agar.general

Re: Cross-compiling for Win32 on Linux using mingw32

Julien Nadeau — 2008-12-04T06:15:51

There is no need to pass the -lc parameter. libc is used by default and you would need to explicitely pass the -nostdlib parameter to the linker if you wanted to disable it. Perhaps a -L is missing somewhere? It could be that SDL compiled properly only because of a -L added because it needed a third-party library. Look for the actual location of libc in your tree and try explicitely passing a -L argument for it in your $CFLAGS.

Re: Cross-compiling for Win32 on Linux using mingw32

Julien Nadeau — 2008-12-03T16:44:29

But for some reason ld is not finding it. Maybe a libtool bug? You can try compiling agar using an alternate libtool with the --with-libtool configure option. By default, the version bundled into the distribution is used.

Re: Cross-compiling for Win32 on Linux using mingw32

Ernesto Domato — 2008-12-03T16:37:34

I'd compiled the tests for SDL with mingw32 and they compiled fine, produced the .exe files and they work as expected under wine so it seems that the libc is not missing from the cross-compile enviroment.

Re: Cross-compiling for Win32 on Linux using mingw32

Julien Nadeau — 2008-12-03T15:09:50

No, they both use libc.

Re: Cross-compiling for Win32 on Linux using mingw32

Ernesto Domato — 2008-12-03T14:56:05

That was my first guess, but then I thought about how sdl and freetype compiled without the -lc parameter to the linker or without libc. Is that possible?

Re: [agar]porting agarGUI to embedded system

Julien Nadeau — 2008-12-03T14:51:02

Agar doesn't rely on Unix features and threads are optional. You may have to edit the file access routines in core/file.c and core/dir.c. Graphics is probably going to be the most difficult part. Is there no OpenGL ES available for your platform? This depends on your environment. Usually cross compiling is achieved by setting the $CC environment variable and running configure such that it looks only for components in your cross-compilation tree. The sdl-config and freetype-config in your $PATH must refer to cross-compiled versions of those libraries, for instance.

Re: Cross-compiling for Win32 on Linux using mingw32

Julien Nadeau — 2008-12-03T14:41:35

It would appear that libc is missing from your cross-compile environment?

Re: Cross-compiling for Win32 on Linux using mingw32

Ernesto Domato — 2008-12-03T14:15:08

Well, evidently I did something wrong when I tried to cross compile Agar because I decided to start again with a clean source directory and even using a different directory and it started to compile fine. But now, my problem is linking and these are the last messages when I do make: /home/edomato/dev/Juegos/agar/tmp/agar-1.3.3/core/dso.c:1: warning: -fPIC ignored for target (all code is position independent) /usr/bin/i586-mingw32msvc-gcc -mno-cygwin -D_AGAR_INTERNAL -D_BSD_SOURCE -I/home/edomato/dev/Juegos/agar/tmp/win32-agar/include -I/home/edomato/dev/Juegos/agar/tmp/win32-agar/include/agar -D_AGAR_CORE_INTERNAL -I/usr/local/cross-tools/i386-mingw32/include/SDL -D_GNU_SOURCE=1 -Dmain=SDL_main -I/home/edomato/dev/Juegos/agar/tmp/win32-agar -c /home/edomato/dev/Juegos/agar/tmp/agar-1.3.3/core/dso.c -o dso.o mv -f .libs/dso.lo dso.lo ..../mk/libtool/libtool --mode=link /usr/bin/i586-mingw32msvc-gcc -o libag_core.la -rpath /usr/local/lib -version-info 1:0:0 config.lo core.lo error.lo event

[agar]porting agarGUI to embedded system

zwolfox — 2008-12-03T09:17:58

_______________________________________________ Agar mailing list Agar-xWq8P/a1moLx9BLsLxWUfA< at >public.gmane.org http://libagar.org/lists.html

Re: Cross-compiling for Win32 on Linux using mingw32

Julien Nadeau — 2008-12-02T01:25:12

Can you post the contents of config.log? Was the "include" directory properly generated in the build directory?

Re: Cross-compiling for Win32 on Linux using mingw32

Ernesto Domato — 2008-12-01T16:29:13

Well, I set this enviroment variables: PATH=/usr/i586-mingw32msvc/bin:/usr/local/cross-tools/i386-mingw32/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games CC=/usr/bin/i586-mingw32msvc-gcc and the win32 sdl and freetype libraries are on /usr/local/cross-tools/i386-mingw32. The configure script of agar-1.3.3 runs fine but when I do make, it fails with this: edomato< at >kcita:~/dev/Juegos/cross/agar-1.3.3$ make ==> core make[1]: se ingresa al directorio `/home/edomato/dev/Juegos/cross/agar-1.3.3/core' sh ../mk/libtool/ltconfig ../mk/libtool/ltmain.sh checking host system type... x86_64-unknown-linux-gnu checking for ranlib... ranlib checking whether we are using GNU C... yes checking for object suffix... o checking for executable suffix... no checking for /usr/bin/i586-mingw32msvc-gcc option to produce PIC... -fPIC checking if /usr/bin/i586-mingw32msvc-gcc PIC flag -fPIC works... yes checking if /usr/bin/i586-mingw32msvc-gcc supports -c -o file.o... yes checking if /usr/bin/i586-mingw32msvc-gcc supports

Re: Cross-compiling for Win32 on Linux using mingw32

Julien Nadeau — 2008-12-01T03:37:35

You can probably cross-compile like you would with any other target. Try setting $CC to your mingw32 gcc. Use the --disable-network configure option. configure looks for "sdl-config" and "freetype-config" so make sure that these refer to the mingw32 versions.

Cross-compiling for Win32 on Linux using mingw32

Ernesto Domato — 2008-12-01T03:23:36

Hello, I would like to know if there's some way to compile Agar with mingw32 on a Linux host (I'm using Debian). Thanks for all. Ernesto

Re: Failed to compile 1.3.3 on amd64

Julien Nadeau — 2008-11-03T15:14:29

Thanks, I did leave an "include" directory by mistake; a corrected tarball has just been uploaded. On Mon, Nov 03, 2008 at 12:49:14PM -0200, Ernesto Domato wrote:

Re: Failed to compile 1.3.3 on amd64

Ernesto Domato — 2008-11-03T14:49:14

_______________________________________________ Agar mailing list Agar-xWq8P/a1moLx9BLsLxWUfA< at >public.gmane.org http://libagar.org/lists.html

Failed to compile 1.3.3 on amd64

Ernesto Domato — 2008-11-03T14:27:13

_______________________________________________ Agar mailing list Agar-xWq8P/a1moLx9BLsLxWUfA< at >public.gmane.org http://libagar.org/lists.html

Agar-1.3.3 released

Julien Nadeau — 2008-11-03T13:47:11

I am pleased to announce the official release of Agar 1.3.3. The source code and precompiled packages are now available for download at: http://libagar.org/download.html Release Notes for Agar 1.3.3 (Blackened Soil Remains) ----------------------------------------------------- Here are some of the most notable changes since Agar 1.3.2, in no particular order. - Implemented Ada bindings (thanks rothwell!). - Documentation fixes. Many new manual pages and examples were also added. - Merged Math library (originally from FreeSG) into Agar distribution. - Include files are now preprocessed for addition of visibility-related specifiers (see http://gcc.gnu.org/wiki/Visibility) - Merged ag_net library into ag_core (though API is still not official). - Generated IDE "project files" are now distributed in the source .zip only. - The MAP library has been removed from the Agar distribution and moved to the FreeSG distribution (http://freesg.org/). - Describe important documentation conventions in AG_Intro(3)

Re: problems compiling with msys

Merick — 2008-11-01T11:26:10

Eh, looks like I won't need to compile it myself after all. I'm just a hobby programmer, I use FreeBASIC and know very little about C/C+. The only reason I was trying to compile agar myself is because trying to link to the VC win32 binaries from the download page was making ld (freebasic's linker) crash. I was talking about this with one of the guys in the freebasic channel but when he went to the agar download page he got a different page than what I was seeing. Turns out my browser was caching an older version of the page. After clearing the cache I was able to get the mingw pre-compiled libs ofr 1.3.3, which can be linked into a freebasic program without causing a crash. The only problem now is that I'll have to go through some 300+ agar headers and try to translate them to freebasic's syntax

Re: problems compiling with msys

Merick — 2008-10-29T02:20:57

here's the output from configure: $ ./configure Host: MINGW32_NT-5.1-1.0.10(0.46/3/2)-i686 checking for a usable C compiler...yes checking for compiler warnings...yes checking for IEEE754 floating point...yes checking __bounded__ attribute...no checking __format__ attribute...yes checking __nonnull__ attribute...yes checking __aligned__ attribute...yes checking __packed__ attribute...yes checking for long double...yes checking for long long...yes checking for cygwin environment...yes checking for ...yes checking for 64-bit types...no checking for conflicting typedefs...no checking for ...yes checking for ...no checking for ...yes checking for the __progname variable...no checking for free(NULL) is a no-op...yes checking for the C math library...yes checking for a gethostname() function...no checking for a getpwuid() function...no checking for a getuid() function...no checking for a getenv() function...yes checking for setenv() and unsetenv()...no checking for a

Re: problems compiling with msys

Julien Nadeau — 2008-10-29T00:31:46

This means configure did not succeed, or the file would be there. Can you post the ./configure output and config.log contents? By the way, I've added a check to configure to prevent it from picking up directories when looking for executables. That would have prevented the /mingw/lib/gcc/ from causing any problems.

Re: problems compiling with msys

Merick — 2008-10-28T23:53:04

Ack, it actually was in the path, I must have looked at that a dozen times before I saw it. I removed it from the windows path and got the configure script to run, but make failed because it couldn't find "config/threads.h"