[GRASS5] New makefiles - work in progress, take 'em for a spin

[Mike Thomas]

Hi Eric.

I did a quick run on your new Makefiles on Win32 using Cygwin but I run into
problems straight away:

make[1]: Entering directory `/cygdrive/f/source/cvsroot/grass/src'
make[2]: Entering directory `/cygdrive/f/source/cvsroot/grass/src/libes'
make[2]: Leaving directory `/cygdrive/f/source/cvsroot/grass/src/libes'
make[1]: Leaving directory `/cygdrive/f/source/cvsroot/grass/src'
make[1]: Entering directory `/cygdrive/f/source/cvsroot/grass/src'
make[2]: Entering directory `/cygdrive/f/source/cvsroot/grass/src/libes'
make[3]: Entering directory
`/cygdrive/f/source/cvsroot/grass/src/libes/vask'
ld -s  -shared -lc    \
 V_call.o V_clear.o V_const.o V_exit.o V_init.o V_line.o V_ques.o V_error.o
V_support.o V_acc.o V_trim_dec.o V_tty.o   -o libvask.so
V_call.o(.text+0x99):V_call.c: undefined reference to `_alloca'
V_call.o(.text+0x10a):V_call.c: undefined reference to `stdscr'
V_call.o(.text+0x110):V_call.c: undefined reference to `wmove'
V_call.o(.text+0x132):V_call.c: undefined reference to `stdscr'

etc.

I gather from this that you're aiming to produce a shared lib (.so) under
Unix and presumably a DLL under Windows, for each subdir in libes.

If so, things are more complicated under Windows than for Unix, as Windows
DLL's don't work the same as Unix shared libraries.  Let me know what your
intention is, and I'll try and help out from the Windows side.

To further complicate matters, I'm not certain what the relationship between
Cygwin .so libraries and Windows DLL's might be - I'm diving into the docs
now to find out.

Cheers

Mike Thomas.


----- Original Message -----
From: Eric Mitchell <emitchell at altaira.com>
To: <grass5 at geog.uni-hannover.de>
Sent: Friday, 4 August 2000 12:35 AM
Subject: [GRASS5] New makefiles - work in progress, take 'em for a spin


>
> Attached is a .tgz of the new makefile work I've been
> up to.  If you're adventurous, try it out as follows:
>
> 1) from within the top level grass distribution directory
> gunzip -cd grass.remake.tgz | tar xvf -
>
> 2) if you're using Linux, you'll probably be ok.  If not,
>     you'll have to copy the contents of src/CMD/head/head
>     into the include/Make/Platform.make file.  There are
>     a handful of macro definitions at the end of the file
>     that will need to be edited for your platform of choice.
>
> 3) type "make"
>
> 4) get coffee, tea, or non-caffeinated beverage and
>     enjoy the show.
>
> 5) type "make install" and watch a bunch of files get
>     copied to locations under $GISBASE/$ARCH.  Note that
>     files that can be shared by multiple platforms can
>     be in the same installation tree, as the platform
>     specific files are installed under unique subdirs.
>
> 6) let me know if I'm on the right track here, and should
>     bother with completing the makefiles, editing startup
>     scripts to use the shared libs, etc.
>
>
> -- ebm
> +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
> | Eric B. Mitchell         mailto:emitchell at altaira.com |
> | tel: (301) 809 - 3534    Altair Aerospace Corporation |
> | tel: (800) 7 - ALTAIR    4201 Northview Dr. Suite 410 |
> | fax: (301) 805 - 8122    Bowie, MD  20716             |
> +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
>               ,___
>           /"\  / o=\  /"""---===/
>          /   \_/  \__/   ---===/
>          |    //\   || /""TT""/ //\   || ||""\
>          |   //  \  ||    ||   //  \  || ||__/
>          |  file://--==\ |L--/ ||  file://--==\ || || "=,
>           \      ---===/
>            \____---===/


---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'