[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
MSYS+MSVC for libtool branch-2-0
From: |
Peter Ekberg |
Subject: |
MSYS+MSVC for libtool branch-2-0 |
Date: |
Tue, 24 May 2005 23:46:37 +0200 |
Hello!
I started an attempt to support the MSVC compiler natively
(w/o the cccl script, which I haven't tried to be honest)
and using MSYS to drive the scripting. With this (rough)
patch I am able to build and use shared libraries (libs
and modules) and convenience libraries. I haven't tested
static libs (I haven't gone through the pain of bootstraping
on Cygwin, which would require building some current
autotools from scratch.)
I realize that this is not likely an acceptable patch.
Perhaps libname_spec should be just $name on MSVC? Instead
of doing that, I added a second very similar loop in
ltmain.sh, but that might be a cludge?
This patch was taken from a libtoolized project (I wrote
the patch), I think I converted all [...] in its ltmain.sh
to [[...]] when I patched ltmain.m4sh in libtool branch-2-0,
but I'm not 100% sure as I didn't actually test the result
(due to the above bootstrap troubles).
But I'd very much appreciate comments on the general
approach, so that I know if I should just throw the whole
thing in the bin now rather than later if I'm way off...
I configure the libtoolized project with
.../configure CC="cl -MD" LDFLAGS=-L/msvc/lib
Where MSYS has a mount so that /msvc points to the MSVC folder
(typically "C:\Program Files\Microsoft Visual Studio\VC98"
or something similar)
Cheers,
Peter
- MSYS+MSVC for libtool branch-2-0,
Peter Ekberg <=
- MSYS+MSVC for libtool branch-2-0, Peter Ekberg, 2005/05/24
- RE: MSYS+MSVC for libtool branch-2-0, Peter Ekberg, 2005/05/25
- RE: MSYS+MSVC for libtool branch-2-0, Peter Ekberg, 2005/05/25
- RE: MSYS+MSVC for libtool branch-2-0, Peter Ekberg, 2005/05/26
- RE: MSYS+MSVC for libtool branch-2-0, Peter Ekberg, 2005/05/28