Re: MSVC Support

[Brendon Costa]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Surely that is very helpful.  Is there a reason you're not contributing
> them to cccl though?  I'm asking because: if we end up with several of
> such wrappers being used widely, Libtool may have to end up supporting
> several, possibly slightly incompatible, "versions" of MSVC, differing
> by wrapper only.  This would make it even harder for us to keep things
> in a working state.

The wrappers I have created work well enough for me in some regards,
they are just small modifications to the original cccl wrapper plus
wrappers for a few other things like lib.exe

I will look at contributing them to cccl if I get somewhere with them
and find them useful, though the state they are in at the moment is
just a "testing/development" state which I don't think people would
yet be interested in.

I have to find some time to look into it further, but currently the
libltdl configure script fails when using the wrappers.


I will try to have a look at the patch later on tonight (If I get some
time after work). If it is just regressions that need to be tested and
there is an appropriate set of tests then I can run it on Windows
using MSVC, and MinGW and on NetBSD and Linux using GCC, but I am
unable to test any other platforms which are probably the ones that
really need to be tested.


> 
> If OTOH your wrappers are good enough to wrap all libtool-needed
> functionality in a way such that it looks like GCC, well, then Libtool
> may just work out of the box with it.  :-)
> But that would be a lot of work to put in such a wrapper, seriously.
> 
I don't know how feasible it will be to have libtool work with these
wrappers straight out of the box. But currently I am able to use
libtool to successfully create static libraries and applications that
use those static libraries without any mods. The shared libs look like
they are coming out as static libs for the moment and I haven't tried
DLOpened modules yet.


I noticed that the libtool script has a few variables like AR, CC, LD,
 objext, libext ... Is there any way to provide those on the command
line, or am I best for now just to edit those in the libtool script
directly?

Also what does libtool use the following variables variables for:

        nm
        strip
        file
        dlltool
        objdump
        as

Does it actually make use of these programs and would I need to wrap
them as well to get libtool to work with wrappers alone? If so i think
there may be a better way of doing this :-)


Thanks,
Brendon.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEcV+aPfREiUgoLqwRAlXoAJ0clFO9MXp5LESiBBdi2JVDGw64RACdFQan
8BGO0V3VeCJeIPKKl4T9bcw=
=qUCy
-----END PGP SIGNATURE-----